LogoLogo
  • INTRODUCTION
  • LEARN
    • Espresso in the Modular Stack
    • The Espresso Network
      • System Overview
      • Properties of HotShot
        • EspressoDA
          • How It Works
      • Interfaces
        • Espresso ↔ Rollup
        • Espresso ↔ L1
        • Rollup ↔ L1
      • Internal Functionality
        • Espresso Node
        • Light Client Contract
        • Fee Token Contract
        • Stake Table
          • How the Stake Table Contract Works
        • Smart Contract Upgradeability
    • Rollup Stacks
      • Integrating a ZK Rollup
        • ZK Rollup Architecture
        • Using Espresso
        • Summary of Changes
      • Integrating an Optimistic Rollup
        • Optimistic Rollup Architecture
        • Using Espresso
        • Summary of Changes
  • Guides
    • Using the Espresso Network
      • Integrating Arbitrum Orbit Chain
        • Quickstart with Arbitrum Nitro Rollups
        • Reading Confirmations from the Espresso Network
        • Arbitrum Nitro Integration Overview
          • Using TEE with Nitro
          • Arbitrum Nitro Trust & Liveness Dependencies
        • Migrating Arbitrum Orbit Chains to Espresso
          • Arbitrum Testnet
            • Nitro Testnet
            • Local Deployment (`docker compose`)
      • Using the Espresso Network as a Cartesi application
    • Running an Espresso Node
    • Running a Builder
    • Bridging with the Espresso Network
  • API Reference
    • Espresso API
      • Status API
      • Catchup API
      • Availability API
      • Node API
      • State API
      • Events API
      • Submit API
      • Earlier Versions
        • v0
          • Status API
          • Catchup API
          • Availability API
          • Node API
          • State API
          • Events API
          • Submit API
    • Builder API
  • Releases
    • Mainnet 1
      • Running a Mainnet 1 Node
      • Contracts
      • Rollup Migration Guide
    • Mainnet 0
      • Running a Mainnet 0 Node
      • Contracts
    • Testnets
      • Decaf Testnet Release
        • Running a Node
        • Contracts
      • Cappuccino Testnet Release
        • Running a Node
        • Deploying a Rollup on Cappuccino
        • Benchmarks
      • Gibraltar Testnet Release
        • Interacting with Gibraltar
        • Arbitrum Nitro integration
        • Deploying a Rollup on Gibraltar
      • Cortado Testnet Release
        • Interacting with Cortado
        • OP Stack Integration
          • Optimism Leader Election RFP
      • Doppio Testnet Release
        • Interacting with Doppio
        • Polygon zkEVM Stack Integration
        • Minimal Rollup Example
        • Benchmarks
      • Americano Testnet Release
  • Appendix
    • Interacting with L1
      • Trustless Sync
      • Fork Recovery
      • Bridging
    • Glossary of Key Terms
Powered by GitBook
On this page
  1. LEARN

The Espresso Network

The global confirmation layer

Espresso's Global Confirmation Network is a shared source of truth that provides secure confirmations for transaction ordering and data across chains. It leverages a BFT consensus protocol called HotShot. Rollup transactions are processed by HotShot consensus and confirmed within a few seconds. By sharing the same Global Confirmation Network, chains have certainty within seconds about what state will eventually be finalized on the L1. This is achieved by preventing sequencers from changing a transaction sequence after it has been confirmed by HotShot, which can happen within only a few seconds (long before settlement on Ethereum).

Compared to relying on a disparate set of centralized sequencers for pre-confirmations, sharing a decentralized consensus protocol as a Global Confirmation Network bolsters the L2 ecosystem as a whole against equivocation of pre-confirmations that may occur as a result of hacks or bad actors. Applications that interact between multiple chains, such as bridges, are especially sensitive to the quality of confirmations of individual chains they are involved with.

This is reflected by the fact that for many of the largest bridge providers today, the waiting time for moving funds away from a rollup is around 15 minutes; the time it takes for the bridging transaction to be finalized inside a blob or as calldata on Ethereum. With HotShot, bridging between rollups can be done in a manner of seconds, as opposed to waiting 15 minutes for transactions to finalize on the Ethereum L1, with similar security guarantees.

The confirmation guarantees of HotShot mirror that of Ethereum L1. Once HotShot confirms a transaction reached, an adversary would need to control at least 1/3rd of the overall stake to revert said transaction. Combined with restaking, this means that HotShot's safety guarantee can approach that of Ethereum L1 over time. In the event that safety is broken, the adversary's stake will be slashed, making it very expensive to undo confirmations in HotShot.

PreviousEspresso in the Modular StackNextSystem Overview

Last updated 2 months ago