Skip to content

Commit

Permalink
Lint and specify v3 or v2 could be used
Browse files Browse the repository at this point in the history
  • Loading branch information
meyer9 committed Jan 21, 2025
1 parent c7702fa commit a6ba30f
Show file tree
Hide file tree
Showing 2 changed files with 3 additions and 4 deletions.
6 changes: 3 additions & 3 deletions specs/protocol/derivation.md
Original file line number Diff line number Diff line change
Expand Up @@ -746,9 +746,9 @@ To interact with the engine, the [execution engine API][exec-engine] is used, wi
- [`engine_newPayloadV3`] — executes an Ecotone execution payload to create a block.
- [`engine_newPayloadV4`] - executes an Isthmus execution payload to create a block.

The current version of `op-node` uses the `v4` Engine API RPC methods as well as `engine_newPayloadV3`, due to
`engine_newPayloadV4` only supporting Isthmus execution payloads. Both `engine_forkchoiceUpdatedV3` and
`engine_getPayloadV3` are backwards compatible with Bedrock, Canyon & Delta payloads.
The current version of `op-node` uses the `v4` Engine API RPC methods as well as `engine_newPayloadV3` and
`engine_newPayloadV2`, due to `engine_newPayloadV4` only supporting Isthmus execution payloads. Both `engine_forkchoiceUpdatedV4` and `engine_getPayloadV4` are backwards compatible with Ecotone, Bedrock,
Canyon & Delta payloads.

Prior versions of `op-node` used `v3`, `v2` and `v1` methods.

Expand Down
1 change: 0 additions & 1 deletion specs/protocol/exec-engine.md
Original file line number Diff line number Diff line change
Expand Up @@ -346,7 +346,6 @@ In Ecotone it MUST be set to the parentBeaconBlockRoot from the L1 Origin block
when called with `payloadAttributes`.
`engine_getPayloadV4` **must only be called with Isthmus payload.**


### `engine_signalSuperchainV1`

Optional extension to the Engine API. Signals superchain information to the Engine:
Expand Down

0 comments on commit a6ba30f

Please sign in to comment.