How do I actually run an Ink mainnet node right now?
Open
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 36.5k
- Forks
- 643
- PR merge metrics
- No merged PRs in 30d
Description
Trying to run an Ink mainnet node and hitting dead ends on every path:
NODE_TYPE=archivefails —ink.snapshots.gelato.clouddoesn't resolve (NXDOMAIN),
so no snapshot download.NODE_TYPE=fullwith 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?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with envs/ink-mainnet/op-node.env and verify the documented bootnodes and port 30305 against the current Ink mainnet setup. Check whether a working snapshot or reachable op-reth peers are identified; done means documenting a reproducible path to a synced mainnet node.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- distributed-systems, infrastructure
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100