Paper 2024/1189

The Espresso Sequencing Network: HotShot Consensus, Tiramisu Data-Availability, and Builder-Exchange

Jeb Bearer, Espresso Systems
Benedikt Bünz, Espresso Systems, New York University
Philippe Camacho, Espresso Systems
Binyi Chen, Espresso Systems, Stanford University
Ellie Davidson, Espresso Systems
Ben Fisch, Espresso Systems, Yale University
Brendon Fish, Espresso Systems
Gus Gutoski, Espresso Systems
Fernando Krell, Espresso Systems
Chengyu Lin, Espresso Systems
Dahlia Malkhi, Espresso Systems, University of California, Santa Barbara, Chainlink Labs
Kartik Nayak, Espresso Systems, Duke University
Keyao Shen, Espresso Systems
Alex Xiong, Espresso Systems
Nathan Yospe, Espresso Systems
Sishan Long, Espresso Systems
Abstract

Building a Consensus platform for shared sequencing can power an ecosystem of layer-2 solutions such as rollups which are crucial for scaling blockchains (e.g.,Ethereum). However, it drastically differs from conventional Consensus for blockchains in two key considerations: • (No) Execution: A shared sequencing platform is not responsible for pre-validating blocks nor for processing state updates. Therefore, agreement is formed on a sequence of certificates of block data-availability (DA) without persisting them or obtaining blocks in full. At the same time, the platform must stream block data with very high efficiency to layer-2 entities for execution, or (in the case of rollups) for proof generation. • Builder-Exchange: A shared sequencing platform delegates to external entities to build blocks and separates it from the role of a consensus proposer. This allows an ecosystem of specialized builders to pre-validate transactions for diversified rollups, languages, and MEV exploits. However, separating the task of block-building from proposing brings a new challenge. Builders want assurances that their blocks would commit in exchange for revealing their contents, whereas validators/proposers want assurance that the data in committed blocks will be available and fees paid. Neither one trusts the other, hence the shared sequencing platform should facilitate a “fair-exchange” between builders and the sequencing network. The Espresso Sequencing Network is purpose-built to address these unique considerations. Among the main novelties of the design are (i) a three-layered DA system called Tiramisu, coupled with (ii) a costless integration of the DA with the platform’s consensus core, and (iii) a Builder-Exchange mechanism between builders and the consensus core. Note that this paper relies substantially on and can be seen as an extension of The Espresso Sequencer: HotShot Consensus and Tiramisu Data Availability [84].

Note: Minor update.

Metadata
Available format(s)
PDF
Category
Cryptographic protocols
Publication info
Preprint.
Keywords
consensusdata-availabilityblockchainfair-exchange
Contact author(s)
jeb @ espressosys com
benedikt @ espressosys com
philippe @ espressosys com
binyi @ espressosys com
ellie @ espressosys com
ben @ espressosys com
brendon @ espressosys com
gus @ espressosys com
fernando @ espressosys com
chengyu @ espressosys com
dahlia @ espressosys com
kartik @ espressosys com
keyao @ espressosys com
alex @ espressosys com
nathan @ espressosys com
sishan @ espressosys com
History
2024-08-14: last of 2 revisions
2024-07-23: received
See all versions
Short URL
https://ia.cr/2024/1189
License
Creative Commons Attribution
CC BY

BibTeX

@misc{cryptoeprint:2024/1189,
      author = {Jeb Bearer and Benedikt Bünz and Philippe Camacho and Binyi Chen and Ellie Davidson and Ben Fisch and Brendon Fish and Gus Gutoski and Fernando Krell and Chengyu Lin and Dahlia Malkhi and Kartik Nayak and Keyao Shen and Alex Xiong and Nathan Yospe and Sishan Long},
      title = {The Espresso Sequencing Network: {HotShot} Consensus, Tiramisu Data-Availability, and Builder-Exchange},
      howpublished = {Cryptology {ePrint} Archive, Paper 2024/1189},
      year = {2024},
      url = {https://eprint.iacr.org/2024/1189}
}
Note: In order to protect the privacy of readers, eprint.iacr.org does not use cookies or embedded third party content.