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

Checkpointz

Checkpointz is a self-hosted Go service that provides an endpoint for Ethereum Beacon Chain checkpoint sync, serving block data in light mode and block and state data in full mode.

Explore the practical guide ↓

Independent OpenViST project profile, based on linked sources.

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

Practical overview

When it fits

Use it when operating a self-hosted checkpoint endpoint for Ethereum beacon nodes, selecting light mode for block cross-referencing or full mode when state requests must also be served.

Who it is for

  • Operators who want to provide a checkpoint-sync endpoint for Ethereum beacon nodes.
  • Beacon-node operators who need a checkpoint state provider or a way to cross-reference checkpoint block and epoch data.

Documented uses

  • Serve block data that users can compare against checkpoint information obtained elsewhere.
  • Provide block and state data for beacon nodes performing checkpoint sync.
  • Display historical epoch boundaries with associated state and block roots.
  • Expose Prometheus metrics and show configured upstream information.
Before you choose

Requirements & limits

The project documents release binaries, Docker images and Kubernetes deployment through Helm. It is open source under GPL-3.0.

  • Light mode serves blocks for cross-reference; full mode serves blocks and state for checkpoint syncing.
  • The project supports Prysm, Lighthouse, Nimbus, Lodestar and Teku; Teku full mode requires archive data storage and a resync from genesis.
  • A new finalized epoch is served only when more than half of configured upstream beacon nodes agree.
  • State cache limits affect memory use because states are large.
  • The project warns that it is in heavy development and does not recommend using it with a beacon node attached to a validator.

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

Configure Checkpointz with a beacon-node upstream

Create the documented YAML configuration for a Checkpointz instance using one upstream beacon node.

Before you start

  • A Checkpointz installation or release binary.
  • A reachable beacon node and its address.
  • A YAML configuration file.

Steps

  1. Create a YAML file with a beacon.upstreams entry.

  2. Set the upstream name, address and dataProvider value; the example uses name remote, address http://localhost:5052 and dataProvider: true.

  3. Start Checkpointz with --config followed by the configuration file path.

Expected outcome

Checkpointz starts using the configured upstream; the documented default mode is light.

Guide limitations

  • The project warns that it is in heavy development and advises against use with a beacon node attached to a validator.
  • This configuration does not enable full mode or establish that the service has been tested in a particular environment.
Documentation 1 ↗
Evidence and transparency

Sources & review

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