You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
How do I actually run an Ink mainnet node right now? #87
Trying to run an Ink mainnet node and hitting dead ends on every path:
NODE_TYPE=archive fails — ink.snapshots.gelato.cloud doesn't resolve (NXDOMAIN),
so no snapshot download.
NODE_TYPE=full with op-geth technically syncs from genesis, but op-geth can't
follow the chain post-Karst anyway.
Tried migrating to op-reth manually (v2.2.5 + op-node v1.18.2) since that's the
recommended path now, but it has zero P2P peers (using the bootnodes from envs/ink-mainnet/op-node.env, port 30305 — all unreachable) so it never
backfills state.
What's the actual working way to bring up a synced mainnet node right now? Is there
a current snapshot, or working op-reth peers?
op-geth can't follow the chain post-Karst — fix: bump node images to Karst-capable releases #95 bumps op-node v1.13.2 → v1.19.7 and op-geth v1.101503.4 → v1.101702.2. Karst lands in op-node v1.17.0 / op-geth v1.101609.x, so the pinned images currently predate it; both target tags exist in the public OP Labs registry, and v1.19.7's embedded superchain registry still carries Ink with keep_karst_upgrade_gas = true, so derivation matches Ink's history.
Point 3 (op-reth bootnodes unreachable) isn't something I can verify from here — if #95 lands, the op-geth path in this template should work again without needing op-reth.
Activity
fix(init-bedrock): actionable errors and a snapshot URL override
Alicepoltora commentedon Oct 5, 2026
Opened fixes for points 1 and 2:
archive / NXDOMAIN — fix(init-bedrock): validate node type and survive the decommissioned snapshot indexes #93 makes
NODE_TYPE=archivefail with an actionable message instead of a curl resolver error, and adds aBEDROCK_TAR_DOWNLOADoverride in.envso you can pointbedrock-initat your own geth datadir tarball (it must ship a matching<url>.sha256; verification is unchanged). docs: mark Gelato snapshot indexes as decommissioned #94 marks the dead indexes as decommissioned in the README.op-geth can't follow the chain post-Karst — fix: bump node images to Karst-capable releases #95 bumps op-node
v1.13.2 → v1.19.7and op-gethv1.101503.4 → v1.101702.2. Karst lands in op-node v1.17.0 / op-geth v1.101609.x, so the pinned images currently predate it; both target tags exist in the public OP Labs registry, and v1.19.7's embedded superchain registry still carries Ink withkeep_karst_upgrade_gas = true, so derivation matches Ink's history.Point 3 (op-reth bootnodes unreachable) isn't something I can verify from here — if #95 lands, the op-geth path in this template should work again without needing op-reth.
All three are open PRs; happy to adjust anything.