Katana Network — External Node Configs

Configuration files and startup scripts for running an external (replica) node on the Katana network, for both Mainnet and the Bokuto testnet.

Katana is an OP Stack L2 chain built on Conduit. Running an external node requires two services: op-reth (execution layer, Conduit fork) and op-node (consensus/rollup layer).

op-geth is deprecated and has reached end-of-support (May 31, 2026). It will not support upcoming hardforks (Glamsterdam). All operators should migrate to op-reth. See the official op-geth deprecation notice for full details.

Reference setup from Conduit: conduitxyz/conduit-optimism-external-node

---

Repository Structure

Each network has two sub-folders:

• op-reth/ — current, supported setup using op-reth + op-node
• legacy/ — old op-geth setup (unsupported, kept for reference only)

.
├── mainnet/
│   ├── op-reth/
│   │   ├── genesis.json                # Mainnet genesis file (op-reth compatible)
│   │   ├── rollup.json                 # Mainnet rollup config
│   │   ├── katana-op-reth.sh           # Start mainnet op-reth (execution layer)
│   │   └── katana-op-node.sh           # Start mainnet op-node (consensus layer)
│   └── legacy/                         # op-geth — UNSUPPORTED
│       ├── genesis.json
│       ├── rollup-snapshot.json
│       ├── genesis-init.sh
│       ├── op-geth-snapshot-edition.sh
│       └── op-node-snapshot-edition.sh
│
└── bokuto/
    ├── op-reth/
    │   ├── genesis.json                # Bokuto testnet genesis file (op-reth compatible)
    │   ├── rollup.json                 # Bokuto rollup config
    │   ├── bokuto-op-reth.sh           # Start Bokuto op-reth (execution layer)
    │   └── bokuto-op-node.sh           # Start Bokuto op-node (consensus layer)
    └── legacy/                         # op-geth — UNSUPPORTED
        ├── genesis.json
        ├── rollup.json
        ├── genesis-init.sh
        ├── bokuto-op-geth.sh
        └── bokuto-op-node.sh

---

Image Versions

Component	Image	Version
op-reth	ghcr.io/conduitxyz/conduit-op-reth (Conduit fork)	v1.0.3
op-node	us-docker.pkg.dev/oplabs-tools-artifacts/images/op-node	v1.16.13

---

Network Details

Property	Mainnet	Bokuto (Testnet)
Chain ID	747474	737373
L1	Ethereum Mainnet	Ethereum (Holesky/Sepolia)
Sequencer RPC	https://rpc.katana.network	—

---

Snapshots

op-reth snapshots (archive node). Conduit only provides op-reth snapshots going forward.

Network	Snapshot URL
Mainnet (katana)	https://storage.googleapis.com/conduit-networks-snapshots/katana/latest.tar
Bokuto (testnet)	https://storage.googleapis.com/conduit-networks-snapshots/katana-bokuto/latest.tar

op-geth snapshots are no longer generated by Conduit.

---

Verify Genesis Files

Before running, verify the genesis file integrity using MD5.

op-reth genesis (current)

# Mainnet (op-reth)
md5 -q mainnet/op-reth/genesis.json
# Expected: b743dc3dd611f6c90bbd192c3d78490c

# Bokuto (op-reth)
md5 -q bokuto/op-reth/genesis.json
# Expected: f2d9950cc289e48c74afddb5706a0e41

Legacy op-geth genesis (for reference)

# Mainnet (legacy)
md5 -q mainnet/legacy/genesis.json
# Expected: 81c916915d3d73af41b65f9e572b5b11

# Bokuto (legacy)
md5 -q bokuto/legacy/genesis.json
# Expected: 895a79b82c0d114972521f530e8661b3

On Linux, use md5sum <file> instead of md5 -q <file>.

---

Key Differences: op-reth vs op-geth

	op-reth (current)	op-geth (legacy)
Genesis init	Automatic on first start via --chain	Manual genesis-init.sh required
Data directory	rethdata/	gethdata/geth/execution-data/
op-node flag	--l2.enginekind=reth required	N/A
Sequencer flag	--rollup.sequencer	--rollup.sequencerhttp
Snapshot format	op-reth tar (no geth/ path)	op-geth tar (mnt/geth/ path)