Consensus Layer

Use Erigon with Caplin or with an external Consensus Layer client

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 is configured to run with an external beacon client.

The embedded consensus layer (Caplin) is still under development and only available for Ethereum and its testnets and Gnosis.

Choosing the Consensus Layer client

A Consensus Layer (CL) client needs to run alongside Erigon to run a full Ethereum node, a Gnosis Chain node and a Polygon node 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:

Caplin, Lighthouse, Lodestar, Nimbus, Prysm, Teku.

*Block validation with Erigon is supported with external beacon nodes.

If you are not validating blocks, it is advisable to run with Caplin, the embedded CL client.

If you are planning to validate blocks , you can use Lighthouse, Prysm or any other supported Beacon Chain, check also Block Production dedicated instructions.

Last updated 14 days ago