What if @ethereum could verify ZK proofs itself, so rollups and apps wouldn't need to run their own verifiers?
This could be achieved through native proof verification.
And we've made some progress there over the past month: the draft for EIP-8357 was merged, and a native rollup is now running on a devnet 👇
Want to dig deeper? We've put everything in one place: l2beat.com/native-rollups/
Replying to @SuccinctLabs
@SuccinctLabs disclosed an SP1 bug, but onchain Groth16 and Plonk verification through Solidity verifiers was unaffected by this issue.
The bug affected native Rust verification. Here’s how our ZK Catalog helps you tell the paths apart 👇
When checking a vulnerability, follow the application’s verification setup and compare it with the disclosure’s scope.
Our ZK Catalog gives you places to start:
l2beat.com/zk-catalog
Most DAO voting happens in public - you can look up a wallet and see exactly how it voted, which allows for bribery and voter pressure. In real-world elections, the secret ballot is an internationally recognised standard that exists to prevent exactly that.
@theInterfold CRISP tries to solve this for onchain voting by keeping individual votes private while making the final results public.
We've added it to the L2BEAT Privacy dashboard. Here's how it works and who you need to trust 👇
@theInterfold CRISP is live on mainnet, although it's still early. The operator set is in its initial stage, and there have only been a handful of votes so far.
Full breakdown: l2beat.com/privacy/projects/…




