Designing the Espresso Sequencer: Combining HotShot Consensus with Tiramisu DA - HackMD

We introduced the motivation, design principles and high-level requirements of Espresso Shared Decentralized Sequencer in an earlier note. In this series of notes, we will dive deeper into understanding the design of the two key components of our sequencer network: HotShot Consensus and the Tiramisu Data Availability layer. We will cover this in three sections:

Designing the Espresso Network: Combining HotShot Consensus with Espresso's Data Availability Layer - HackMD # Designing the Espresso Network: Combining HotShot Consensus with Espresso's Data Availability Layer ## Introduction We introduced the motivation, design principles and high-level requirements of the Espresso Network in an earlier [note](https://hackmd.io/@EspressoSystems/EspressoSequencer). In this post, we will dive deeper into understanding the design of the two key components of the Espresso Network: the HotShot consensus protocol and EspressoDA, our custom data availability (DA) l

related reading

• Based Espresso: ad-hoc shared sequencing for all L2s, from based rollups to validiums - HackMDhackmd.io
• The Hitchhiker's Guide to Ethereum - Delphi Digitalmembers.delphidigital.io
• Shared Sequencing: Defragmenting the L2 Rollup Ecosystem - HackMDhackmd.io
• Possible futures of the Ethereum protocol, part 2: The Surgevitalik.eth.limo
• Data availability sampling and danksharding: An overview and a proposal for improvements - a16z cryptoa16zcrypto.com
• EIP-4844: Shard Blob Transactionseips.ethereum.org
• Serenity Design Rationale - HackMDnotes.ethereum.org
• What is the difference between PBFT, Tendermint, HotStuff, and HotStuff-2?decentralizedthoughts.github.io
• A comparison between DA layers - General - Celestia Forumforum.celestia.org
• Networking layer | ethereum.orgethereum.org
• The Shared Sequencermaven11.com
• From 4844 to Danksharding, a DA layer roadmap | Francesco Damato (Januray 2024)youtube.com