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
  • Preconfirmations
  • Faucet
  • Transaction Submission Using MetaMask
  1. Releases
  2. Testnets
  3. Doppio Testnet Release

Interacting with Doppio

PreviousDoppio Testnet ReleaseNextPolygon zkEVM Stack Integration

Last updated 7 months ago

With the deployment of (testnet 3), the instructions in this document for connecting to Doppio no longer work. See for instructions for interacting with Cortado.

  1. If not yet set up, install and set up a new wallet.

  2. In MetaMask, click on the upper left icon to select a network.

  3. Click "Add network" -> "Add a network manually".

Use the following parameters:

  • Network name: espresso-polygon-zkevm-0

  • Chain ID: 1001

To interact with the second rollup, add a network with these parameters:

  • Network name: espresso-polygon-zkevm-1

  • Chain ID: 1002

For "Currency symbol", anything can be set and "Block explorer URL" should be left blank.

Preconfirmations

The Espresso Sequencer uses the HotShot consensus protocol to provide fast confirmations of new blocks. These confirmations are secure, in that a block confirmed by HotShot is guaranteed to execute in the order determined by HotShot unless at least 1/3 of the total value staked in consensus is corrupt. They are also fast: a block may be confirmed by HotShot well before the same block is eventually processed by the layer 1 blockchain.

The RPC node for zkevm-0 that you connected to above uses these "preconfirmations" from HotShot to achieve low latency, but the RPC node for zkevm-1 does not. Try transferring some ETH on each network. Do you notice a difference in the speed with which the transaction gets confirmed?

For a more direct comparison, Doppio also includes an additional RPC node for zkevm-0 which fetches new blocks from the L1 rollup contract instead of directly from the Espresso Sequencer. You can try this "slow" RPC node to compare the latency with and without preconfirmations on the same L2.

Faucet

To copy your MetaMask address, click on the address at the top of the MetaMask panel.

Transaction Submission Using MetaMask

The end-user experience for submitting transactions to an instance of the Polygon zkEVM running on the Espresso Sequencer via MetaMask is identical to the user experience of submitting transactions to Polygon rollup today. Additionally, gas savings are realized by utilizing Espresso DA rather than storing transactions in Ethereum L1 calldata.

New RPC URL:

New RPC URL:

To connect your MetaMask wallet to the slow RPC, go to Settings -> Networks and change the RPC URL for espresso-polygon-zkevm-0 to .

You can request funds in the #faucet channel with the following command: /faucet <address>

https://zkevm-0-preconfirmations.doppio.espresso.network
https://zkevm-1.doppio.espresso.network
https://zkevm-0.doppio.espresso.network
Discord
Cortado
Interacting with Cortado
MetaMask