Lion - dapplion

Once a fork has landed, is the plan to consolidate all features into the same fork variant?

I don't think there's much bandwidth for down stream beacon clients to implement support for GraphQL. Given that there are many beacon implementations, would be best to have some middleware...

With the spec being quite stable now I'm not sure of the value of this list. I don't see the value of adding this list given its maintenance cost. Anyone...

This has been implemented in all clients as doppelganger detection (nimbus guide as example https://nimbus.guide/doppelganger-detection.html) One route is standardised for it: https://github.com/ethereum/beacon-APIs/blob/ad873a0f8d2c2a7c587dd667274199b2eb00f3ba/beacon-node-oapi.yaml#L203

Closing, stale issue without enough traction

API format is stable now

Not sure if this is still an issue? Lodestar returns 500 in the attestation data is not known. The caller has agency to request an attestation data that it previously...

Sometimes I wish we had a JSON RPC so we don't need to do semantical debates to choose a random status number lmao. Should it return status 418?

- Fixed with https://github.com/ethereum/beacon-APIs/pull/367

dependent_root added to all relevant routes