Skip to content

Engine API: deprecate exchangeTransitionConfiguration #375

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
mkalinin wants to merge 3 commits into from
Closed

Engine API: deprecate exchangeTransitionConfiguration #375

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
de8fde9
Deprecate exchangeTransitionConfiguration
mkalinin Feb 2, 2023
ae4732e
Say that EL must not surface an error either
mkalinin Feb 3, 2023
5f59135
Update shanghai.md
mkalinin Feb 4, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions src/engine/shanghai.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -231,3 +231,11 @@ This method follows the same specification as [`engine_getPayloadV1`](./paris.md
1. Callers must be careful to verify the hash of the received blocks when requesting non-finalized parts of the chain since the response is prone to being re-orged.

1. Callers must consider that syncing execution layer client may not serve any block bodies, including those that were supplied by `engine_newPayload` calls.

### Deprecate `engine_exchangeTransitionConfigurationV1`

#### Specification

1. Consensus layer client software **MUST NOT** surface an error to the user if this method call fails with any error including `-32601: Method not found`. Consensus layer client software **MUST** still call this method.

1. Execution layer client software **MUST NOT** surface an error to the user if this method is not called.