HotShot

  • Name: HotShot
  • URL: https://docs.espressosys.com/network/concepts/the-espresso-network/properties-of-hotshot
  • Category: shared-confirmation consensus subprotocol / DA-aware BFT ordering layer / modular sequencing consensus / Espresso infrastructure
  • Tags: ethereum-ecosystem
  • Summary: HotShot is the consensus-and-availability-certification sublayer inside Espresso’s shared-confirmation stack, not just another internal implementation detail. The useful part is the split it keeps visible: validators vote on block commitments instead of executing transactions, a sampled DA committee plus VID retrievability forms the DAC, and finalized commitments can be anchored to L1. That makes HotShot a good lower-layer comparison point for shared sequencing and rollup-confirmation systems.
  • What it does:
    • Finalizes block commitments for Espresso and provides fast confirmations for connected rollups
    • Separates execution from consensus so participating nodes do not need to execute transactions before voting on ordering/finality
    • Uses a DA path that combines a sampled committee’s optimistic availability votes with VID-based retrievability shares to form a DAC before commitment finalization
    • Lets Espresso post finalized commitment data and proofs to an L1 contract so downstream rollups can verify that a referenced Espresso block really was finalized
    • Emphasizes leader-based all-to-leader / leader-to-all communication and optional CDN-assisted routing as the scaling path toward large validator sets
    • Now lives operationally inside Espresso’s sequencer monorepo, with the older standalone HotShot repository archived
  • Key claims:
    • HotShot clears the corpus bar because it exposes a reusable lower layer beneath Espresso’s higher-level shared sequencer framing: commitment voting, DA certification, and L1-verifiable finality are explicit modules rather than one blended sequencing brand.
    • The most important architectural claim in the docs is the separation of execution and DA from consensus. HotShot nodes vote without executing rollup transactions, and the default DA path is treated as a separate mechanism rather than something implicit in the consensus messages.
    • The DA design is analytically useful because it does not rely only on a committee or only on erasure-style retrievability. The reviewed docs describe a DAC composed from an optimistic committee certificate plus a VID retrievability certificate, making the hybrid construction itself a key comparison surface.
    • The system-overview and L1-interface docs also show that HotShot is not merely offchain soft confirmation. Finalized commitments are meant to be posted to an L1 contract that other rollup components use as a trustless checkpoint surface.
    • HotShot belongs in the active corpus because leaving it folded entirely into Espresso would hide where practical authority may sit: leader rotation, DA committee formation, CDN / networking assumptions, stake distribution, and contract-level proof-verification policy.
    • The archived-repo notice is itself worth preserving in the corpus because it marks a governance and maintenance shift: the standalone codebase is no longer the live implementation, and the actual operational surface now follows Espresso’s sequencer monorepo and docs.
  • Whitepaper: No standalone canonical HotShot whitepaper surfaced in this pass. The strongest primary materials reviewed were the official Espresso documentation pages covering HotShot properties, system flow, data availability, and L1 interfacing, plus the archived HotShot repository notice; see ../whitepapers/hotshot-primary-sources-2026-05-14.md.
  • Sources:

Internal linkages

  • Parent stack and cleanest baseline: espresso and hotstuff-2.

  • Strongest external contrast: astria.

  • Last reviewed: 2026-05-14 UTC