Skip to content

Commit

Permalink
Apply suggestions from code review
Browse files Browse the repository at this point in the history
MAY -> SHOULD for block value calculation spec

Co-authored-by: Mikhail Kalinin <noblesse.knight@gmail.com>
Co-authored-by: lightclient <14004106+lightclient@users.noreply.github.com>
  • Loading branch information
3 people committed Dec 24, 2022
1 parent 292a683 commit 710e2b7
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions src/engine/specification.md
Original file line number Diff line number Diff line change
Expand Up @@ -476,14 +476,14 @@ This method follows the same specification as [`engine_forkchoiceUpdatedV1`](#en

* result: `object`
- `executionPayload`: [`ExecutionPayloadV2`](#ExecutionPayloadV2)
- `blockValue` : `QUANTITY`, 256 Bits - The expected value to be recieved by the `feeRecipient` in wei
- `blockValue` : `QUANTITY`, 256 Bits - The expected value to be received by the `feeRecipient` in wei
* error: code and message set in case an exception happens while getting the payload.

#### Specification

This method follows the same specification as [`engine_getPayloadV1`](#engine_getpayloadv1) with the addition of the following:

1. Client software **MAY** use the sum of the block's priority fees or any other algorithm to determine `blockValue`.
1. Client software **SHOULD** use the sum of the block's priority fees or any other algorithm to determine `blockValue`.

### engine_exchangeTransitionConfigurationV1

Expand Down

0 comments on commit 710e2b7

Please sign in to comment.