Ivan (@ivanlitteri) header
Ivan (@ivanlitteri) profile picture

@ethrex_client tech lead at @class_lambda. Interested in number theory, cryptography and distributed systems. I just press keys and things kinda work

Buenos Aires, Argentina
Joined December 2017
Ivan retweeted
ZisK v1.4.0-alpha release Delivering real-time proving on just 2×5090, with no compromise on security: > 2×5090: 4.84s median, 7.92s p999, max 9.10s > 4×5090: 3.16s median, 4.89s p999, max 5.50s - 128-bit provable security - Post-quantum secure - Proofs under 256 kB - No arithmetic hashes
3
11
7
54
5,386
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.
1
2
2
15
1,132
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.
3
7
343
Don't forget, our Community Call is tomorrow at 3:30 PM UTC on X. We'll cover what we've been shipping and where we're headed next.
1
3
156
For the 'multi-node' enjoyooors out there, this one's for you! Beyond the performance gains, I'm particularly excited about the reusable components (p2p-networking, state hashing, BLS/KZG libraries) and the application of formal verification to performance-critical cryptography. Will be interesting to see how other client teams can benefit from this work. Also a great reminder that Ethereum client development is permissionless. At a time when people are discussing sustainable client funding and reliance on the EF, seeing independent teams invest in new implementations is encouraging. Pretty remarkable engineering work!
5
29
689
My first speaking appearance on Ethereum ACD, December the 15th, 2017. I was quite terrified, but @hudsonjameson was kind and all was well. Nice to see a few friends still around at ACD - particular s/o to @mkalinin2 and Anton! And now...
5
7
96
2,798
We want Ethereum to also win on UX, while getting even harder to censor, more private and more secure. Silver is our effort to contribute to that, with a focus on performance. We’re standing on the shoulders of all the client teams who’ve brought Ethereum this far, and are keen to work with the community and bring our experience in high-performance engineering. $ETH
6
14
195
5,131
Ivan retweeted
We want to see a lot more activity on Ethereum. I think we can make it much faster and easier to use while strengthening its decentralisation and security. Excited to share Silver, our new consensus client. It’s in its first alpha, and we’ve pushed hard on performance to make as much room as possible for changes like shorter slots and PQ. We want to use Silver to contribute much more directly to Ethereum’s development and help get more of its roadmap shipped.
4
7
76
1,637
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.
1
3
239
Taking this opportunity to plug all the tooling built by the EF zkEVM team @ignaciohagopian @codytouchgrass @han__0110 @kevaundray @ladislaus0x and friends 🙏 📊 Hive dashboards: execution-spec tests run against every EL's execution witness and every guest × zkVM eth-act.github.io/eest-execu… ✅ zkevm-test-monitor: tracks zkVM compliance with the zkEVM standards eth-act.github.io/zkevm-test… 🔧 ere: one interface to compile, prove and verify across zkVMs github.com/eth-act/ere 📦 ere-guests: the stateless EVM validator guests we're proving github.com/eth-act/ere-guest… 🚀 zkboost: proves every block and feeds proofs to the beacon node github.com/eth-act/zkboost 🧪 ethereum-package: spin up a local EIP-8025 devnet with provers in one command github.com/ethpandaops/ether… ⚙️ provoor: runs the GPU proving clusters github.com/han0110/provoor 📈 provoor runs: proving benchmarks han0110.github.io/provoor-ru…
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 🙂)
1
8
1
28
1,937
Vero enabled us to introduce @ethrex_client into our multi-node setup early on, without having to fully rely on it. It's been performing really well for us over the past year! We're looking forward to trying out @ethlambda_lean on the consensus layer soon. Client diversity! 🚀
Replying to @SerenitaIO
@SerenitaIO was one of our early adopters, and we're grateful for that support. Great to connect with @serenita_luca and hear more about Vero. Looking forward to continuing our work together!
2
3
86
Security fix disclosure: PropAMM contract We fixed a critical bug in the PropAMM contract in github.com/lambdaclass/propa… main branch; our factories on Ethereum mainnet are not affected by this vulnerability. The vulnerability found was due to the PropAMM contract that had a leftover setup function, reinitializeV2, which anyone could call once on a newly created PropAMM. Calling it could let an exploiter point the PropAMM at a price feed they control and then trade against its vaults at any price they chose, emptying them. More information here: github.com/lambdaclass/propa… From our conversations with third parties interested in it and from the information we have seen on-chain, there should not be anyone affected. But if anyone has deployed their own factory, or their own PropAMM forking our code, from this repo's code before October 27, 2026, please follow the instructions below: revoke your vaults' approvals to the PropAMM or move the funds out of the vaults create a new PropAMM through our mainnet factory (address in docs/production.md) or from the latest main. Contact us at [email protected] if you need help.
4
1
45
6,214
Replying to @SerenitaIO
@SerenitaIO was one of our early adopters, and we're grateful for that support. Great to connect with @serenita_luca and hear more about Vero. Looking forward to continuing our work together!
Great meeting with @serenita_luca! @SerenitaIO was one of ethrex's early adopters, and we enjoyed hearing more about the team's work on Vero. Excited to keep working together to bring more client diversity to Ethereum with @ethrex_client and @ethlambda_lean.
1
1
7
309
We enjoyed exchanging ideas with @serenita_luca and learning more about Vero. Excited to keep working with @SerenitaIO as we build ethlambda and contribute to Ethereum's client diversity!
Great meeting with @serenita_luca! @SerenitaIO was one of ethrex's early adopters, and we enjoyed hearing more about the team's work on Vero. Excited to keep working together to bring more client diversity to Ethereum with @ethrex_client and @ethlambda_lean.
2
5
453
Great meeting with @serenita_luca! @SerenitaIO was one of ethrex's early adopters, and we enjoyed hearing more about the team's work on Vero. Excited to keep working together to bring more client diversity to Ethereum with @ethrex_client and @ethlambda_lean.
1
5
2
14
1,789
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 🙂)
2
6
25
965
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 🙂)
5
12
3
47
3,985
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.
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…
1
2
6
276
Mumbai is getting closer and we are wrapping up our @EFDevcon talk. See you there friends! cc: @ivanlitteri Ps: Sorry about the mess but Boca and hungry Luffy drive me – at Buenos Aires City Region, Argentina
1
4
131