A modular, Ethereum L1 & L2 execution client in Rust. Built by @class_lambda.

Filter
Exclude
Time range
-
Minimum likes
ethrex retweeted
If you want to get a feel for what the future of privacy on Ethereum looks like 👇
EIP-8250 (Keyed Nonces) and EIP-8272 (Recent Roots) are now considered for inclusion in Hegotá. Both run alongside EIP-8141 (Frame Transactions) on our public privacy testnet, where you can already try them. We're excited to keep pushing privacy on Ethereum closer to users. If you haven't tried it yet, find out how here: faucet.privacy.ethrex.xyz/
1
5
28
1,352
The recording from today's Community Call is already available. Catch up on the latest updates and what's coming next, on demand.
3
140
EIP-7906 (Transaction Assertions via State Diff Opcode) was also considered for inclusion in Hegotá. It's live on our Hegotá testnet alongside frame transactions. If you haven't tried it yet, find out how here: faucet.hegota.ethrex.xyz/
EIP-8250 (Keyed Nonces) and EIP-8272 (Recent Roots) are now considered for inclusion in Hegotá. Both run alongside EIP-8141 (Frame Transactions) on our public privacy testnet, where you can already try them. We're excited to keep pushing privacy on Ethereum closer to users. If you haven't tried it yet, find out how here: faucet.privacy.ethrex.xyz/
4
12
566
EIP-8250 (Keyed Nonces) and EIP-8272 (Recent Roots) are now considered for inclusion in Hegotá. Both run alongside EIP-8141 (Frame Transactions) on our public privacy testnet, where you can already try them. We're excited to keep pushing privacy on Ethereum closer to users. If you haven't tried it yet, find out how here: faucet.privacy.ethrex.xyz/
1
8
34
2,813
Our Community Call goes live at 2:30 PM UTC on X. We'll walk through the latest progress and what the team is focused on next.
2
4
303
The recording from today's Community Call is already available. Catch up on the latest updates and what's coming next, on demand.
2
1
6
1,094
Don't forget, our Community Call is tomorrow at 2:30 PM UTC on X. We'll cover what we've been shipping and where we're headed next.
2
2
4
612
ethrex v27.0.0 adds state and block overrides to the RPC simulation methods. It also ships the Ethereum Foundation's new bootnode fleet for mainnet, Sepolia, and Hoodi, and stops transaction-admission rules from rejecting simulated calls. The override sets are the headline. eth_call, eth_estimateGas, eth_createAccessList, and debug_traceCall now accept the State Override Set and Block Override Set that geth defines, on both L1 and L2: per-address balance, nonce, code, state, and stateDiff, plus movePrecompileToAddress. Tooling that assumes those parameters exist, from forge script to Tenderly-style and MEV simulators to wallet balance previews and Multicall3 aggregators, now works against an ethrex RPC. Also in v27.0.0: - Bootnodes: the Ethereum Foundation's Node Infrastructure team is replacing the fleet that ships as the EF entries, and the new records are here. Five nodes per network, each serving mainnet, Sepolia, and Hoodi, geographically distributed, multi-cloud, dual stack, and spread across several discovery implementations, so one implementation bug cannot take the whole set down. It is a replacement rather than an addition, and third-party bootnodes and DNS discovery roots are untouched. Nodes pick the records up on upgrade, with no configuration change. - Simulated calls are no longer refused by transaction-admission rules. A call object carries no signature, so EIP-3607's contract-sender rule has nothing to protect: a smart contract wallet previewing its own transaction now gets a result instead of an error saying the sender should not be a contract. Transaction admission and block execution are unchanged. - A method in a namespace that is not enabled now says so, instead of reporting itself as not implemented. --http.api defaults to eth,net,web3, so debug_* probes against a stock node were reading as missing functionality when the handler was simply never reached. - Stateless-validator guests are on ERE v0.17.0, with the ERE version pinned by tag across the guest manifests and the release workflow. If you run ethrex, upgrade. No resync is needed.
2
3
13
626
Privacy testnet post:
We are running a public testnet for the EIPs behind Ethereum's privacy roadmap, built on top of Glamsterdam. It runs EIP-8141 (Frame Transactions), EIP-8250 (Keyed Nonces), EIP-8272 (Recent Roots), EIP-7805 (FOCIL), and EIP-8369 (VOPS profiles), each implementation up to date with its spec. The frames implementation matches the latest execution spec tests release. Anyone can sync, peer, transact, and use the faucet to fund test accounts. The only permissioned part of the network is validator entry. If your client team is working on any of these EIPs and wants to validate, reach out to us, and we'll get you set up with deposit tokens. RPC, explorer, and tooling notes: faucet.privacy.ethrex.xyz/
2
141
Frame transactions testnet post:
EIP-8141 (Frame Transactions) was SFI'd in the last ACDE. We've been frames-pilled since it was first proposed as a headliner, and we started building a reference implementation on ethrex back then. Adoption grew with time: other clients picked frames up, there are now execution spec tests (our implementation matches the latest release), and an official EthPandaOps-hosted frames devnet is getting close. We didn't want to make anyone wait for it, so we're already hosting a public testnet for frame transactions, built on top of Glamsterdam. Validator entry is permissioned; everything else on the chain is not. Anyone can sync, peer, and transact, and the faucet funds test accounts. If your client team is working on frames and wants to validate, reach out and we'll set you up with deposit tokens. RPC, explorer, and frame tooling, including a CLI that builds and submits frame transactions: faucet.frames.ethrex.xyz/
1
1
4
269
EIP-8141 (Frame Transactions) is now a Hegotá headliner! We backed frames from the moment they were first proposed as one, and we've been building an implementation in ethrex ever since. That implementation now runs two public testnets: one dedicated to frame transactions, and one dedicated to privacy, which adds the companion EIPs also up for Hegotá: EIP-8250 (Keyed Nonces), EIP-8272 (Recent Roots), and EIP-7805 (FOCIL). The future of Ethereum is looking good, and you can already get a taste of it: faucet.privacy.ethrex.xyz faucet.frames.ethrex.xyz
⚡ ACDE #245 - ultra tl;dr: → 8141 (frame tx) confirmed as a Hegota headliner, alongside 7805 (FOCIL) 🏆 → first 14 DFI decisions made: 7819, 7851, 2488, 8219, 8182, 7645, 7923, 8200, 8188, 8358, 8115, 7862, 7807, 8094 🪓 video and summary: forkcast.org/calls/acde/245/
5
6
43
2,068
The recording from today's Community Call is already available. Catch up on the latest updates and what's coming next, on demand.
2
10
542
Tomorrow at 3 PM UTC, we're hosting our Community Call live on X. Latest updates, recent work, and what's ahead. Come hang with us. PS: Note that for this week, we are doing it half an hour later as usual.
3
2
701
Following up on our execution EIP tier list, we wanted to share our combined execution and consensus rankings for Hegota. We've followed the same EF Protocol scoring system and tier definitions for both lists. We'd also like to make a special mention of the post-quantum-ready deposit contract proposal. It didn't make it onto the Hegota EIP selection list, but we think proposals like this one should be included in the fork to prepare validator deposits for future post-quantum credentials. We'll expand on our thoughts about Hegota and the reasoning behind our rankings in the blog post we're preparing.
Over the last few months, we've been working with EF researchers and EIP authors on Hegota proposals, implementing them in ethrex and opening our public testnets to users and other client teams. We wanted to share our execution EIP tier list, which follows the EF Protocol team's scoring system and tier definitions. After spending these months building and testing several of these proposals, we're excited to contribute to the discussion of what should come next for Ethereum. We'll also share our consensus EIP tier list soon, as part of a blog post where we'll expand on our thoughts about Hegota.
4
4
31
3,845
Over the last few months, we've been working with EF researchers and EIP authors on Hegota proposals, implementing them in ethrex and opening our public testnets to users and other client teams. We wanted to share our execution EIP tier list, which follows the EF Protocol team's scoring system and tier definitions. After spending these months building and testing several of these proposals, we're excited to contribute to the discussion of what should come next for Ethereum. We'll also share our consensus EIP tier list soon, as part of a blog post where we'll expand on our thoughts about Hegota.
6
8
42
3,955
ethrex v26.0.0 adds Platåberget, the first public Glamsterdam testnet, as a named network. It also ships the eth/72 sparse blobpool, a batch of sync-robustness fixes, and the eth_ RPC methods other clients serve. ⚠️ This release bumps the database schema from v3 to v4. The migration runs at startup and rewrites nothing, so upgrading is a plain restart, and no resync is needed. It is one way, though: a v26 datadir can no longer be opened by v25, so rolling back after upgrading is not supported. Platåberget launched on 17 August and forked to Glamsterdam three days later. Ethrex already supported the spec, but joining meant hand-feeding a genesis file and bootnodes. Now --network plataberget works like hoodi or sepolia, with the genesis hash pinned in a test against the published EL genesis. Also in v26.0.0: - eth/72 sparse blobpool (EIP-8070): per-transaction custody columns, cell verification against EIP-7594 proofs, GetCells and Cells messages, and optional custodyColumns on forkchoiceUpdatedV4. The EIP is a draft Glamsterdam candidate rather than scheduled for inclusion, and capability negotiation leaves eth/71 peers untouched. - Sync robustness: the syncer no longer wedges while waiting for a forkchoice head, recovers instead of stalling when the head's post-state is unreachable, stops burning full-sync cycles on the ePBS FCU and newPayload ordering race, and no longer fails a deep reorg on a missing pre-state at the pivot. Peers syncing from us can fetch their head by non-canonical hash, and are told the earliest block we can actually serve instead of block 0. - RPC: net_listening, debug_getRawBlockAccessList, the remaining eth_ namespace methods other clients serve, and EIP-8037 two-dimensional gas in callTracer output. - Memory: the RocksDB block cache is sized from available memory instead of a flat 12 GiB, which on a 16 GB host meant handing RocksDB 71 percent of the machine. Containers were worse, since /proc/meminfo reports the host's memory and not the container's limit. Surfaced on ethpandaops' syncoor runners. - Database safety: a node restarted partway through a full-sync batch recovers its state instead of reporting an unrecoverable database, and a datadir last written by a newer ethrex is refused with a clear version error rather than a misleading migration failure. - Discovery: external IP learned from discv4 PONGs, unsolicited discv5 NODES responses rejected, and the ENR fork id refreshed when the chain crosses a fork. - Performance: cheaper cold contract-code access, which is what the schema bump is for, plus breadth-first trie-node prefetch in the storage-root path and a faster LEVM memory hot path. On the Glamsterdam BAL path, O(1) recorder checkpoints and batched code prefetch. - Correctness fixes in eth_estimateGas, eth_getLogs, eth_getBlockByHash and receipt lookups, stateless-validator guests on ERE v0.16.2, L2 build and sequencer fixes, and EIP-8037 state-gas accounting plus undecodable block-access-list handling aligned with the devnet-8 suite (devnets only). If you run ethrex, upgrade. No resync is needed. Check the rollback caveat above first.
3
3
14
669
Our testnet continues to be a public testing ground for frame transactions, not only for users who want to build on top of this feature, but also for execution clients who want to test their implementations. A week after the launch, @Nethermind has been able to onboard some validators on it. @go_ethereum now has a full frame transactions implementation passing all the spec tests suite and will be validating in the testnet soon. At today's frame transactions breakout, @Besu_eth expressed that they will attempt to explore the testnet as well. We're excited to continue pushing frame transactions closer to users. If you haven't tried it yet, find out how to do so here: faucet.frames.ethrex.xyz
EIP-8141 (Frame Transactions) was SFI'd in the last ACDE. We've been frames-pilled since it was first proposed as a headliner, and we started building a reference implementation on ethrex back then. Adoption grew with time: other clients picked frames up, there are now execution spec tests (our implementation matches the latest release), and an official EthPandaOps-hosted frames devnet is getting close. We didn't want to make anyone wait for it, so we're already hosting a public testnet for frame transactions, built on top of Glamsterdam. Validator entry is permissioned; everything else on the chain is not. Anyone can sync, peer, and transact, and the faucet funds test accounts. If your client team is working on frames and wants to validate, reach out and we'll set you up with deposit tokens. RPC, explorer, and frame tooling, including a CLI that builds and submits frame transactions: faucet.frames.ethrex.xyz/
7
38
2,288
Frames are all you need, and all you need to try frames is our public frames testnet, freshly upgraded to the current spec! faucet.frames.ethrex.xyz/
3
4
28
2,069