explaingit

inkonchain/node

36,622ShellAudience · developerComplexity · 3/5ActiveLicenseSetup · moderate

TLDR

Docker Compose setup to run your own Ink blockchain node, syncing transaction data locally instead of relying on third-party providers.

Mindmap

mindmap
  root((repo))
    What it does
      Runs Ink node locally
      Syncs blockchain data
      Queries transactions
    How it works
      Docker Compose setup
      Execution client layer
      Consensus verification
      Monitoring dashboard
    Use cases
      App developers on Ink
      Infrastructure operators
      Chain verification
    Tech stack
      Docker Compose
      op-geth client
      op-node consensus
      Prometheus Grafana
    Networks supported
      Ink mainnet
      Sepolia testnet
    Setup requirements
      Ethereum L1 RPC
      Docker installed

Things people build with this

USE CASE 1

Run a private Ink blockchain node to query transaction data and smart contract state without relying on third-party RPC providers.

USE CASE 2

Monitor your node's sync progress and health metrics using the built-in Prometheus and Grafana dashboard.

USE CASE 3

Verify the Ink blockchain independently as an infrastructure operator by running your own consensus and execution layers.

USE CASE 4

Build and test applications on Ink with reliable, low-latency access to blockchain data.

Tech stack

Docker ComposeShellop-gethop-nodePrometheusGrafanaInfluxDB

Getting it running

Difficulty · moderate Time to first run · 1h+

Blockchain node syncing requires significant time and bandwidth; initial sync can take hours to days depending on network state.

Use freely for any purpose including commercial, as long as you keep the copyright notice.

In plain English

This repository provides a Docker Compose setup for running an Ink blockchain node. Ink is a Layer 2 blockchain network built on the Optimism (OP Stack) framework, meaning it processes transactions faster and cheaper than Ethereum mainnet, but periodically anchors its state to Ethereum for security. Running your own Ink node means you have a local copy of the blockchain that you can query for transaction data, smart contract calls, and historical state, rather than relying entirely on a third-party RPC provider. The way it works is that Docker Compose starts several services together: an execution client (currently op-geth, a modified version of the standard Ethereum client) that actually processes and stores blocks, an op-node consensus layer component that communicates with Ethereum to verify rollup data, a one-time initialization container (bedrock-init) that sets up the data directory and a shared JWT secret for secure communication between the clients, and monitoring services (Prometheus, Grafana, InfluxDB) that give you a dashboard to watch sync progress. You point the node at an Ethereum L1 RPC endpoint, and it begins syncing Ink's chain by downloading and validating blocks. Both mainnet and testnet (Sepolia) configurations are supported. You would run this if you are a developer building applications on Ink who needs reliable, private access to blockchain data, or an infrastructure operator who wants to verify the chain independently. Note that the current op-geth execution client will be deprecated at the Ethereum Glamsterdam hardfork (May 31, 2026) and a migration to op-reth will be required. The tech stack is Shell scripts for initialization logic, Docker Compose for service orchestration, and the OP Stack (op-geth, op-node) as the underlying blockchain software.

Copy-paste prompts

Prompt 1
How do I set up an Ink blockchain node using this Docker Compose configuration? Walk me through the steps to get it syncing.
Prompt 2
What's the difference between the execution client and consensus layer in this Ink node setup, and why do both need to run?
Prompt 3
I want to monitor my Ink node's sync progress. How do I access the Grafana dashboard and what metrics should I watch?
Prompt 4
My Ink node is running on testnet. How do I switch it to mainnet, and what RPC endpoint should I point it to?
Prompt 5
The explanation mentions op-geth will be deprecated in May 2026. What do I need to do to migrate to op-reth?
Open on GitHub → Explain another repo

Generated 2026-05-18 · Model: sonnet-4-6 · Verify against the repo before relying on details.