Skip to main content
Bootnodes, container images, and downloadable artifacts needed to run a Celo L2 node on each network.
You don’t need to supply genesis.json or rollup.jsonThe recommended celo-l2-node-docker-compose setup selects the chain by name: op-node loads the rollup config from the superchain registry with --network (celo-mainnet / celo-sepolia), and op-reth loads the chain spec — genesis included — with --chain (celo / celo-sepolia). The genesis.json and rollup.json files below are listed for reference and for custom or from-source setups.

Mainnet

  • op-reth snapshots — published at snapshots.celo.org; a mainnet node must bootstrap from one (OP_RETH__SNAPSHOT=true) for the pre-L2 history (see Run a node)
  • Rollup deploy config
  • L1 contract addresses
  • L2 allocs
  • rollup.json
  • Genesis
  • Full migrated chaindata — geth-format, for legacy op-geth full/archive sync
  • P2P peers
    • Execution-client bootnodes, used by op-reth (OP_RETH__BOOTNODES) and op-geth (--bootnodes):
    • op-node bootnodes, to be used with op-node --p2p.bootnodes flag:
  • Container images:

Celo Sepolia

  • op-reth snapshots — published at snapshots.celo.org; optional, enable with OP_RETH__SNAPSHOT=true to skip syncing from genesis (see Run a node)
  • L1 contract addresses
  • rollup.json
  • Genesis
  • P2P peers:
    • Execution-client bootnodes, used by op-reth (OP_RETH__BOOTNODES) and op-geth (--bootnodes):
    • op-node static peers, to be used with op-node --p2p.bootnodes flag:
  • Container images: