←
ethrex618 posts
ethrex avatar

ethrex

@ethrex_client

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

◷ Joined July 2025▧ 157 Photos and videos
ethrex avatar
ethrex@ethrex_client·20h

Ethereum users need quantum-resistant signatures they can afford to use. Hash-based signatures are much larger than today’s signatures. EIP-8288 proposes using STARKs to prove many signatures valid together, reducing their data and verification costs. With ethrex, we’ll help implement and test the execution-layer changes needed for new user signatures, and publish benchmarks so wallet builders and client teams can evaluate the tradeoffs. We support the goal of post-quantum readiness by the end of 2028. Getting there requires testing these designs in real clients now.

Post attachment

Mission 2028: Ethereum's cryptography can't wait for Q-Day. Our takeaways from Devcon 8 and the L1 R&D workshop, and how @ethrex_client and @ethlambda_lean should help @ethereum reach post-quantum readiness by 2028. First in our post-quantum Ethereum series. blog.lambdaclass.com/mission…

Fede’s intern avatar
⟳ ethrex retweeted
Fede’s intern@fede_intern·Nov 10

Great to see people using @ethrex_client at @ETHGlobal hackathons! The team using it won second prize. We run an ethrex devnet (chain 1337) with the EIP-8141 tracer profile, behind a Skandha sidecar that implements the ERC-8421 alternative mempool, plus the public alt-mempool devnet. Transactions are encoded either with @forshtat/hegota-support, a codec for frame transactions that is driven by a per-network profile, or an extension we wrote for viem, using forshatat library as a dependency. ethglobal.com/showcase/frame…

Fede’s intern avatar
⟳ ethrex retweeted
Fede’s intern@fede_intern·Nov 6

Nice to see Ivan, our @ethrex_client lead, talking at @EFDevcon. Let's go @ethereum!

The strawmap set a goal of Lean Ethereum by 2029—we now have a fork-by-fork plan to get there. H* will be the last fork without lean features. I* will ship the leanVM and lean transactions. J* will add lean attestations, DA sampling and PCS. By L*, Lean Ethereum will be complete

0:45
Fede’s intern avatar
⟳ ethrex retweeted
Fede’s intern@fede_intern·Nov 6

ethlambda @ethlambda_lean, our consensus client for @ethereum, is with silver from @gattacahq the fastest consensus client. we're very proud of the work we're doing in @ethrex_client and @ethlambda_lean. in the upcoming months we're gonna focus more and more in performance. most of the work we have been doing was around testing new EIPs, implementing new features and making everything stable. we're in talks with multiple big validators that want to adopt ethrex and ethlambda.

Post attachment
ethrex avatar
ethrex@ethrex_client·Nov 3

We are at @EFDevcon! We’d love to meet stakers looking to diversify their stack with ethrex, one of Ethereum’s fastest execution clients, built in Rust. Come chat about running ethrex in your setup. DM us to meet up!

ethlambda avatar
⟳ ethrex retweeted
ethlambda@ethlambda_lean·Oct 30

ethlambda v1.0.0 is here! We now support the beacon chain through Gloas and run on mainnet and testnets, with a smooth Glamsterdam transition on Sepolia behind us. Proud to bring more client diversity to Ethereum as we keep building toward its post-quantum future.

ethlambda v1.0.0 is here! Our Lean Ethereum consensus client now has full beacon chain support, including Gloas. We're running it on mainnet, Sepolia, Hoodi, and Platåberget. Our Sepolia validators successfully transitioned to Glamsterdam without a single issue. Built in Rust, ethlambda brings together what we've learned from Lean Ethereum devnets and years of developing ethrex. With @ethrex_client on execution and @ethlambda_lean on consensus, we're contributing to client diversity across both layers of Ethereum. Next, we're pushing performance further, participating in Hegotá interoperability devnets, and working to bring post-quantum cryptography to the beacon chain. Explore ethlambda and what we're building next in the full announcement: blog.lambdaclass.com/ethlamb…

ethrex avatar
ethrex@ethrex_client·Oct 30

Congratulations to @ethlambda_lean on v1.0.0! We're proud to see lessons from building ethrex help shape another Ethereum client. With ethlambda supporting the beacon chain, we can work together on improvements across Ethereum's execution and consensus layers.

ethlambda v1.0.0 is here! Our Lean Ethereum consensus client now has full beacon chain support, including Gloas. We're running it on mainnet, Sepolia, Hoodi, and Platåberget. Our Sepolia validators successfully transitioned to Glamsterdam without a single issue. Built in Rust, ethlambda brings together what we've learned from Lean Ethereum devnets and years of developing ethrex. With @ethrex_client on execution and @ethlambda_lean on consensus, we're contributing to client diversity across both layers of Ethereum. Next, we're pushing performance further, participating in Hegotá interoperability devnets, and working to bring post-quantum cryptography to the beacon chain. Explore ethlambda and what we're building next in the full announcement: blog.lambdaclass.com/ethlamb…

ethrex avatar
ethrex@ethrex_client·Oct 29

We’re bringing ethrex to @EFDevcon. We’d like to exchange ideas with other teams, hear what you’re working on, and connect with people using ethrex or interested in trying it. DM us to coordinate a meetup.

We’re heading to @EFDevcon. @lean_knack and @ivanlitteri will be speaking about Lean Ethereum: cfp.devcon.org/devcon8/talk/… We’re working across Ethereum execution, consensus, and proving, and want to hear what other teams are building in these areas. If you’re attending and want to meet, DM us to coordinate.

Post attachment
ethrex avatar
ethrex@ethrex_client·Oct 29

No ethrex Community Call tomorrow. We’ll share the date for our next call soon. In the meantime, we have some updates coming your way.

ethrex avatar
ethrex@ethrex_client·Oct 26

Great to see ethrex proving Sepolia blocks side by side with @openvm_org. Ethereum’s move toward execution proofs should preserve client diversity from day one. Thanks @ignaciohagopia, @TauLepton_, and everyone bringing EIP-8025 to life!

Let there be proofs! 🎉 Running an EIP-8025 execution-proof prover on Sepolia: blocks proven in ~6–7s on 16× RTX 5090 with OpenVM, for two guests, ethrex + reth (8 GPUs each). 36k+ proofs and counting. Big shoutout to the prover teams, guest program teams and everyone who contributed to making this a reality! We'll be rotating provers and guests over the coming days and weeks. Which prover + guest should we spin up next? ⚠️ Experimental: validators MUST NOT rely on execution proofs for fork choice or attestations. Keep running an execution client. (Yes, Sepolia validators are permissioned, but still 🙂)

Post attachment
ethrex avatar
ethrex@ethrex_client·Oct 23

ethrex v30.0.1 unschedules Glamsterdam on Hoodi, after the ACDE call unscheduled it yesterday. If you run a Hoodi node on v30.0.0, or on one of its release candidates, you need this release before 26 October at 17:42:48 UTC. That is the time v30.0.0 still has the fork set for, and a node that activates it alone splits off from the rest of Hoodi. L2 operators running a sequencer or a follower should upgrade too. Mainnet and Sepolia are unchanged, so operators there who do not run an L2 or the stateless validator can stay on v30.0.0. ⚠️ The stateless-validator guests move to ERE v0.19.5 (SP1 v6.9.0, ZisK v1.3.2-alpha), and the ZisK guest's verification key changes. Anyone who verifies ethrex's stateless-validator proofs, such as zkEVM integrations, has to move to this release's keys together. Node operators who do not use the stateless validator are unaffected. The rest of the release is mostly L2 reliability. A follower whose head was past the last sealed batch used to stop importing blocks when the sequencer or the follower restarted, and only wiping its data brought it back; it now resumes from its own head. A node holding more than one connection to the sequencer could stall mid-sync with RPC and logging frozen, so blocks are now imported in order by a single importer per node. Catch-up is faster as well: the sequencer sends a reconnecting peer only the blocks it is missing and up to 16 batches at a time, and followers no longer commit trie layers to disk after every imported block. Also in v30.0.1: - Stateless validation: witnesses with trie paths that do not end at the hashed key length are rejected, and zero-amount withdrawals read their recipient, as the specification requires. The check runs while the witness tries are rebuilt, so it adds little proving cost. - Block building: withdrawals are applied before the request system calls, the order the specification and block import already use. Only chains with custom request predeploy code were affected, not mainnet or the public testnets. - Networking: node records are encoded without base64 padding, so clients with strict parsers can bootstrap from an ethrex node. If you run ethrex on Hoodi, upgrade before 26 October. No resync is needed.

Post attachment

Core developers decided to delay the upcoming Hoodi hard fork on today's ACDE call. Refer to this blog post for further details and be sure to watch for any client releases pertaining to your infrastructure on Hoodi. blog.ethereum.org/2026/10/22…