Chainbound Profile picture
May 31 11 tweets 3 min read Read on X
1/ We are thrilled to soft-launch Bolt, a trustless protocol that allows Ethereum proposers to offer credible commitments about their block contents. Bolt V1 unlocks trustless inclusion preconfirmations, a new primitive that aims to enhance Ethereum’s UX and applicability. Image
2/ You can directly check Bolt's documentation here! If you're just interested in a TLDR, continue reading :)

Let’s break down how Bolt impacts the main entities within the block production pipeline 👨‍🍳

chainbound.github.io/bolt-docs/
3/ For Validators, Bolt will allow them to recapture agency and further monetize their most valuable asset: blockspace. Bolt aims to bring new revenue streams and expand the scope of proposers. Contact us to learn more and be included in "Cohort 1" for a demo and testing.
4/ For Users, Bolt's goal is to realize L1 pre-confirmations, enabling near-instant transaction confirmation. We've identified numerous compelling use cases for this and will share more details in the coming weeks!
5/ For Relay and Builders, Bolt doesn’t change much, but does extend the builder-API to communicate and enforce block ‘constraints.’ Builders will now need to build around these constraints and provide light-weight proofs back to the proposer.
6/ Bolt has 4 core design principles:
- Trustless: No new trusted relationships. Commitments are backed by (re)staked collateral, not by trusted intermediaries such as relays.
- Credible: Bolt is proposer-centric. Proposers are entirely held accountable for their commitments.
7/ - Permissionless: Any proposer/relay/builder can opt into the protocol, and any user can request commitments.
- Compatible: Bolt is compatible with the existing PBS pipeline (eventually ePBS). A proposer needs only to run an additional sidecar and a modified mev-boost client.
8/ Bolt is simple to integrate. Proposers extend their stack with a new component called the bolt-sidecar that implements the default builder-API and two new interfaces: The Commitments API and Constraints API. Image
9/ Commitments API — Channel Users use to interact with Proposers and receive credible commitments.
Constraints API — Extension of the builder and relay APIs, enabling proposers to convey constraints to builders and receive validity proofs from builders.
10/ Bolt V1 is our initial move towards a broad vision of enabling generic credible commitments. Our roadmap: Image
11/ This is a call to action! If you're a team building similar software, a validator, a builder, or anyone interested, please reach out. Let’s establish standards together! In the meantime, checkout our docs!

chainbound.github.io/bolt-docs/

• • •

Missing some Tweet in this thread? You can try to force a refresh
 

Keep Current with Chainbound

Chainbound Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Don't want to be a Premium member but still want to support us?

Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal

Or Donate anonymously using crypto!

Ethereum

0xfe58350B80634f60Fa6Dc149a72b4DFbc17D341E copy

Bitcoin

3ATGMxNzCUFzxpMCHL5sWSt4DVtS8UqXpi copy

Thank you for your support!

Follow Us!

:(