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 ↓Trusted by mainnet validators.
SOME OF THE OPERATORS RUNNING ETHREX
…and a growing list of solo stakers and operators. Running ethrex too? Tell us on Telegram.
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.
A bug in a supermajority client can finalize a bad chain. Spread validators across clients and one failure stays one failure.
Snap sync with state healing on 4–8 cores, 32 GB of RAM and a 1 TB NVMe disk.
A stable release every week. Swap the binary, restart, keep the database. No resync, no missed attestations to speak of.
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 ↗
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.
Open source, open process
Code, issues, roadmap and design discussions all happen in public on GitHub. Contributions are welcome.
An active channel
Ask anything on Telegram. The core team is there every day, answering operators and contributors directly.
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.
Questions operators ask first.
The engineers who write the client answer on Telegram and GitHub.
4–8 cores, 32 GB of RAM and a 1 TB NVMe disk. Snap sync reaches the head of mainnet in about an hour and a half.
All of them — ethlambda, Lighthouse, Prysm, Teku, Nimbus, Lodestar and Grandine. They talk over the standard Engine API on port 8551 with a shared JWT secret.
Start ethrex with the same JWT secret, point your consensus client at it and let it snap-sync. Validator client and keys stay as they are — or run ethrex on a second machine first and fail over.
Yes. MEV-Boost connects to your consensus client, so it is independent of the execution client you run.
Stable releases ship weekly. Upgrading is a drop-in restart that keeps the database, so staying current is a non-event.
Yes. Least Authority audited ethrex in 2026 and every issue they found has been addressed. We are now working on formal verification. Hive and execution-spec-tests results are published daily.
GitHub issues or the ethrex Telegram. The engineers who write the client answer there directly.
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.
