OpenViSTAI · Agents · Blockchain · Crypto
Submit a project
Menu
Developer Tools

Beacon Kit

Beacon Kit is Berachain’s Go-based consensus client and a modular framework for building EVM consensus clients. It implements the Ethereum consensus-layer specification with Berachain-specific modifications and uses modified CometBFT for consensus. It connects to the separate Bera-Reth execution client through the Engine API.

Explore the practical guide ↓

Independent OpenViST project profile, based on linked sources.

Beacon Kit — OpenViST project profile in Developer Tools.
OpenViST project illustration. See the linked sources for product details.
Understand the project

Practical overview

When it fits

Use Beacon Kit when developing consensus-client software for EVM-based systems or when working with Berachain’s consensus layer. Its repository also provides documented single-node and Kurtosis-based multinode local-devnet workflows.

Who it is for

  • Developers building or extending EVM consensus clients.
  • Developers working on Berachain consensus-client functionality.
  • Engineers exploring Berachain’s two-client architecture or local development networks.

Documented uses

  • Build an EVM consensus client using a modular framework.
  • Develop Berachain consensus-client and validator functionality.
  • Start the documented local devnet with Beacon Kit and Bera-Reth.
  • Start a multinode local devnet using the documented Kurtosis target.
Before you choose

Requirements & limits

The repository is public and identified as open source.

  • Beacon Kit is the consensus client; Berachain’s Bera-Reth is a separate required execution client for the documented local quick start.
  • The quick-start prerequisites are Docker, Go, and Foundry.
  • The documented local devnet uses chain ID 80087; the multinode workflow uses Kurtosis.
  • The repository includes consensus, state-transition, validator, execution-integration, storage, network-configuration, and REST API code.
  • The README describes Berachain-specific consensus differences, including timeout-based rounds, sequential block heights, and commit-based finality.

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

Start the documented local development network

Start Beacon Kit’s consensus client and then its Bera-Reth execution client for the local devnet.

Before you start

  • Docker
  • Go
  • Foundry
  • Two terminals
  • The Beacon Kit repository and its documented make targets

Steps

  1. In the first terminal, run the command below to start the consensus client and generate the execution genesis file.

    Documented command
    make start

  2. After beacond is running, use the second terminal to run the command below for the execution client.

    Documented command
    make start-reth

Expected outcome

The README describes a local devnet with chain ID 80087 and a development account preloaded with the native token.

Guide limitations

  • The guide documents the local quick-start flow only; it does not provide detailed troubleshooting or configuration steps.
  • Bera-Reth is required as a separate execution client.
  • The repository instructs developers to consult the Kurtosis README for multinode devnet configuration.
Documentation 1 ↗
Source-based practical guide

Start a multinode local devnet

Use the documented Kurtosis target to start a multinode local devnet.

Before you start

  • Kurtosis
  • The Beacon Kit repository

Steps

  1. Run the command below.

    Documented command
    make start-devnet

  2. Consult kurtosis/README.md in the repository for configuration and usage details.

Expected outcome

The repository documents a Kurtosis-based multinode local devnet workflow.

Documentation 1 ↗
Evidence and transparency

Sources & review

Official repository ↗
Source record details
Source availability
Active
Sources checked
16 October 2026
Original website title
berachain/beacon-kit · Official homepage title · retained in its source language
How we review sourcesSuggest a correction