beacon-APIs
beacon-APIs copied to clipboard
ethereum
Collection of RESTful APIs provided by Ethereum Beacon nodes
Similar to execution api: https://github.com/ethereum/execution-apis/blob/main/.github/workflows/spellcheck.yaml
I noticed while browsing the API spec that there is no `GET /eth/v1/beacon/pool/sync_committees` to match the [POST](https://ethereum.github.io/beacon-APIs/#/Beacon/submitPoolSyncCommitteeSignatures) endpoint. For attestations and all other types of messages we define `GET` as...
The current description says: > and a successful response (20X) only indicates that the broadcast has been successful "Successful" can be interpreted in two ways: 1. the block was sent...
In Eth1 apis, certain endpoints are practically unusable because the amount of data returned is unbounded and becomes too large for certain consumers. If we have endpoints that return larger...
In renaming the repo, all links to https://ethereum.github.io/eth2.0-APIs/#/ were broken - it would be nice with a redirect such that old links continue to work.
Suggested API for VC to communicated with SSV node (SSV node will emulate BN API to VC, to keep things simple)
Some of the endpoints that use query strings don't play well with large numbers of validators. eg: `GET /eth/v1/beacon/states/{state_id}/validators` called with several hundred pubkeys To work around the issue, we...
**Problem** Somes probe systems uses HTTP status code as **yes**(200-2XX)/**no**(503) rather than **yes**(200)/**maybe**(206)/**no**(503), requiring complex configuration for integration (e.g: Kubernetes [probes](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#probe-v1-core), shell scripts, ...). To help those systems a non-breaking...
Should skipped slots return a 404 in the `/eth/v1/beacon/blocks/{block_id}` endpoint? In Lighthouse we return information about the most recent non-skipped slot presently. I don't see it explicitly in the spec....
- update validator status according to new spec: https://hackmd.io/bQxMDRt1RbS1TLno8K4NPg - removed validator status groups (it's simpler to just define all statuses) - didn't include next_state_epoch but included description how to...