bolt • Holesky v1: Node Operator Working Group and Relay Support
This post aims to update the Lido community on our current Holesky Initiative, invite Node Operators to join Cohort 1 of our Working Group, and seek support for the recent proposal to add bolt-compatible relays to Lido’s vetted relay list.
NO Primer
To catch Lido community members up to speed, here is a quick primer and a couple helpful resources on bolt.
Bolt enables sub-second inclusion preconfirmations on Ethereum through the use of proposer commitments. For Ethereum validators, bolt allows proposers to take on additional duties (and risk) to access orthogonal reward streams in a MEV-Boost compatible and safe manner. By opting into the bolt protocol, proposers can make commitments with users and relay these commitments as constraints to MEV-Boost builders. This opens the door to a variety of potential use cases, including encrypted transaction inclusion, settlement guarantees for dApps and rollups, and based sequencing.
Resources:
Node Operator Working Group
As we progress towards mainnet, we have established a Node Operator Working Group composed of dedicated teams willing to run and support bolt. This is crucial because node operators (NOs) are the primary supply-side users and beneficiaries of bolt. From genesis, we have designed bolt around the needs and requirements of both node operators and liquid staking providers—and this remains true now that we are part of the Lido Alliance.
For each dedicated release of bolt, we plan to implement a staged cohort process. The updated format is as follows:
| Working Group Cohort | Environment | Release |
|---|---|---|
| Cohort 0 | Helder | bolt • Alpha |
| Cohort 1 (current) | Holesky | bolt • Holesky v1 |
| Cohort 2 | Holesky | bolt • Holesky v2 |
| Cohort 3 | Mainnet | bolt • Mainnet v1 |
Cohort 1 (Holesky v1)
We are currently live on Holesky and in the process of onboarding external validators, as part of our Cohort 1 of our Node Operator Working Group. The primary goals for Cohort 1 are for validators to get comfortable with bolt software and flows, give feedback on bolt’s design and where to iterate, and battle-test bolt before our next Holesky v2 release.
Here are useful links for our current Holesky release:
Everything is open-source, and we welcome anyone to participate on Holesky. We plan to have our first call with Cohort 1 this Friday at 9am EST (12/06). With this, we have a couple of requests for both the Lido community and node operators on Lido:
-
For the community, please support the RMC Proposal: Add Relays Supporting Proposer Commitments to the Holesky Allow List. We have had NOs from various Lido modules request this in efforts to test bolt on Holesky!
-
For node operators on Lido, please join our Working Group. We provide dedicated support to help you onboard onto Holesky. You can use this intake form we shared at Lido Connect, or reach out to the team directly!
Feel free to contact us with any questions or if you need further information. Thank you to the Lido community for being an integral part of bolt.