Shura

@FlowSubHQ @Nethermind I would say - it's both for different purpose

This week the Ethereum Foundation called for synchronous composability and native rollup status for L2s. We agree. So we built it. Surge merges sequencing and proving into a single L1 transaction. The L2 block and its ZK proof land on L1 together. L1 verifies L2 state immediately. No bridges. No optimistic windows. Atomic L1↔L2 execution in seconds. @DuckDegen has the full architecture breakdown and a demo at EthCC, March 31.

@FlowSubHQ @Nethermind We are using Zisk for proofs. It executes the program producing a single trace, which is witnessed in parallel by specialized state machines (ROM, memory, arithmetic, hashes, etc.) Those proofs are then recursively aggregated into one final STARK, which is wrapped into a SNARK.

@MarcinM02 @Nethermind The final snark proof is Plonk. Stark proof is wrapped into Snark's Plonk

@Nethermind what's the final zk that you used? plonk ? groth16? i wish that Ethereum had some cheap FRI verification precompile..