ethereum / ethereum/builder-specs
How frequently do validator registrations need to be published?
- Dominant language
- HTML
- Stars
- 234
- Forks
- 86
- Avg merge
- 4d 1h
- Merged PRs (30d)
- 2
Description
The spec currently says validators should submit their registrations once per epoch.
However, it seems like the mev-boost component has the responsibility to keep registrations it learns about and upstream them to connected relays in which case the validator client may be posting data every ~6 mins for no additional gain.
I'm opening this issue to seek feedback on expectations around this process and if we can reduce the frequency I'm happy to change the spec to reflect that.
Based on my current understanding, the validator client only needs to call the registration API when they boot or if any of their registration data changes (which practically may be synonymous with boot if clients only allow changes to config during validator client process boot).
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reading the validator-registration requirements in the specification and the stated mev-boost responsibility. Compare the once-per-epoch wording with the proposed boot-or-change behavior; done means reaching agreement on expected publication frequency and updating the spec accordingly.
Written by the indexing model from the issue text.
Assessment
- Domain
- distributed-systems, documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100