Required actions and configuration for external nodes on gensyn-mainnet (chain ID 685689) ahead of its RaaS migration from Alchemy to Conduit and the Karst hardfork.

<aside> ⏰

Required actions

Before cutover (Monday, November 23, 2026, 13:30 UTC), operators must:

Before Karst activation (Monday, November 30, 2026, 13:30:01 UTC):

Timeline

Event Date Exact timestamp
Sequencer cutover from Alchemy to Conduit Monday, November 23, 2026 13:30 UTC · 1795440600
Karst hardfork activation Monday, November 30, 2026 13:30:01 UTC · 1796045401

Until cutover

<aside> 💡

To keep nodes at the tip until cutover, run Alchemy and Conduit peers side by side on op-node:

enode://3fcc32f6bc5bd6ab8fa458d1bf4dd020ed59369948b739e360978bc090dab29bb5481e3c5efd577d95c273b7ad4413bcdde0a2c2b7ba85313be85a5dd4efeed0@51.96.160.112:0?discport=30301,enode://8cf1d63797726eef41c2682b7ce037093057468b330a4e98e9e6079fe4148a53c4282719050a022dfa7d0ca4749f5d19621a20968ec6cafaa89c704841b55a01@16.63.220.126:0?discport=30301

The Alchemy entries can be removed after cutover.

</aside>

At cutover

<aside> ⚠️

Expect about an hour with no new blocks, starting Monday, November 23, 2026, 13:30 UTC.

</aside>

Quickest setup

The quickest and easiest way to run a node is conduitxyz/conduit-optimism-external-node. It runs op-node and op-reth with Docker Compose. make setup downloads rollup.json and genesis.json, configures the static peer and EL peer, and optionally restores the snapshot.

git clone https://github.com/conduitxyz/conduit-optimism-external-node.git
cd conduit-optimism-external-node
cp .env.example .env

Set these in .env:

OP_NODE_L1_ETH_RPC=<ethereum-mainnet-rpc>
OP_NODE_L1_BEACON=<ethereum-mainnet-beacon-rpc>
SNAPSHOT_ENABLED=true  # new nodes only
GCP_PROJECT=<billing-project-id>

Run setup: