How do I actually run an Ink mainnet node right now?
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- shell
- Domain
- distributed-systems, infrastructure
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.
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?
- Dominant language
- Shell
- Stars
- 36.4k
- Forks
- 643
- PR merge metrics
- No merged PRs in 30d
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No contributing guide
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.
More from inkonchain/node
-
Shell scripts initially in CRLF instead of LF (causing execution issues on Linux)Possibly taken @Kewe63 claimed this 22 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
inkonchain/node#73 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
inkonchain/node#84 · 1 reaction ·
-
Difficulty 4/5 3-5 days Newbie friendliness 38/100
inkonchain/node#79 ·
-
testOpen
Difficulty 5/5 Over a week Newbie friendliness 5/100
inkonchain/node#75 ·
-
Snapshot file link is invalidPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 42/100
inkonchain/node#68 · 2 comments · 1 reaction ·
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
mattpocock/skills#1174 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
documentation good first issue hacktoberfest
Difficulty 1/5 Under an hour Newbie friendliness 88/100
-
area/tests theme/ci-dx
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day