[GUEST ACCESS MODE: Data is scrambled or limited to provide examples. Make requests using your API key to unlock full data. Check https://lunarcrush.ai/auth for authentication information.]  chokhrich | espresso [@chokhrich1](/creator/twitter/chokhrich1) on x XXX followers Created: 2025-07-21 14:27:21 UTC Alright, let’s dive in and share the rest of my research results with you! 🚀 The Data Availability Process: A Thrilling Journey! 🎢 Ready to see EspressoDA in action? Here’s a step-by-step look at how it ensures data availability with precision and speed: Sequencers and HotShot Kick Things Off: Sequencers submit blocks to the HotShot consensus protocol. In each view, a leader is chosen to bundle these blocks. Instead of sending full block data, the leader shares a commitment to the block for other nodes to vote on. Data Broadcasting Begins: The DA leader kicks off a broadcast to ensure data availability: - Sends the DA proposal to the DA committee. - Distributes VID chunks to all nodes. - Gradually sends the DA proposal to all nodes, with broadcasting prioritized for efficiency. A proposal gets rejected if it’s from the wrong leader or references an outdated view X. Nodes Vote on Availability: Nodes receiving the DA proposal send a strong DA vote to the leader, while those receiving only their VID chunk send a normal DA vote. X. Forming the Data Availability Certificate (DAC): Once enough votes are collected, the DA leader creates a Data Availability Certificate (DAC), which has two parts: - Optimistic DAC: Formed when the leader gets 2f+1 strong votes from the DA committee (where f is the number of faulty nodes in the committee). - Retrievability Certificate: Formed with f+1 strong votes (from committee or regular nodes) or f+m normal votes (where m is the number of VID chunks). This dual-certification approach ensures both speed (via the committee) and robustness (via VID). The leader stops broadcasting once the DAC is formed or when a new quorum certificate arrives. Block Commitment and Finalization: The leader sends a block commitment proposal (a cryptographic proof of the block’s validity and DA) to nodes. Nodes validate it if they receive: - The commitment proposal and DAC, or - The commitment proposal and DA proposal (block + view number). Once validated, nodes send quorum votes to the next consensus leader. With over two-thirds of HotShot stake being honest, no adversary not even one bribing the DA committee can forge a DAC. This makes EspressoDA both fast and secure XXX engagements  **Related Topics** [blockchain](/topic/blockchain) [protocol](/topic/protocol) [Post Link](https://x.com/chokhrich1/status/1947302379738517980)
[GUEST ACCESS MODE: Data is scrambled or limited to provide examples. Make requests using your API key to unlock full data. Check https://lunarcrush.ai/auth for authentication information.]
chokhrich | espresso @chokhrich1 on x XXX followers
Created: 2025-07-21 14:27:21 UTC
Alright, let’s dive in and share the rest of my research results with you! 🚀
The Data Availability Process: A Thrilling Journey! 🎢
Ready to see EspressoDA in action?
Here’s a step-by-step look at how it ensures data availability with precision and speed:
Sequencers and HotShot Kick Things Off: Sequencers submit blocks to the HotShot consensus protocol.
In each view, a leader is chosen to bundle these blocks. Instead of sending full block data, the leader shares a commitment to the block for other nodes to vote on.
Data Broadcasting Begins:
The DA leader kicks off a broadcast to ensure data availability:
- Sends the DA proposal to the DA committee.
- Distributes VID chunks to all nodes.
- Gradually sends the DA proposal to all nodes, with broadcasting prioritized for efficiency. A proposal gets rejected if it’s from the wrong leader or references an outdated view
X. Nodes Vote on Availability: Nodes receiving the DA proposal send a strong DA vote to the leader, while those receiving only their VID chunk send a normal DA vote.
X. Forming the Data Availability Certificate (DAC): Once enough votes are collected, the DA leader creates a Data Availability Certificate (DAC), which has two parts:
Optimistic DAC: Formed when the leader gets 2f+1 strong votes from the DA committee (where f is the number of faulty nodes in the committee).
Retrievability Certificate: Formed with f+1 strong votes (from committee or regular nodes) or f+m normal votes (where m is the number of VID chunks).
This dual-certification approach ensures both speed (via the committee) and robustness (via VID). The leader stops broadcasting once the DAC is formed or when a new quorum certificate arrives.
Block Commitment and Finalization: The leader sends a block commitment proposal (a cryptographic proof of the block’s validity and DA) to nodes. Nodes validate it if they receive:
- The commitment proposal and DAC, or
- The commitment proposal and DA proposal (block + view number).
Once validated, nodes send quorum votes to the next consensus leader. With over two-thirds of HotShot stake being honest, no adversary not even one bribing the DA committee can forge a DAC. This makes EspressoDA both fast and secure
XXX engagements
Related Topics blockchain protocol