The modern Ethereum execution client.

Stable on mainnet since 2025. Written in Rust, audited, and running behind mainnet validators.

Building a rollup? ethrex is also an L2 stack ↓
$ brew install lambdaclass/tap/ethrex
$ ethrex # sync mainnet
ethrex 31.0.0 · mainnet
HEAD
EXEC · MGAS/S
PEERS
BLOCK EXECUTION · LAST 32avg ms
SLOT next block in s

Trusted by mainnet validators.

SOME OF THE OPERATORS RUNNING ETHREX
VALIDATING
VALIDATING
VALIDATING
VALIDATING

…and a growing list of solo stakers and operators. Running ethrex too? Tell us on Telegram.

SNAP SYNC 1h 30m Fresh node to mainnet head 4–8 cores · 32 GB · 1 TB NVMe
EXECUTION 20× Faster in 2026 and we never stop improving
RELEASES Weekly Every one stable drop-in restart · no resync
SECURITY Audited By Least Authority formal verification in progress

Why operators add ethrex to their client mix.

Same Engine API, same keys, same consensus client. What changes is how correlated your risk is with everyone else's.

Diversify your execution layer01

A bug in a supermajority client can finalize a bad chain. Spread validators across clients and one failure stays one failure.

Mainnet in about ninety minutes02

Snap sync with state healing on 4–8 cores, 32 GB of RAM and a 1 TB NVMe disk.

Upgrades are a restart03

A stable release every week. Swap the binary, restart, keep the database. No resync, no missed attestations to speak of.

Tested in public, every day04

EF execution-spec-tests and cross-client Hive suites run in CI with daily published reports. Externally audited by Least Authority.

Run it your way.

Pick the setup you prefer. ethrex works with every consensus client. Full guide in the docs ↗

YOUR CONSENSUS CLIENT
Also packaged by Stereum and Ethereum on ARM, and a first-class client in EthPandaOps' Kurtosis ethereum-package.
— COMMUNITY

Built in the open, with you.

Every line of ethrex is public, and so is the conversation around it. Operators, researchers and contributors talk directly with the engineers who write the client, and that is where the roadmap gets shaped.

01

Open source, open process

Code, issues, roadmap and design discussions all happen in public on GitHub. Contributions are welcome.

02

An active channel

Ask anything on Telegram. The core team is there every day, answering operators and contributors directly.

03

Community calls every week

We meet every week to share progress and hear from the people running ethrex. Join the Telegram to get the invite.

— FAQ

Questions operators ask first.

The engineers who write the client answer on Telegram and GitHub.

— ETHREX L2

Building a rollup? Same client.

ethrex L2 is a ZK rollup stack built on the execution client — sequencer, prover and bridge contracts included. Stablecoin-ready, settles to Ethereum.

Explore ethrex L2 → $ ethrex l2 --dev