Nico Flaig
Nico Flaig
### Problem description The current implementation of [eventstream](https://ethereum.github.io/beacon-APIs/#/Events/eventstream) does not support fallback beacon nodes. Only the URL of the primary node is used https://github.com/ChainSafe/lodestar/blob/959a8af1b757c46a0e57450788fb72773a372608/packages/api/src/beacon/client/index.ts#L31 This means if primary node is...
From https://github.com/ethereum/builder-specs/pull/95: > Honest proposers implement a "circuit breaker" condition operationalized by the beacon node that is triggered when the node determines the chain is unhealthy. When the circuit breaker...
Add named ssz types introduced in https://github.com/ethereum/consensus-specs/pull/3563 for representing LC Merkle branches. | Name | SSZ equivalent | Description | | - | - | - | | `FinalityBranch` |...
- https://github.com/ethereum/beacon-APIs/pull/367
### Describe the bug The beacon API spec notes that multiple API errors (e.g [submitPoolAttestations](https://ethereum.github.io/beacon-APIs/#/ValidatorRequiredApi/submitPoolAttestations)) should return a 400 error with details of each failure. > If one or more...
> Maybe we should run `yarn check-readme` in CI along with tests to keep these readmes compile-able? We actually do https://github.com/ChainSafe/lodestar/blob/88744d8a4877499c8c7aa43aeb4d576b98581faf/.github/workflows/test.yml#L144-L145 But it doesn't seem to care at all ```bash...
### Problem description As discussed [on discord](https://discord.com/channels/593655374469660673/605818244036821012/1186256566056390667) it would be useful to be able to configure a different builder URL per validator. It is relevant for DVT setups when running...
> It might be worth updating the consensus-specs link to so that they both point to their respective master branches. I don't think it good to point to master branch...
To be compliant to latest beacon API spec ([v2.5.0](https://github.com/ethereum/beacon-APIs/releases/tag/v2.5.0)) several updates are required. # v2.5.0 - [ ] https://github.com/ChainSafe/lodestar/issues/6470 - [x] https://github.com/ChainSafe/lodestar/issues/6058 # v2.4.2 - [x] https://github.com/ChainSafe/lodestar/issues/6185 # v2.4.1 *Nothing*...
### Describe the bug Some keymanager APIs are not spec compliant due to the fact that we return a empty json body even though the HTTP status code is 204...