[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.]  DUKE [@DUKETHAGREAT](/creator/twitter/DUKETHAGREAT) on x 10.7K followers Created: 2025-07-18 07:54:49 UTC . @EspressoSys’s BFT consensus protocol - HOTSHOT. The most trust minimized way to pass messages between L2 chains is by verifying them against an L1 blockhash. But this takes a long time! With fast proofs (either zkps or tees) it need not require waiting for the sending chain to settle, but it requires waiting for L1 finality (about XX min). It also depends on the frequency with which chains post to the L1, typically infrequently because posting is expensive! For interoperability to work well, chains need to be able to send and receive messages within seconds. To address the latency issues of L1-based messaging, interoperability cluster designs like the OP Superchain rely on a temporary trust assumption between chains and deeper settlement dependencies. First, all the chains in the cluster have interdependent settlement if one reorgs, it causes all others to reorg: "cascading reorgs". Prior to settlement time, a chain can act upon a message from another chain but it has to trust the sequencer of the sending chain. If it turns out the sending chain reported its messages incorrectly to the receiving chain then this will be caught during the cascading reorg and the messages will be discarded. This X day uncertainty window is reduced if chain operators all run full nodes for each other’s chains. A more scalable solution is sending validity proofs to one another, as is done within ZKSync’s Elastic Chains and Polygon’s AggLayer. There is still the risk of sequencer equivocation, a chain’s sequencer may report one block along with its proof to a recipient chain, yet publish a different block to the L1. Waiting for L1 finality takes the maximum of XX minutes and the frequency with which the sequencer publishes to the L1. Pairwise trust agreements between chains doesn’t scale, and carries great systemic risk. A single sequencer hack can send the whole system into a cascading reorg. This is where a trust minimized and robust confirmation layer, similar to the L1, but faster and cheaper comes into play. The Espresso Network runs a BFT consensus protocol called Hotshot which is designed to scale to a validator set as large and geographically diverse as Ethereum’s and reach similar levels of economic security. Hotshot is derived from the Hotstuff family of consensus protocols. In contrast to Ethereum, it is designed to reach finality (i.e. confirm transactions) within a few seconds. Moreover, Espresso Network runs Hotshot to agree on ordered blocks of data only, it does not require validators to perform any verification on these blocks of data. If you need explanation around any of this, do lmk in the comments. CC: @benafisch I’ll be sharing a lot about Espresso over the next few weeks, stay tuned!  XXXXX engagements  **Related Topics** [coins interoperability](/topic/coins-interoperability) [l2](/topic/l2) [protocol](/topic/protocol) [ethereum](/topic/ethereum) [coins layer 1](/topic/coins-layer-1) [Post Link](https://x.com/DUKETHAGREAT/status/1946116435358409120)
[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.]
DUKE @DUKETHAGREAT on x 10.7K followers
Created: 2025-07-18 07:54:49 UTC
. @EspressoSys’s BFT consensus protocol - HOTSHOT.
The most trust minimized way to pass messages between L2 chains is by verifying them against an L1 blockhash.
But this takes a long time!
With fast proofs (either zkps or tees) it need not require waiting for the sending chain to settle, but it requires waiting for L1 finality (about XX min).
It also depends on the frequency with which chains post to the L1, typically infrequently because posting is expensive!
For interoperability to work well, chains need to be able to send and receive messages within seconds.
To address the latency issues of L1-based messaging, interoperability cluster designs like the OP Superchain rely on a temporary trust assumption between chains and deeper settlement dependencies.
First, all the chains in the cluster have interdependent settlement if one reorgs, it causes all others to reorg: "cascading reorgs".
Prior to settlement time, a chain can act upon a message from another chain but it has to trust the sequencer of the sending chain.
If it turns out the sending chain reported its messages incorrectly to the receiving chain then this will be caught during the cascading reorg and the messages will be discarded.
This X day uncertainty window is reduced if chain operators all run full nodes for each other’s chains.
A more scalable solution is sending validity proofs to one another, as is done within ZKSync’s Elastic Chains and Polygon’s AggLayer.
There is still the risk of sequencer equivocation, a chain’s sequencer may report one block along with its proof to a recipient chain, yet publish a different block to the L1.
Waiting for L1 finality takes the maximum of XX minutes and the frequency with which the sequencer publishes to the L1.
Pairwise trust agreements between chains doesn’t scale, and carries great systemic risk.
A single sequencer hack can send the whole system into a cascading reorg.
This is where a trust minimized and robust confirmation layer, similar to the L1, but faster and cheaper comes into play.
The Espresso Network runs a BFT consensus protocol called Hotshot which is designed to scale to a validator set as large and geographically diverse as Ethereum’s and reach similar levels of economic security.
Hotshot is derived from the Hotstuff family of consensus protocols.
In contrast to Ethereum, it is designed to reach finality (i.e. confirm transactions) within a few seconds.
Moreover, Espresso Network runs Hotshot to agree on ordered blocks of data only, it does not require validators to perform any verification on these blocks of data.
If you need explanation around any of this, do lmk in the comments.
CC: @benafisch
I’ll be sharing a lot about Espresso over the next few weeks, stay tuned!
XXXXX engagements
Related Topics coins interoperability l2 protocol ethereum coins layer 1