erigon: An Ethereum execution layer with an embeddable consensus layer.
What problem it solves
Ethereum node operators need an execution client that can integrate consensus functionality while supporting bulk block processing, historical queries, validator workloads, and flexible deployment configurations. Repository contributors also need guidance for building, testing, configuring, and extending the implementation.
Key features
Embedded and external consensus layers — The node includes an embedded consensus layer called Caplin and can also operate as an execution layer for external consensus layer clients.
Source: README
Batch-oriented block handling — The execution design handles many blocks simultaneously and sorts and processes data in batches rather than following a one-block-at-a-time Engine API delivery model.
Source: README
Transaction-level history — Historical history has per-transaction granularity, allowing an individual historical transaction to be executed without executing its containing block.
Source: README
Flexible component deployment — Core components can run within the main node or as independent processes, including the RPC daemon, snapshot downloader, sentry, and transaction pool.
Source: README, docker-compose.yml
Proof-of-stake block production — Block production is supported for Ethereum and Gnosis Chain, and the project includes validator mode alongside its execution capabilities.
Source: README
Quick start
Copied verbatim from the project's README.
git clone https://github.com/erigontech/erigon.git
cd erigon
make erigon# please use git branch name (or commit hash). don't use git tags
go get github.com/erigontech/erigon@main
go mod tidyWho it may suit
This may suit Ethereum node operators, validator operators, and developers who need to build, configure, test, or embed an execution client with consensus-layer integration.
Topics to discuss
Which deployment configuration is most useful for a given node operation: integrated components or independent processes?
How should pruning modes and immutable data storage be documented for operators with different archival needs?
Which community-maintained tools and interfaces should be prioritized around Caplin, validator operation, and local development?
Written by ReadmeX AI from the project's README, source and public GitHub data; it may contain mistakes.
Read the original README https://github.com/erigontech/erigon#readme
ReadmeX opened this community for a trending project; it is not run by the project. Maintainers can claim it from the community page.
Comments
…