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

INTRODUCTION

Espresso is a global confirmation layer that provides L2 chains with fast, reliable transaction confirmations backed by BFT consensus.

NextEspresso in the Modular Stack

Last updated 2 months ago

Espresso confirmations can improve cross-chain composability, as they provide chains with near-instant access to reliable, credibly neutral information about what’s happening not just on their own chain, but on all chains plugged into the network. Espresso's confirmation layer can prevent sequencer equivocation, protect against reorgs, and reduce finality risk for solvers in intent-based systems. Its versatility means chains can also use it as a decentralized sequencer and low-cost data availability layer.

The Espresso Network is currently in its and supports applications by providing the following functionality:

  1. Fast confirmations: HotShot, the consensus protocol used by the Espresso Network, confirms transactions within a few seconds. This enables bridges to move assets from chains integrated with Espresso at high speeds with minimal risk. Chains can maintain a centralized sequencer while opting in to Espresso for stronger confirmations.

  2. Decentralized sequencing: 100 nodes will be running the Espresso Network in a decentralized manner during Mainnet 0. Rollups can opt into having their transactions sequenced by this group of 100 nodes, instead of using their own centralized sequencer. We plan to quickly scale the number of participating nodes and enable permissionless proof-of-stake-based participation following the Mainnet 0 release.

  3. Low-cost data availability: Espresso offers applications a cheaper alternative to Ethereum for DA. Any integration with Espresso can take advantage of Espresso's strong data availability guarantee to improve its scalability.

Chains and applications can quickly get started with using Espresso following these . For the easiest deployment experience, we are also actively contributing to integrations for the following stacks:

If you don't see your stack listed above, or if you'd like to help improve our current integration work, please ! You can also explore our high level integration guides if you'd like to start working on your own integration.

If you're a chain or application looking to enable faster bridging using Espresso confirmations, .

To learn more about the inner workings of the Espresso Network, .

In our documentation we generically refer to chains, rollups and L2s, but Espresso supports any kind of application that requires fast confirmations, transaction ordering, and/or data availability.

Mainnet 0 release
general integration steps
Arbitrum Orbit chains
Cartesi applications
OP stack chains
Polygon CDK
get in touch with us here
ZK rollup
Optimistic rollup
click here
please read this section of the docs