🦦
Erigon 2 Documentation
  • Welcome to Erigon 2
    • Disclaimer
    • Project Links
  • ELI5 NODES
    • How to run an Ethereum node
    • How to run a Gnosis Chain node
    • How to run a Polygon node
  • Basic usage
    • Getting started
      • Linux and MacOS
      • Windows
      • Docker
    • Usage
      • Type of Node
    • Upgrading from a previous version
    • Supported Networks
    • Default Ports and Firewalls
    • Otterscan
    • Wallet
  • Advanced Usage
    • Configure Erigon
    • Consensus Layer
      • Prysm
      • Lighthouse
      • JWT secret
      • Block production
    • Options
    • RPC daemon
    • TxPool
    • Sentry
    • Downloader
    • TLS Authentication
    • ❔FAQ
    • External resources
      • Erigon on a Raspberry Pi 4
  • DIAGNOSTIC TOOL
    • Introduction
    • Installation
    • Setup
    • User Interface
  • About
    • Contributing to Erigon
    • Donate
    • License
    • Privacy policy
Powered by GitBook
On this page

Was this helpful?

  1. Advanced Usage

Consensus Layer

How to run Erigon 2 with an external Consensus Layer client

Last updated 2 months ago

Was this helpful?

Historically, an Execution Layer (EL) client alone was enough to run a full Ethereum node. However, as Ethereum has moved from proof-of-work (PoW) to proof-of-stake (PoS) based consensus with "The Merge", a Consensus Layer (CL) client needs to run alongside the EL to run a full Ethereum node, a Gnosis Chain node or a Polygon node.

The execution client listens to new transactions, executes them in the Ethereum Virtual Machine (EVM), and holds the latest state and database of all current Ethereum data.

The consensus client, also known as the Beacon Node or CL client, implements the Proof-of-Stake consensus algorithm, which enables the network to achieve agreement based on validated data from the execution client. Both clients work together to keep track of the head of the Ethereum chain and allow users to interact with the Ethereum network.

By default, Erigon 2 is configured to run with an external beacon client.


Choosing the Consensus Layer client

A Consensus Layer (CL) client needs to run alongside Erigon to run a , a and a and its respective testnets. Basically, without a CL client the EL will never get in sync. See below which Beacon node for which chain you can run along with Erigon:

, , Lodestar, Nimbus, Teku.

See also .

*Block validation with Erigon is with external beacon nodes.

, , Lodestar, Nimbus, Teku.

See also

If you are planning or not to validate blocks , you can use , or any other supported Beacon Chain. Check also page.

full Ethereum node
Gnosis Chain node
Polygon node
Prysm
Lighthouse
https://ethereum.org/en/developers/docs/nodes-and-clients/client-diversity/#consensus-clients
Prysm
Lighthouse
https://docs.gnosischain.com/node/manual
Lighthouse
Prysm
Block Production
supported
Cover

Prysm

Running Erigon with Prysm as external CL

Cover

Lighthouse

Running Erigon with Lighthouse as external CL