OpenViSTAI · Agents · Blockchain · Crypto
Submit a project
Menu
Infrastructure

Chainplane

Chainplane is an Apache-2.0-licensed Go Kubernetes operator that deploys and manages blockchain full nodes using ChainInstance custom resources. It automates node resources and configuration, monitors chain health, supports snapshot bootstrapping and can recover degraded nodes.

Explore the practical guide ↓

Independent OpenViST project profile, based on linked sources.

Chainplane — OpenViST project profile in Infrastructure.
OpenViST project illustration. See the linked sources for product details.
Understand the project

Practical overview

When it fits

Use Chainplane when you already operate a Kubernetes cluster and want to manage blockchain full nodes through declarative resources, with health monitoring and lifecycle automation.

Who it is for

  • Platform teams running Kubernetes clusters that host blockchain full nodes.
  • Node operators seeking declarative provisioning, health reporting and lifecycle automation across multiple chains.

Documented uses

  • Define blockchain nodes as Kubernetes resources and have the operator create their workloads and persistent storage.
  • Monitor sync progress, peer counts and node health indicators.
  • Bootstrap nodes from MinIO-based snapshots and automatically restart nodes that remain degraded.
Before you choose

Requirements & limits

  • The README lists support for 102 chains, but some adapters require an explicitly supplied container image.
  • The operator needs access to a Kubernetes cluster; the documented prerequisites include Go 1.23+ and kubectl 1.25+.
  • The v1alpha2 CRD is alpha software and may change in minor releases.
  • Node resource and storage settings must be planned for the selected chain and cluster.

Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.

Source-based practical guide

Install Chainplane with Helm

Install the Chainplane operator into a Kubernetes cluster using the documented Helm OCI chart.

Before you start

  • Go 1.23+
  • kubectl 1.25+
  • Access to a Kubernetes cluster

Steps

  1. Install the chart from oci://ghcr.io/tazhate/charts/chainplane at version 0.2.3.

  2. Set the namespace to chainplane-system and create the namespace as part of the Helm installation.

Expected outcome

The Helm installation command is configured to install Chainplane in the chainplane-system namespace.

Guide limitations

  • The API is v1alpha2 and may have breaking changes in minor releases.
  • The project cautions against production use without thorough testing in the target environment.
Documentation 1 ↗
Source-based practical guide

Define and observe a Bitcoin node

Create a Bitcoin mainnet ChainInstance and inspect its reported lifecycle and sync status.

Before you start

  • A Kubernetes cluster with Chainplane installed
  • kubectl 1.25+
  • A ChainInstance manifest specifying chain, network, storage and resource requests

Steps

  1. Create a manifest with apiVersion chains.chainplane.io/v1alpha2 and kind ChainInstance.

  2. Set the chain to bitcoin and network to mainnet, and configure storage and resource requests.

  3. Apply the manifest with kubectl apply -f bitcoin-node.yaml.

  4. Watch resources with kubectl get chaininstances -w.

Expected outcome

The ChainInstance status can report its phase, block height, peers, sync progress and estimated time.

Guide limitations

  • The example manifest uses a 600Gi volume and a fast-nvme storage class; suitable capacity and storage configuration depend on the cluster.
  • The README labels the software alpha and advises thorough testing before production use.
Documentation 1 ↗
Evidence and transparency

Sources & review

Official repository ↗
Source record details
Source availability
Active
Sources checked
13 October 2026
Original website title
tazhate/chainplane · Official homepage title · retained in its source language
How we review sourcesSuggest a correction