What

Gensyn Mainnet (chain ID 685689) is moving its sequencer and RPC infrastructure from Alchemy to Conduit. One week later the Karst hardfork (OP Stack upgrade 19) activates. Both changes are covered by one configuration update. Apply it once, before the cutover, and nothing further is needed for Karst.

Chain ID, contract addresses, chain state, token addresses and bridge contracts do not change.

When

Event Date Unix time
Sequencer cutover Alchemy → Conduit Monday, 23 November 2026, 13:30 UTC 1795440600
Karst hardfork activation Monday, 30 November 2026, 13:30:01 UTC 1796045401

At cutover, expect about 10 minutes with no new blocks while sequencing moves to Conduit. Transactions submitted in that window are processed once the chain resumes. Karst activation itself causes no downtime.

Who needs to act

<aside> 🔴

You run a Gensyn Mainnet node (op-node / op-reth): follow Conduit's guide below and complete it before 23 November, 13:30 UTC. A node that is not updated loses transaction forwarding and block gossip at cutover and falls out of sync at Karst activation.

</aside>

<aside> 🟡

You only use an RPC endpoint (no node): switch to https://rpc-gensyn-mainnet.t.conduit.xyz (public, 25 req/s) or a keyed URL from app.conduit.xyz/rpc-keys before 23 November, 13:30 UTC. Alchemy's Gensyn endpoints stop at cutover.

</aside>

<aside> 🟢

You only hold or trade the token, or integrate via a wallet or an Ethereum listing: no action needed.

</aside>

Node operators: what to do

Follow Conduit's guide, which has the versions, config files with checksums, peers, flags and a Docker Compose quickstart:

Gensyn Mainnet — External Node Operator Required Actions

Four points to add to that guide:

  1. Do everything in one go, before 23 November 13:30 UTC. The guide allows the new rollup.json / genesis.json to be deployed any time before 30 November; we ask you to deploy them together with the rest so you touch your node once.
  2. Transaction forwarding needs no API key. Set --rollup.sequencer-http=https://rpc-gensyn-mainnet.t.conduit.xyz. Switch to it before cutover: until then it forwards to Alchemy's sequencer, from cutover to Conduit's, so nothing changes on the day. Use a keyed URL only if you also serve reads through it.
  3. Keep your existing data directory. No resync is needed. If you do need a fresh node, Conduit's snapshot opens only on conduit-op-reth v2.5.1 or upstream op-reth v2.6.0-2.
  4. Verify before restarting: grep -l 1796045401 rollup.json genesis.json must print both filenames. A stale genesis file is the most common failure we have seen.

Expected before 23 November: op-node logging failed dials to Conduit's static peer on port 9222. It opens at cutover and op-node connects on its own.

What if you don't apply the new configuration