🚧 Spec Changes
The following are spec changes to the beacon API and builder API that would improve Distributed Validator clients. These checklists track whether the spec changes are stable and accepted.
Distributed Sync Aggregation
Beacon Nodes
Whether consensus clients have implemented our proposed API endpoint additions. None of these are a priority or need to be implemented for a minimum viable mainnet, they are, however, important for DVT to scale to a large percentage of the validator set without harming network effectiveness.
Client | Aggregation Endpoint | Contribution Endpoint | Relay Registration Endpoint |
Teku | 🛑 | 🛑 | 🛑 |
Lighthouse | 🛑 | 🛑 | 🛑 |
Nimbus | 🛑 | 🛑 | 🛑 |
Prysm | 🛑 | 🛑 | 🛑 |
Lodestar | ✅ | 🛑 | 🛑 |
Validator Clients
Whether validator clients can use our new API endpoints to successfully aggregate attestations and sync messages, and register with relays. These changes do not need to be implemented for a minimum viable mainnet, but do need to be implemented to grow the number of DVs on mainnet.
Client | Supports distributed mode |
Teku | 🛑 |
Lighthouse | ✅ |
Nimbus | 🛑 |
Prysm | 🛑 |
Lodestar | 🛑 |
Vouch | 🛑 |