<aside> 💡 This page is publicly viewable!

</aside>

• Espresso forks of Nitro repos with chances for the integration with the Espresso sequencer:
  • https://github.com/EspressoSystems/nitro-espresso-integration
  • https://github.com/EspressoSystems/nitro-testnode
  • https://github.com/EspressoSystems/nitro-contracts/tree/develop
  • https://github.com/espressosystems/arbitrum-token-bridge
    • Note: The arbitrum-sdk used by the bridge UI requires a small change to be compatible with the Espresso integration: withdrawals will never become claimable if one uses the upstream UI at bridge.arbitrum.io.

Help

• If things don’t work as expected please send us all information you think is relevant. At a minimum share the configuration used as well as the complete (including the first start of the nodes) log files from all the services.

Local Devnet

git clone --branch integration --recursive <https://github.com/EspressoSystems/nitro-espresso-integration/>
cd nitro-espresso-integration/nitro-testnode
docker compose pull --ignore-pull-failures
./test-node.bash --init --validate --espresso --blockscout --latest-espresso-image

Note: since nitro-testnode is submodule of nitro one needs to run git submodule update in the nitro checkout when switching branches or pulling changes in the nitro checkout.

Docker images

• nitro-node-dev
• Release tag 20240711 should be used for deployments.
• Note on arm64 images: the module root currently does not match the amd64 images. The arm64 images are currently provided for local development on arm based computers only. When extracting the module root from images make sure it’s done on computers with amd64 architecture.

Contract deployment

Note: The upstream RollupCreator contracts do not deploy a version of the contracts that is compatible with the Espresso integration. Either our RollupCreator (see below) should be used or the contract in our fork of nitro-contracts needs to be deployed.

Contract deployment using deploy binary

For integration with the Espresso Sequencer we had to modify the OneStepProverHostIO contract. The OSP contract now needs to read from the HotShot Light Client contract. The deploy binary in our nitro fork has been updated to reflect this. The HotShot Light Client contract address needs to be passed via a new argument to the binary. The light client contract is deployed to sepolia here

  -hotshot string
    	the address of hotshot contract in L1

Contract deployment using hardhat scripts

Using deployed RollupCreator to create rollup

Espresso’s version of forked nitro-contracts contains a hardhat script which can be used to deploy a rollup given a RollupCreator address. We have already deployed a RollupCreator to sepolia here