The inkonchain/node repository is a Docker Compose setup for running an Ink node on an op-geth-based stack, forked and customized from the simple-optimism-node project. The repository provides a complete operational framework including supporting healthcheck and monitoring services, making it the primary resource for node operators looking to participate in the Ink network.
The repository is written primarily in Shell and serves as a practical runbook for deploying and maintaining Ink nodes. According to GitGenius activity tracking, the repository has seen moderate engagement with a median issue and pull request response latency of 148.8 hours and a mean latency of 300.9 hours across 21 tracked items. The most active contributors include victorcheeney with 14 events, qedgardo with 4 events, and MMcyclic with 3 events. The repository shares overlapping contributors with base/node, airbytehq/airbyte, and anoma/anoma, indicating cross-project collaboration within the blockchain infrastructure space.
The current implementation ships an op-geth execution client, though the repository explicitly acknowledges this as a transitional state. According to Optimism's deprecation timeline, op-geth support ends on May 31, 2026, and nodes still running it at the L1 Glamsterdam hardfork will be unable to follow the canonical chain. The repository documentation emphasizes that production and long-lived node operators should begin planning migration to op-reth immediately, running it in parallel with existing infrastructure and validating it over meaningful windows before the hardfork deadline. The repository does not yet ship an op-reth Compose path, with outstanding work needed in service configuration, engine endpoint updates, snapshot handling, healthcheck and monitoring updates, and environment variable naming conventions.
Hardware requirements vary by network tier. Mainnet nodes require 16GB or more RAM, 2TB SSD storage with NVME recommended, and 100 Mbps or faster download speeds. Testnet nodes require 16GB or more RAM, 500GB SSD with NVME recommended, and the same 100 Mbps minimum download speed. The setup process begins with cloning the repository, copying the environment template, and configuring network selection between ink-sepolia and ink-mainnet, along with node type selection between full and archive modes.
The Docker Compose stack orchestrates multiple services including bedrock-init for one-time initialization, op-geth as the execution client, op-node as the rollup node, healthcheck for monitoring, prometheus for metrics collection, grafana for visualization, and influxdb for time-series data storage. The repository provides comprehensive operational guidance including startup validation procedures, RPC endpoint testing, sync status monitoring, and troubleshooting workflows. Grafana dashboards are preloaded with a Simple Node Dashboard accessible at localhost:3000 with default credentials.
The repository includes detailed monitoring capabilities through a progress.sh script that estimates remaining sync time using Foundry's cast tool, though this requires local Foundry installation. Troubleshooting documentation addresses common scenarios including bedrock-init behavior on different node types, snapshot download and verification processes, block number progression during bootstrap, and peer connectivity issues. The documentation emphasizes that certain behaviors like eth_blockNumber remaining at 0x0 during early full node bootstrap are expected and should be validated through alternative metrics like optimism_syncStatus and healthcheck indicators rather than interpreted as failures.
