Ivan (@ivanlitteri) - Twitter Profili | Zamantika Mersobahis Locabet

Ivan retweetledi

ethrex@ethrex_client·13h

During @eth_proofs BEAST MODE day, we upgraded our @ziskvm single-GPU prover from ZisK 0.14.0 to 0.16.0. The proving time went down from ~2m to 1m 17s average with a single 5090. Also, the failure rate looks very good, from 30%-40% missing proofs a day to 0% so far! This is thanks to all the hard work of the @ziskvm team has been doing and some optimizations we've been doing on @ethrex_client. Our mainnet proving times went down from ~6m to ~1m since we first integrated with them. There's still much more room for improvement.

English

3

8

57

3.8K

Ivan retweetledi

ladislaus.eth@ladislaus0x·23h

Optional zkEVM proofs (EIP-8025) don't just affect the CL for zkAttesting — they require adaptation on the EL side as well. In particular, a stateless program that gets proven ("guest program") and a standardised data package that enables stateless validation: the ExecutionWitness Here's a demo of an initial implementation of EIP-8025 by an EL client

ethrex@ethrex_client

We've implemented EIP-8025 (Optional Execution Proofs) in @ethrex_client. EIP-8025 lets consensus clients request and verify zkEVM proofs of block execution. Validators check a proof instead of re-executing the block, a step toward proof-of-proof-of-stake. @ethrex_client already had witness generation and zkVM guest programs for L2, plus distributed proving. We brought all of it to L1. We're passing the new zkEVM execution spec tests from ethereum/execution-spec-tests. Each fixture ships a pre-built witness with the block, the same setup that a beacon node sends under EIP-8025. The demo shows the proof lifecycle: - Block produced and submitted through the standard Engine API - Proof requested, coordinator dispatches to prover via TCP - Prover executes the block statelessly, submits the proof - Proof delivered via HTTP callback - Verification: SYNCING (no proof yet) → VALID (proof verified) Three terminals running locally: ethrex node with proof engine, L1 prover worker, and our REPL acting as a mock beacon node. The demo uses no-op proofs (re-execution only). ZK proof integration is next. Try it yourself. Instructions in the PR below.

English

3

6

35

2.6K

Ivan retweetledi

ethrex@ethrex_client·1d

We've implemented EIP-8025 (Optional Execution Proofs) in @ethrex_client. EIP-8025 lets consensus clients request and verify zkEVM proofs of block execution. Validators check a proof instead of re-executing the block, a step toward proof-of-proof-of-stake. @ethrex_client already had witness generation and zkVM guest programs for L2, plus distributed proving. We brought all of it to L1. We're passing the new zkEVM execution spec tests from ethereum/execution-spec-tests. Each fixture ships a pre-built witness with the block, the same setup that a beacon node sends under EIP-8025. The demo shows the proof lifecycle: - Block produced and submitted through the standard Engine API - Proof requested, coordinator dispatches to prover via TCP - Prover executes the block statelessly, submits the proof - Proof delivered via HTTP callback - Verification: SYNCING (no proof yet) → VALID (proof verified) Three terminals running locally: ethrex node with proof engine, L1 prover worker, and our REPL acting as a mock beacon node. The demo uses no-op proofs (re-execution only). ZK proof integration is next. Try it yourself. Instructions in the PR below.

English

1

11

52

6.8K

Ivan retweetledi

Diego Kingston🟩@diego_aligned·1d

Updates from @ziskvm at @leanEthereum Beast Mode. Paired with @ethrex_client proving time went significantly down! Amazing work by the Zisk team

English

1

5

34

1.3K

Ivan retweetledi

Diego Kingston🟩@diego_aligned·1d

Time for BEAST mode: the future of @leanEthereum execution. Look for the @class_lambda and @alignedlayer teams

English

0

4

26

2.6K

Ivan retweetledi

Diego Kingston🟩@diego_aligned·1d

Time for @class_lambda at @leanEthereum Beast mode

English

2

6

21

1.4K

Ivan retweetledi

RJ 🟩@rj_aligned·1d

the future of @ethereum is here. check out the amazing work @ethrex_client is doing. i’m incredibly proud of working with them and seeing in real time all the hard work they put. never underestimate @class_lambda. with @alignedlayer + @ethrex_client we will build incredible products to upgrade the world to @ethereum.

ethrex@ethrex_client

We've implemented EIP-8025 (Optional Execution Proofs) in @ethrex_client. EIP-8025 lets consensus clients request and verify zkEVM proofs of block execution. Validators check a proof instead of re-executing the block, a step toward proof-of-proof-of-stake. @ethrex_client already had witness generation and zkVM guest programs for L2, plus distributed proving. We brought all of it to L1. We're passing the new zkEVM execution spec tests from ethereum/execution-spec-tests. Each fixture ships a pre-built witness with the block, the same setup that a beacon node sends under EIP-8025. The demo shows the proof lifecycle: - Block produced and submitted through the standard Engine API - Proof requested, coordinator dispatches to prover via TCP - Prover executes the block statelessly, submits the proof - Proof delivered via HTTP callback - Verification: SYNCING (no proof yet) → VALID (proof verified) Three terminals running locally: ethrex node with proof engine, L1 prover worker, and our REPL acting as a mock beacon node. The demo uses no-op proofs (re-execution only). ZK proof integration is next. Try it yourself. Instructions in the PR below.

English

2

7

18

1.4K

Ivan retweetledi

ethrex@ethrex_client·1d

We open-sourced libssz, a fast, no_std SSZ library in Rust. It's available on crates.io. EL clients are picking up SSZ. In ethrex we keep dependencies minimal and care a lot about performance, so we built our own: fast for binary SSZ transport, fast and zkVM-friendly for EIP-8025 proving. Faster than Lighthouse on encode and decode. Passes 62,489 consensus spec tests across all forks. Multiple differential fuzz targets against Lighthouse and ssz_rs are running nightly. Pluggable SHA-256 backend so zkVM vendors can use their own accelerators. We're already using it in @ethrex_client and @ethlambda_lean. ere-guests switched and measured a 2x hash_tree_root speedup inside ziskemu. Compiles on RISC-V and thumbv7m out of the box.

English

1

8

37

1.6K

Ivan retweetledi

ladislaus.eth@ladislaus0x·6d

AllCoreDevs plans to make a decision on EIP-8141 (frame transactions) inclusion in Hegota this Thursday. If you care about post-quantum security on the consensus layer (leanCL), you should equally care about it on the execution layer. A PQ-secure CL with quantum-vulnerable (i.e. ECDSA-locked) user transactions is an incomplete migration. EIP-8141 decouples accounts from a fixed signature scheme, providing a native migration path to PQ-secure signature schemes. But it goes beyond PQ. Frame transactions also make account abstraction a first-class protocol feature rather than something bolted on via entry-point contracts, and enable programmable gas payment (in ERC-20s + sponsoring). Ultimately, both layers need to be PQ-ready.

English

40

52

314

75.6K

Ivan retweetledi

ethlambda@ethlambda_lean·19 Mar

We are hosting the #10 Ethlambda Community Call tomorrow and will walk through recent progress, key insights, and upcoming work. The call will be streamed live on X at 3:30 PM UTC. Join us to be part of the conversation.

English

0

1

50

Ivan retweetledi

ethrex@ethrex_client·19 Mar

Join us tomorrow for the #10 Ethrex Community Call, where we will share the latest updates, ongoing work, and what is coming next for the project. The session will be streamed live on X at 2:30 PM UTC.

English

2

4

8

467

Ivan retweetledi

Ethproofs@eth_proofs·18 Mar

If proving becomes part of Ethereum’s core infrastructure, it cannot live only in the cloud. It has to work on machines people actually own, under real-world constraints. Today, Ethproofs is launching a pilot to test exactly that. We’re funding 4 prover teams to run on-prem multi-GPU rigs and prove 1-in-10 Ethereum L1 blocks on Ethproofs. The goal is simple: encourage more production-grade proving in the wild. This first cohort is a pilot, not a closed club. We are ready to scale. We’re also updating the $300K RTP grants. They are separate from this pilot and open to any team that meets the criteria. Read about all the details here 👇

Ethproofs@eth_proofs

x.com/i/article/2033…

English

0

7

34

5.8K

Ivan retweetledi

Ethproofs@eth_proofs·18 Mar

Ethproofs v3.2 is live 🚀 If proving is part of Ethereum’s future, the ecosystem needs a public way to see what is real: - not just speed, - but security, - reliability, - cost, - hard blocks, - and who is actually making progress. That’s what this upgrade is about.

Ethproofs@eth_proofs

x.com/i/article/2034…

English

0

12

41

5.4K

Ivan retweetledi

ethrex@ethrex_client·18 Mar

When we announced BAL Devnet 3 support, the tests were just starting. Today, ethrex is at 1040/1040 tests passing for 6 consecutive days. Only two EL clients at 100% right now.

ethrex@ethrex_client

Last week, ethrex joined its first Ethereum devnet ever: devnet-bal-2. A few days later, Hive tests for devnet-bal-3 went live, and ethrex is already the most compliant execution client: ethrex: 900/1028 (87.5%) nimbus: 630 (61.3%) erigon: 626 (60.9%) nethermind: 585 (56.9%)

English

2

8

12

1.6K

Ivan retweetledi

LambdaClass@class_lambda·17 Mar

Software development is changing fast. The iteration loop for product development just got 10x faster. At LambdaClass, anyone can type a prompt, get an AI agent working on it in an isolated environment, and share a live preview with the team in minutes. No setup, no waiting for dev cycles. We built the infra to make it work safely at scale.

English

2

9

1.6K

Ivan retweetledi

ziskvm@ziskvm·13 Mar

🚀 ZisK v0.16 is live! This release brings major performance improvements and new architectural capabilities as we move closer to ZisK v1.0. 🔗 Release notes: github.com/0xPolygonHerme… Highlights 👇

English

2

10

41

1.9K

Ivan retweetledi

Clave@getclave·11 Mar

1/ Clave is joining @ParibuCom, leading crypto exchange and and a pioneer in institutional-grade custody solutions in Türkiye. Three years ago we set out to prove that self-custody doesn't have to be hard. Today we're taking that mission to an entirely new scale. Here's what's happening and what it means 🧵

English

20

15

116

26K

Ivan retweetledi

Fede’s intern 🥊@fede_intern·11 Mar

We just came back from an offsite and we started delivering again with @class_lambda in @ethereum. We were out and resting. It’s summer in the south so this is like july and august for europe or the US. Ethrex is now the second execution client only by a little bit. We just pushed some new code. We got many more ideas coming. We are integrating as always all this with the provers of @alignedlayer. We got many great news there with @rj_aligned about distribution and work around our zkVM! Mainnet performance: reth 33ms @ethrex_client 35 ms nethermind 57ms geth 76ms besu 118ms erigom 579ms

English

4

6

35

3.5K

Ivan retweetledi

ladislaus.eth@ladislaus0x·10 Mar

Native rollups and L1-zkEVM proofs are perfectly complementary efforts. Once all validators verify execution proofs, the same proofs can also be used by an EXECUTE precompile for native rollups. L2s and rollup teams benefit from this infrastructure convergence: L1 proving infrastructure becomes shared infrastructure.

ethrex@ethrex_client

We've been working with @kevaundray and @ladislaus0x from @ethereumfndn and @donnoh_eth from @l2beat on a proof of concept of EIP-8079 (native rollups) using @ethrex_client. Native rollups reuse Ethereum's own execution to verify L2 state transitions. No ZK circuits, no fraud proofs, no complex proof systems to maintain. Every L1 upgrade is automatically inherited. Any bug in the verification is also a bug in Ethereum itself. The demo shows a full end-to-end native rollup: - L2 blocks settled to L1 via the EXECUTE precompile - L1→L2 deposit - Contract deployment and cross-layer calls - L2→L1 withdrawal with MPT proof claim - Blockscout verifying EXECUTE precompile calls on L1 Try it yourself. Instructions in the PR below.

English

3

5

31

3.9K

Ivan retweetledi

leandro.ferrigno@lean_knack·10 Mar

Native rollups are becoming a reality. It’s great to see these initiatives moving forward, and we couldn’t have done it alone. Kudos to the team driving this forward and to everyone who has supported it along the way. There’s still more work ahead 💪

ethrex@ethrex_client

We've been working with @kevaundray and @ladislaus0x from @ethereumfndn and @donnoh_eth from @l2beat on a proof of concept of EIP-8079 (native rollups) using @ethrex_client. Native rollups reuse Ethereum's own execution to verify L2 state transitions. No ZK circuits, no fraud proofs, no complex proof systems to maintain. Every L1 upgrade is automatically inherited. Any bug in the verification is also a bug in Ethereum itself. The demo shows a full end-to-end native rollup: - L2 blocks settled to L1 via the EXECUTE precompile - L1→L2 deposit - Contract deployment and cross-layer calls - L2→L1 withdrawal with MPT proof claim - Blockscout verifying EXECUTE precompile calls on L1 Try it yourself. Instructions in the PR below.

English

2

5

416

Ivan

Keşfet