erigontech /erigon

Ethereum implementation on the efficiency frontier

★ 3,634⑂ 1,581👁 56⑃ 20,414● 5,713▤ 257
GoLGPL-3.0Created 2019-05-27docs.erigon.tech
Download: v3.8.1v3.8.1 ↓3.8.12026-10-23
3,634
stars
1,581
forks
56
watchers
20,414
prs
5,713
issues
257
releases

README

Erigon







Erigon is an implementation of Ethereum (execution layer with embeddable consensus layer), on the efficiency
frontier.

Download
| Documentation
| Blog

This README is for people working on the repository. Everything about operating a node — install methods,
flags, pruning modes, ports, monitoring, staking — is on the documentation site.

Documentation
=============

The Erigon documentation answers most questions. Useful starting points:

 Installation — binaries, Docker, Linux/macOS, Windows, ARM
 Hardware requirements — disk, RAM, CPU, bandwidth
 Pruning modes — archive, full, blocks, minimal
 CLI reference — every flag, config files, env vars
 Default ports and Security
 Interacting with Erigon — JSON-RPC, GraphQL, gRPC namespaces
 Creating a dashboard — Prometheus and Grafana
 Upgrading — versions and snapshot formats

In-depth links are marked by the microscope sign (🔬) 

Usage
=====

 Erigon3 changes from Erigon2

- Initial sync doesn't re-exec from 0: downloading 99% LatestState and History
- Per-Transaction granularity of history (Erigon2 had per-block). Means:
    - Can execute 1 historical transaction - without executing it's block
    - If account X change V1-V2-V1 within 1 block (different transactions): debug_getModifiedAccountsByNumber return
      it
    - Erigon3 doesn't store Logs (aka Receipts) - it always re-executing historical txn (but it's cheaper)
- Validator mode: added. --internalcl is enabled by default. to disable use --externalcl.
- Store most of data in immutable files (segments/snapshots):
    - can symlink/mount latest state to fast drive and history to cheap drive
    - chaindata is tens of gb (22gb on an archive mainnet node). It's ok to rm -rf chaindata. (to prevent grow: recommend --batchSize  🔬 Detailed explanation is DEV_CHAIN.

For developers
==============

 Building

Toolchain: Go = 1.26, GCC 11+ or Clang 13+, 64-bit architecture. On Linux, kernel  v4.

On x86-64 the build targets the x86-64-v2 baseline (requires SSE4.2, POPCNT). Intel Nehalem (2008) and AMD
Bulldozer (2011) or newer qualify; older hardware is not supported.

sh
git clone https://github.com/erigontech/erigon.git
cd erigon
make erigon


Binaries land in ./build/bin. Use -j to parallelise the build. Packaged binaries, Docker images and the
per-platform install steps are on the
installation page; to build a specific release rather than main,
check out its tag.

On Windows, build natively (Chocolatey, MinGW, and the MinGW anti-virus false-positive workaround) or under WSL2:
Native compilation and
WSL.

 Executables

make erigon builds the node; make all builds the full suite into ./build/bin. make help lists every target.

| Command      | Description                                                                                      |
|--------------|--------------------------------------------------------------------------------------------------|
| erigon     | The node: execution layer with the embedded consensus layer (Capl

Top issues

Discussions

Latest release

v3.8.1 v3.8.1 2026-10-23
Erigon v3.8.1 — Watery Whiskers

Erigon 3.8.1 unschedules Glamsterdam on Hoodi and improves block validation, validator reliability,
and block production. Hoodi operators running 3.8.0 must upgrade before 26 October 2026, 17:42:48 UTC.
This release is recommended for all users. Non-archive nodes can upgrade from 3.8.0 without a re-sync.
Beacon API metadata consumers and Caplin archive operators should read the breaking changes and upgrade notes below.

 Highlights

- Glamsterdam on Hoodi postponed. Removes the Amsterdam execution-layer and Gloas Caplin activations at epoch 132352 and 

Snapshot: 2026-11-16T09:23:14Z · Data license Apache-2.0 · JSON