Skip to content
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

Jump to bottom

Engine API: expose eth namespace to reduce to single connection #97

Merged
merged 2 commits into from
Nov 2, 2021
Merged

Engine API: expose eth namespace to reduce to single connection #97

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
f4e07d6
Engine API: expose eth namespace to reduce beacon-node usage of engin…
protolambda Nov 2, 2021
6a00401
Engine API: require eth namespace
protolambda Nov 2, 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
7 changes: 6 additions & 1 deletion src/engine/specification.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,12 @@ This specification is based on [Ethereum JSON-RPC API](https://eth.wiki/json-rpc
* Message format and encoding notation
* [Error codes improvement proposal](https://eth.wiki/json-rpc/json-rpc-error-codes-improvement-proposal)

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.
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.
The Engine API is exposed under the `engine` namespace.

To facilitate an Engine API consumer to access state and logs (e.g. proof-of-stake deposits) through the same connection,
the client **MUST** also expose the `eth` namespace.

## Versioning

Expand Down