Quickstarts
Run the Chiado L2
CONFIGURE ONCE
.env from .env.chiado.example
poster + proof-signer keys
chiado L1 snapshot
shared JWT
published images (:latest by default)
$ cp .env.chiado.example .env && chmod 600 .env
# EEZ_L1_RPC_URL · EEZ_L1_POSTER_KEY · EEZ_PROOF_SIGNER_KEY
$ docker run --rm -v "$PWD/data/chiado-l1:/data" \
ghcr.io/gnosischain/reth_gnosis:v2.0.0 download --chain chiado --minimal --datadir /data
$ openssl rand -hex 32 > data/jwt.hex
→
faucet.chiadochain.net
funds the poster (and deployer) with test xDAI
All of it once — nothing is built locally; the node, signer and deploy images are pulled.
ROLLUP OPERATORS
How to run against a real testnet
This points the same stack at Chiado instead of a sandbox, from published Docker images.
Configure .env and prepare the embedded L1’s chain data once, deploy once, then one script starts the node, signer and Lighthouse and checks that settlement works.
WHAT YOU'LL LEARN
- 01 · CONFIGURE ONCE.env from the Chiado example with the RPC, poster and proof-signer keys, plus the L1 snapshot and JWT the embedded L1 needs to sync.
- 02 · DEPLOY ONCEThe published deploy image writes deployments.env and the genesis files. It broadcasts transactions, so it is never a restart step.
- 03 · START AND CHECKchiado-up.sh starts the three containers and reports UP only after L2 production, an L1 settlement and retrievable blobs.
PIN YOUR IMAGES · the three EEZ images default to :latest, which can change between starts; pin a full commit tag or digest. EEZ_DEPLOY_SKIP_SIMULATION=1 skips Foundry’s pre-broadcast simulation, which public RPCs can fail; the deploy still broadcasts.
Verified against eez-rollupX Git commit 2c19e36; interfaces may move.