KVORUM
lidoSource: Snapshot · #0x2676108832842e60ca27aa7060b9ca6c09c6d2a9fe308b0ee0decc7a6728e137

Lido Alliance application: Bolt

succeededOct 24, 2024, 04:00 PM UTCsignaling · non-bindingbyDB0xdbbc…1cb6View on Snapshot ↗

01Summary

AISummary by Kvorum

An AI summary is not generated yet. Read the description →

02Description

660 words

Summary

Bolt, a protocol developed by Chainbound, enables sub-second preconfirmations on Ethereum through the use of proposer commitments, a novel primitive that allows proposers (validators) to make credible commitments on the blocks they produce.

In this proposal, Chainbound asks for the onboarding Bolt as a part of Lido Alliance (a framework for Lido DAO to provide support and endorsement to protocols that share a strong dedication to security and an unwavering commitment to decentralizing Ethereum validation, more details here).

How Bolt will help the Lido Alliance achieve its mission:

  • Ethereum-alignment and commitment to decentralized validation

Bolt’s innovation helps improve Ethereum's UX and bolsters its censorship resistance, namely via new out-of-protocol primitives such as preconfirmations and inclusion lists.

Bolt’s preconfirmation design is trust-minimized, credible, permissionless and compatible with the existing PBS pipeline (and eventually ePBS). Ultimately, the goal is to boost the value of differentiated blockspace for users and applications, as well as generate more yield for validators.

  • Strategic alignment with Lido DAO’s values and long-term goals

One of the key reGOOSE principles, adopted in May of this year, is to ‘support Ethereum-aligned validator services, starting with preconfirmations without exposing users to additional risk’.

Preconfirmation offers significant advantages to the end user, such as the provision of early signals of transaction validity, reduced uncertainty during the confirmation period, improved security measures and faster decision-making for time-sensitive applications.

Preconfirmations are high on the list of use cases that should be championed by the Lido Alliance. Their implementation supports the innovation ethos and helps the protocol stay on top of the latest advancements in the block production pipeline.

  • Effective Preconf solution for Node Operators on Lido on Ethereum

Bolt is implemented out-of-protocol, easy to integrate, and designed to be compatible with the existing block production pipeline. It covers a number of existing block-space use cases while future-proofing in case of a transition towards ePBS. With Bolt, validators do not need to rely on trusted relationships (no added gateways or special relays are required in order to run the software) to make commitments to further monetize their blockspace, which minimizes centralization factors and single-point of failure risks.

  • Chainbound Commitment to Lido Alliance

Chainbound plans to allocate 6.5% of Bolt's total token supply to the Lido Alliance. The total allocation consists of two components:

  • Strategic Allocation: 3.5%

This 3.5% represents the minimum number of tokens that the Lido Alliance will receive. Tokens will follow the same unlock schedule as early contributors to Bolt.

  • KPI-Based Allocation: 3%

The KPI is defined as the percentage of Ethereum delegated to validators part of the Lido on Ethereum Curated Module who have opted in and are running the Bolt protocol, out of the total amount of Ethereum delegated to all validators part of the Lido on Ethereum Curated Module.

A 90% adoption rate among the validators part of the Lido on Ethereum Curated Module is targeted as the threshold for 100% KPI achievement.

More in-depth explanations with examples can be found at the link.

What Chainbound is seeking from Lido Alliance membership:

  • Endorsement, Integration, and communication support

Lido DAO’s acceptance of Chainbound as a member of Lido Alliance for the Bolt protocol.

Lido DAO will endorse Bolt as one of the preconfirmation solutions that align with key reGOOSE principles, facilitating the adoption of Bolt on Ethereum. This initiative will begin with support for Cohort 1, a working group focused on testing Bolt on Holesky, by encouraging Node Operators within Lido on Ethereum to participate in Bolt’s opt-in testnet.

To the extent possible and where appropriate, collaborate with Bolt in community distribution channels, such as websites, landing pages, and support large Bolt announcements.

  • Support and consultation

Direct collaboration with Lido’s contributors and working groups, including feedback and evaluation of Bolt’s design choices, suggestions on auditors and potential partners, and continuous testing of the Bolt software.

Proposal actions

Through the proposal, Chainbound requests onboarding of Bolt to Lido Alliance.

03Mismatch analysis

AIMismatch analysis by Kvorum

A calldata-vs-description analysis is not generated yet. Review the decoded actions →

04Actions

0 total

This proposal carries no on-chain actions.

05Tally

Summed from votes

Voters91
VP participating0
Outcome (current)Onboard Bolt to Lido Alliance
Current support—

06Voters

91 total
Filter:
VoterChoice% of totalRationale
4A0x4af8…6a0bOnboard Bolt to Lido Alliance021.34%—2y ago
7E0x7ee0…bb6cOnboard Bolt to Lido Alliance08.19%—2y ago
510x510a…8d0eOnboard Bolt to Lido Alliance06.41%—2y ago
6D0x6d8d…0cccOnboard Bolt to Lido Alliance06.33%—2y ago
EE0xee44…fad1Onboard Bolt to Lido Alliance05.88%—2y ago
LIlido.banteg.eth0x55bc…f0faOnboard Bolt to Lido Alliance05.88%—2y ago
A40xa418…b737Onboard Bolt to Lido Alliance05.78%—2y ago
4C0x4ca1…2945Onboard Bolt to Lido Alliance05.71%—2y ago
9C0x9ca8…36afOnboard Bolt to Lido Alliance05.13%—2y ago
3D0x3ddc…05b0Onboard Bolt to Lido Alliance04.16%—2y ago
FF0xff41…a67bOnboard Bolt to Lido Alliance04.08%—2y ago
BE0xbeb3…7646Onboard Bolt to Lido Alliance03.46%—2y ago
110x1109…43daOnboard Bolt to Lido Alliance03.33%—2y ago
CE0xce3b…2e55Onboard Bolt to Lido Alliance03.27%—2y ago
6A0x6a39…4bd2Onboard Bolt to Lido Alliance02.34%—2y ago
1F0x1f76…5ed6Onboard Bolt to Lido Alliance02.04%—2y ago
B90xb933…8dd1Onboard Bolt to Lido Alliance01.56%—2y ago
7A0x7a59…8e22Onboard Bolt to Lido Alliance01.50%—2y ago
A20xa2ff…7be9Onboard Bolt to Lido Alliance01.03%—2y ago
870x8787…ea52Onboard Bolt to Lido Alliance00.52%—2y ago
E80xe80e…28e8Onboard Bolt to Lido Alliance00.52%—2y ago
B60xb664…f890Onboard Bolt to Lido Alliance00.46%—2y ago
290x29b5…2c2fOnboard Bolt to Lido Alliance00.33%—2y ago
6F0x6f9b…8a1dNo Action00.33%—2y ago
980x9830…bd94Onboard Bolt to Lido Alliance00.13%—2y ago
060x06a9…bba0Onboard Bolt to Lido Alliance00.13%—2y ago
3D0x3d63…4afcOnboard Bolt to Lido Alliance00.10%—2y ago
3F0x3fb1…4c8aOnboard Bolt to Lido Alliance00.03%—2y ago
050x0579…4048Onboard Bolt to Lido Alliance00.00%—2y ago
CE0xcedf…614bOnboard Bolt to Lido Alliance00.00%—2y ago
420x42e6…3fb0Onboard Bolt to Lido Alliance00.00%—2y ago
7A0x7af3…8df3Onboard Bolt to Lido Alliance00.00%—2y ago
4D0x4d26…7017Onboard Bolt to Lido Alliance00.00%—2y ago
3D0x3d5a…b97fOnboard Bolt to Lido Alliance00.00%—2y ago
B70xb792…89d7Onboard Bolt to Lido Alliance00.00%—2y ago
6A0x6afa…5deeOnboard Bolt to Lido Alliance00.00%—2y ago
ED0xed95…68a6Onboard Bolt to Lido Alliance00.00%—2y ago
0F0x0fad…1d32Onboard Bolt to Lido Alliance00.00%—2y ago
520x5243…3440No Action00.00%—2y ago
C30xc34a…68c2Onboard Bolt to Lido Alliance00.00%—2y ago
EC0xecc2…6ac9Onboard Bolt to Lido Alliance00.00%—2y ago
C10xc1c2…24f8Onboard Bolt to Lido Alliance00.00%—2y ago
E60xe6b5…f1fdOnboard Bolt to Lido Alliance00.00%—2y ago
530x53c4…3584Onboard Bolt to Lido Alliance00.00%—2y ago
D30xd31a…1072Onboard Bolt to Lido Alliance00.00%—2y ago
8B0x8bc8…7276Onboard Bolt to Lido Alliance00.00%—2y ago
C40xc48b…75b6Onboard Bolt to Lido Alliance00.00%—2y ago
500x500f…7d0bOnboard Bolt to Lido Alliance00.00%—2y ago
270x2748…ac26Onboard Bolt to Lido Alliance00.00%—2y ago
D50xd5d7…3c4dOnboard Bolt to Lido Alliance00.00%—2y ago
Showing 50

07Forum

No forum thread is confidently linked to this proposal.

08Similar proposals

AI · embeddings

No semantically similar proposals found yet.