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. Releases

Mainnet 0

Espresso Mainnet 0 release — October 2024

PreviousRollup Migration GuideNextRunning a Mainnet 0 Node

Last updated 2 months ago

Mainnet 0 marks the production release of the Espresso Network. This release is an important step towards enabling Espresso's vision of an ecosystem of open, composable and permissionless applications.

Espresso’s Global Confirmation Layer will support applications such as rollups with faster bridging, and lays the groundwork for chains to improve coordination amongst each other, enhancing cross-chain interoperability.

Underpinning the Espresso Network is HotShot, which will be run in a production setting for the first time. During the initial stages of Mainnet 0, HotShot will be run by a set of 20 node operators, running 100 nodes in total. An important upcoming milestone will be to open up participation to more node operators and increase economic security through proof-of-stake.

During the initial release, block size has conservatively been set to 1 MB, with plans to scale up to 5 MB in the short term if there is sufficient demand. We expect it to take around ~8 seconds for a transaction to be confirmed in the initial release. In the short term, an update to HotShot will implement ideas from HotStuff-2 to reduce this time to ~5-6 seconds. In the medium term, that will enable confirmation latency of ~3 seconds, even as we scale to thousands of consensus nodes. This will also enable us to increase the blocksize further without greatly impacting latency.

You can track activity on Mainnet in our , and you can interact with it via the .

a VID update is in the works
block explorer
public API endpoint