Skip to content

Engine API: Strict message ordering #89

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

Merged
merged 5 commits into from
Oct 29, 2021
Merged

Engine API: Strict message ordering #89

Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
5ba0f15
add directive about using rpc id to resolve fork choice ordering
djrtwo Oct 28, 2021
98cadfd
rquire JSON RPC message ID ordering for all messages
djrtwo Oct 29, 2021
307634a
Use CL and EL terms for clarity
mkalinin Oct 29, 2021
e98cd1b
Apply suggestions from code review
djrtwo Oct 29, 2021
6d86792
Merge pull request #92 from mkalinin/patch-1
djrtwo Oct 29, 2021
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/specification.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,6 +11,14 @@ This specification is based on [Ethereum JSON-RPC API](https://eth.wiki/json-rpc

Client software **MUST** expose Engine API at a port independent from JSON-RPC API. The default port for the Engine API is 8550 for HTTP and 8551 for WebSocket.

## Message ordering

Consensus Layer client software **MUST** utilize JSON-RPC request IDs that are strictly
increasing.

Execution Layer client software **MUST** execute calls strictly in the order of request IDs
to avoid degenerate race conditions.

## Load-balancing and advanced configurations

The Engine API supports a one-to-many Consensus Layer to Execution Layer configuration.
Expand Down