RT @MatteoFrig60839: @zeroknowledgefm @AnnaRRose @nico_mnbl @Google The source code is now open to all .

RT @HouseofZK: @jbaylina @0xPolygon @BruestleJeremy @RiscZero @NorbertVadas @thezkcloud @drakefjustin @ethereumfndn @eth_proofs @sd_eigen @….

RT @LineaBuild: While zkVMs (especially RISC-V) have recently dominated the zk-EVM landscape, Linea's direct arithmetization approach offer….

RT @DeclanFox14: @LineaBuild just dropped a huge UX unlock by adding eth_sendBundle:. - Bundled transactions (eg. approve-and-swap in 1 cli….

RT @DeclanFox14: EOF needs more product discovery. Before committing to the roadmap, I always ask PMs to ensure a feature is:. - feasible.-….

RT @YaoGalteland: We benchmarked Plonky3’s FRI PCS vs Vortex (@LineaBuild’s polynomial commitment scheme). 🚀 Vortex commitment is 3.7× fas….

RT @DeclanFox14: Prover completeness has been achieved internally!. Work on the zkEVM started in July 2021, with the first publication shar….

The amazing gnark team optimized the SIS hash function that we are using in Vortex for Linea's prover. This an important step for the migration toward using small fields. Can't wait for it to be integrated in the prover.

9/9 More details here: End of the thread!.------------------------------.

8/9 Technical benefits:.* Asynchronous operation: No inter-job synchronization required.* Dynamic subproof generation: "Pay-for-what-you-use" model.* Improved resource allocation: Mitigates current inefficiencies from disparate limit utilization.

7/9 Anticipated improvements:.* Reduced memory footprint: From 700GiB to significantly lower requirements.* Enhanced cost-efficiency: Enables deployment on more economical hardware.* Increased TPS: Removal of limit-counting logic in sequencer (currently 90% of CPU utilization).

6/9 Proof aggregation leverages existing Vortex recursion techniques. This process verifies inter-segment consistency, ensuring holistic correctness of the EVM execution.

5/9 Challenge: Managing cross-segment constraints (lookups, permutations, projections). Solution: a novel shared-randomness protocol, ensuring the whole system is fully asynchronous with close to no overheads compared to synchronous alternatives.

4/9 Horizontal split: different areas of the EVM are processed by different proofs (we call them modules). Vertical split: each module .is processed by several proofs depending on its usage.

3/9 The solution? Implementing a distributed proof system: the prover splits the task of generating a proof into small "segment proofs". The splitting is done both horizontally and vertically.

2/9 Currently, Linea imposes execution limits on transactions going through the network. For instance, a transaction may not call the Keccakf sponge function more than 8192 times on Linea. This is a problem as it completely blocks transactions attempting to do.a lot of hashing.

1/9 Breaking news from Linea core team. We are working on a major upgrade of our proof system architecture: .eliminating the execution bounds on Linea! This update will drastically improve the UX and the overall system throughput.

RT @bigironchris: Introducing the Limitless Prover . Linea plans to eliminate execution limits, enhancing user experience, increasing TPS r….

RT @francescoswiss: Excited to learn from @alexand_belling from @LineaBuild about Wizard, a new open-source framework that lets you create….

RT @DeclanFox14: One week ago we open sourced Vortex, the prover system that powers Linea. Vortex is the best zkEVM tech available: speed,….