charon
charon copied to clipboard
validator registrations with lighthouse
🎯 Problem to be solved
We want to support validator registrations with lighthouse Validator Client.
Ciaran already worked on such a PR 7 months back. But since then, we have formalized the solution with this design doc. We have also added an internal proposal for a new endpoint /eth/v1/validator/proposer_config
to standardize how different VCs fetch override values for pubkey
& timestamp
.
So, in a nutshell, we want lighthouse VC to be capable of fetching override values from charon DVT and use those values to perform validator registrations in a DV setting.
🛠️ Proposed solution
- Fix the outdated PR with a new PR branching off latest unstable branch of
sigp:lighthouse
. Use the original PR as a reference. - Add support for the new endpoint
/eth/v1/validator/proposer_config
to lighthouse VC
🧪 Tests
- [ ] Tested by new automated unit/integration/smoke tests
- [ ] Manually tested on core team/canary/test clusters
- [ ] Manually tested on local compose simnet
See this WIP PR - https://github.com/xenowits/lighthouse/pull/1
See PR on lighthouse - https://github.com/sigp/lighthouse/pull/4306
@boulder225 to add comments