beacon-APIs
beacon-APIs copied to clipboard
ethereum
Collection of RESTful APIs provided by Ethereum Beacon nodes
Thanks to [ethereum/consensus-specs/pull/3506](https://github.com/ethereum/consensus-specs/pull/3506) we have canonical mapping of SSZ -> YAML, so it is possible to derive OpenAPI schemas for all the spec types. Since the vast majority of API...
Investigate solutions to ease PR verifications, notably that no regression gets introduced in the UI. e.g. * testing framework with unit tests/screenshot diffs * deployment per PR for manual inspection...
- https://github.com/ethereum/beacon-APIs/issues/186 noted missing route to retrieve SyncCommitteeSignature from the pool There hasn't been much demand for it, but there's no good reason to omit this route on purpose so...
The SSE block event is used currently to measure block propagation times. This data is critical to inform decisions like blob count and overall network health. In consensus clients blocks...
As discussed in #377 and #386, Blocks V3 enforce BNs to produce unblinded content when execution payload is built locally, and return a blinded content only when is built remotely...
The `/eth/v1/node/peers` returns a `meta` element that contains a `count` item. The schema for this item declares the value to be a number, which is inconsistent with the common format...
Currently we need to reimplement everything that beacon node is doing to measure the withdrawable epoch and time. It'll be good to have an API returning back informations like: -...
We recently had some interoperability issues when new parameters has been introduced in the configuration. As an example, when networking parameters has been promoted to [configuration parameters](https://github.com/ethereum/consensus-specs/blob/28e3c807e29f0125f6871fbc06ec3465597b8175/configs/mainnet.yaml#L106) caused VCs failing...
The `/eth/v1/beacon/states//validators` endpoint returns a lot of data. At the time of writing, this endpoint returns around 370MB of JSON. This requires a fair amount of CPU and memory resources...
- All endpoints in the `Beacon` section begin with `/eth/v{1,2}/beacon/...` - All endpoints in the `Builder` section begin with `/eth/v1/builder/...` - All endpoints in the `Config` section begin with `/eth/v1/config/...`...
