The inkonchain/node repository provides a comprehensive Docker Compose setup for running an Ink Node, which is a customized fork of the simple-optimism-node project. Its primary purpose is to enable users to operate a node on the Ink network, leveraging the current op-geth-based stack for execution, along with integrated healthcheck and monitoring services. The repository is designed to simplify the deployment and management of an Ink Node, making it accessible for both mainnet and testnet environments.
Currently, the repository ships with an op-geth execution client, but it is important to note that op-geth support will end on May 31, 2026, following the L1 Glamsterdam hardfork. After this date, nodes running op-geth will not be able to follow the canonical chain, so operators are advised to plan a migration to op-reth, which is not being deprecated. The repository does not yet provide a Compose path for op-reth, but outlines the necessary steps for future support, including validated op-reth services, updated engine endpoints, improved snapshot handling, and revised healthcheck and monitoring configurations.
To run an Ink Node, users must have Docker Engine and Docker Compose v2 installed on Linux, or Docker Desktop on macOS and Windows. Additionally, working L1 execution RPC and L1 beacon API endpoints for the corresponding Ethereum network are required, along with sufficient disk space. Recommended hardware specifications include at least 16GB RAM and 2TB NVME SSD for mainnet, and 16GB RAM with 500GB NVME SSD for testnet, both with a minimum 100 Mbps download speed.
The setup process is straightforward: users clone the repository, copy the environment template, edit the .env file with network-specific parameters, and launch the stack using Docker Compose. The stack includes several services: bedrock-init (for one-time initialization), op-geth (execution client), op-node (rollup node), healthcheck, Prometheus, Grafana, and InfluxDB. The initialization process involves creating a JWT and Bedrock flag, and both op-geth and op-node wait for bedrock-init to signal completion before starting.
Monitoring and validation are integral features of the repository. Users can check service status, review logs, and perform smoke tests on RPC endpoints to ensure proper operation. Grafana is preconfigured for monitoring, accessible locally with default credentials, and provides a dashboard for node health and performance metrics. The repository also includes scripts and instructions for estimating sync progress, troubleshooting common issues, and managing node operations such as stopping, restarting, upgrading, and wiping data.
Snapshot handling is supported for archive nodes, allowing restoration from Gelato ChainSnap indexes. The bedrock-init process verifies snapshot integrity before extraction, ensuring reliable data recovery. The repository provides detailed troubleshooting guidance for issues related to initialization, syncing, connectivity, and peer management, helping operators maintain node stability and performance.
Overall, inkonchain/node is a robust solution for deploying and operating Ink Nodes, offering a user-friendly Docker Compose setup, integrated monitoring, and clear migration guidance for future execution client changes. It is suitable for both new and experienced node operators seeking to participate in the Ink network with minimal friction.
