Ethrex is an open-source Ethereum execution client written in Rust, aimed at developers and infrastructure engineers who want a minimalist, modular node that is designed from the ground up to work with zero-knowledge proving. It is free to use and is built around the idea that the same execution code should serve both Layer 1 and Layer 2 environments.
Unlike general-purpose clients that were built before zero-knowledge proving became practical, Ethrex keeps its codebase small and structures its data with proving costs in mind. That makes it a natural fit for teams experimenting with validity proofs, rollup operators, and researchers who need predictable, auditable behavior when running alongside provers.
What Is an Ethereum Execution Client?
An Ethereum node has two conceptual halves. The consensus layer decides which blocks are final, while the execution layer processes transactions, updates account balances and storage, and runs smart contract code. Ethrex is an execution client, meaning it is responsible for the second half.
Running an execution client means your machine independently checks every transaction against the protocol rules instead of trusting a third party's report. That independence is the core value of operating your own node.
Who Is Ethrex For?
Ethrex is most relevant to people working close to the protocol rather than end users looking for a wallet. Typical readers include:
- Rollup and Layer 2 teams that need an execution engine they can pair with zero-knowledge provers.
- Researchers studying validity proofs who want a compact, readable Ethereum implementation.
- Infrastructure engineers evaluating clients for diversity across their own stack.
- Developers who want to understand Ethereum execution by reading a clean Rust codebase.
How Zero-Knowledge Proofs Fit Into Block Execution
A zero-knowledge proof lets one party demonstrate that a computation was carried out correctly without revealing every intermediate step. In the context of Ethereum, a prover can take a block, run its execution inside a zkVM, and produce a proof that the resulting state transition follows the rules.
Verifying that proof is much cheaper than re-executing the whole block. This is why ZK-native clients matter: the execution trace they produce has to be efficient to prove, and that is the problem Ethrex is built around.
Proving still carries real computational cost, so the choice of data structures and the size of the execution code both affect how practical a setup is.
Why Rust Matters for a Node Implementation
Rust offers memory safety without a garbage collector, which matters for long-running software that handles financial state. Its strict compiler catches many classes of bugs before the code ever runs, and its performance is close to C and C++.
For a protocol client, predictable performance and fewer memory-related crashes are valuable qualities. Ethrex's choice of Rust follows a trend across blockchain infrastructure, where new implementations increasingly favor the language.
Key features
Multiple zkVM integrations
Proving-friendly data structures
Lightweight codebase
Multi-prover rollup architecture
Proof aggregation
One client for L1 and L2
Supported coins
The project's documentation mentions Ethereum (ETH) as the base network, along with rollup-oriented environments such as Polygon, Arbitrum and Optimism. Because Ethrex works as an execution client for Ethereum-compatible networks, it is best understood as infrastructure for those chains rather than a tool for holding or trading individual tokens.
How to install Ethrex on Windows
- 1
Get the official build
Download the release from the official project resources, which include the GitHub repository at github.com/lambdaclass/ethrex and its Releases page. Stick to these sources and avoid mirrors you cannot verify.
- 2
Verify the file
Compare the SHA-256 checksum of the downloaded file against the value published alongside the release, or check the project's signature if one is provided. A mismatch means the file should not be run.
- 3
Check the platform support
Windows builds are mentioned as likely available, but support depends on the specific release. Review the release notes on GitHub to confirm a Windows artifact exists for the version you want.
-
Install and configure
Extract or install the program into a dedicated folder, then follow the configuration guidance in the project documentation. Point it at the network and data directory you intend to use, and make sure there is enough disk space for chain data before starting a sync.
How to use Ethrex
Running an execution client is mostly a matter of configuring it correctly and letting it sync. The exact commands depend on the release, so always follow the documentation that ships with your version. The general workflow looks like this.
- Decide the role: run it as a standalone L1 execution node, or as the execution component in a Layer 2 or prover setup.
- Prepare a data directory on a drive with enough free space for chain data, and make sure it is on fast storage.
- Configure the target network and any RPC endpoints you need, keeping them bound to localhost unless you have a specific reason to expose them.
- Start the client and let it synchronize with the network. Monitor logs for errors during the initial sync.
- If you are connecting a prover, configure the zkVM backend you intend to use, such as SP1 or RISC Zero, and test it on a few blocks before running it continuously.
- Keep the client updated by watching the Releases page, and check release notes for breaking changes before upgrading.
Pros & cons
- Free and open source, with the source code publicly available for review
- Written in Rust, which favors memory safety and performance
- Designed for zero-knowledge proving from the start
- Supports several zkVMs, so teams are not locked to one prover
- Same client for L1 and L2 simplifies debugging and testing
- Compact codebase that is easier to read and reason about
- Targets developers and infrastructure teams rather than casual users
- Version labels such as release candidates suggest the software is still maturing
- Windows support is described as likely rather than guaranteed, so you must verify each release
- Running a node and proving blocks require significant hardware and storage
- Documentation may assume familiarity with Ethereum internals and zero-knowledge tooling
Is Ethrex safe?
Download Ethrex only from the official GitHub repository or its Releases page, and avoid third-party sites that repackage the software. Before running any binary, compare its SHA-256 checksum with the value published by the developers, or verify a signature where one is offered. A file that fails verification should be deleted, not executed.
Never enter a seed phrase or private key into a third-party website or a program you have not verified, and do not share wallet credentials with anyone offering to help you set up a node. Keep the node's RPC interfaces restricted to trusted networks. Check the project's latest activity on GitHub before deploying it, and confirm the version you install is the one you intend to run.
- Official source only. Download from github.com/lambdaclass/ethrex. Ignore ads and lookalike domains.
- Check the SHA-256. Compare the installer hash with the value the developer publishes before running it.
- Never share your seed phrase. No developer, support agent or website — including CryptApps — will ever ask for it.
Alternatives
Ethrex sits in a crowded field of Ethereum execution clients. Nethermind is built on .NET and is known for a broad feature set, while Geth is the official Go implementation and the most widely deployed client. Erigon focuses on performance and storage efficiency, and Nimbus is a lightweight consensus client rather than an execution client, so it solves a different problem.
What distinguishes Ethrex is its orientation toward zero-knowledge proving. Its design choices around data structures and multi-prover support target teams building ZK rollups, rather than general node operators. If your goal is a mainstream, battle-tested node for everyday use, the established clients are usually the safer starting point. If you are working on validity proofs, Ethrex is worth a closer look.
Specifications
- Price
- Free
- Type
- Open source
- License
- —
- Latest version
- v30.0.1-rc.3
- Last update
- 30 Oct 2026
- Windows support
- Likely (builds for Windows; check releases)
- Source code
- github.com/lambdaclass/ethrex
Frequently asked questions
Yes. Ethrex is listed as free and open source, and its source code is available on GitHub. You can read the code, build it yourself, or use the released binaries without paying a license fee.
Windows builds are mentioned as likely available, but you should confirm that the release you want includes a Windows artifact. Check the GitHub Releases page, and verify the checksum of anything you download.
Ethrex is used as an Ethereum execution client, particularly by teams building zero-knowledge rollups. It executes blocks, maintains state, and can be paired with zkVMs such as SP1 or RISC Zero to prove that execution was carried out correctly.
It can be, provided you download it from the official repository, verify its checksum or signature, and keep its network interfaces restricted. Never enter seed phrases or private keys into third-party tools, and treat any unofficial copy with suspicion.
Geth is the official Go implementation and is widely deployed for general use. Ethrex is a Rust client with a smaller codebase and a design focus on zero-knowledge proving, which makes it more specialized.
Running an Ethereum execution node requires substantial disk space and reliable bandwidth, and proving blocks with a zkVM is computationally heavy. Plan your hardware around the role you intend the node to play.
Yes. Ethrex uses the same execution client for Layer 1 and Layer 2, and its documentation references rollup environments such as Polygon, Arbitrum and Optimism.
Verdict
Ethrex is a focused, free Ethereum execution client for developers and infrastructure teams who care about zero-knowledge proving. It suits rollup builders, researchers and engineers who want a compact Rust codebase they can read and test. It is not a consumer app, and it is not the right first choice for a general-purpose node operator. Check the latest release and its Windows support on the official GitHub page before you install.