YQ 🦦🦇🔊 Profile picture
restaking/acc https://t.co/d8fCmiYo4N, shared security with restaked rollups. https://t.co/pj3bo75iij, https://t.co/0vVOb8y8a9, https://t.co/zrs6AVQBJb.

Oct 10, 2022, 18 tweets

1/x Prior to #DevconVI, at #RollupDay, @VitalikButerin talked about “Hardening rollups with multi-proofs”. Here is a thread of brief summary.

2/x Nowadays, almost all #rollup protocols are still on “training wheels”, as proofs are either in development or can be easily overridden by simple governance.

3/x Even if we have proof systems ready say validity proof for zk-rollups, due to the complexity of the generated proofs, it’s quite tough to ensure there’s no bug in the proof. One example below, for a simple code snippet in #PSE zk-EVM impl, it has 34,469 lines of circuit code.

4/x It’s almost impossible to ensure so many lines of code are bug-free for a long long time.

5/x Option 1: to run high-threshold(the super majority of guardians or token holders) governance to override the buggy states from the single proof system.

6/x Option 2: multi provers say fraud proof from optimistic rollup and validity proof from zk rollup. Or different implements of the same proof system like WASM or MIPS for fraud proof.

7/x Option 3: two different types of provers plus governance.

8/x The advantages for option 3 are to avoid to solely trust governance and minimize the chance to have simultaneous bugs in different types of provers.

9/c To conclude, #ZK-EVMs won’t be bug-free for long time. To minimize the chance of bugs, we need multiple implementations from #op/zk rollups. The governance can be considered only when emergency happens.

10/x thanks for @toghrulmaharram from @Scroll_ZKP and @EspressoSys @benafisch’s invite and hosting the events.

11/x More talks and panels. @Inphi @optimismFND shared about EIP 4484 and how it can help rollup protocols to reduce the cost.

11/x Panel to discuss building new apps using rollups especially privacy apps as #L3 from @lukejdpearson @polychaincap @jaosef @aztecnetwork @Oskarlso @worldcoin

12/x our friend @stonecoldpat0 @infura_io shared about the various bridge approaches and how to do proper validation for them. Meanwhile, he also left a bunch of open problems for rollups.

13/x @ben_chain @optimismFND @TrustlessState @BanklessHQ @gitcoin discussed how to fund public goods, especially the experience in gitcoin and OP.

14/x ZK-EVM panel with @bkiepuszewski @MakerDAO @yezhang1998 @Scroll_ZKP @jbaylina @0xPolygon @jadler0 @fuellabs_ @optimismFND. With the public testnet launch of Polygon ZK-EVM, other zkrollup protocols are also speeding up. Censorship is still a big issue for rollups atm.

15/x #MEV impacts a lot of apps and users on @ethereum and it’ll happen on various #L2s, too. @toghrulmaharram @tarunchitra @robotventures @DCbuild3r @ObadiaAlex @GuilleAngeris @AnotherJannik

16/x Data availability crucial to rollups. Depending on the security requirements, we have diff types of DA layers.Proto-Danksharding is vital to next stage of scaling @ethereum. DA panel from @drakefjustin @sreeramkannan @eigenlayer @Jskybowen @CelestiaOrg @dankrad @protolambda

Bonus: #DevCon speaker welcome reception. Looking forward to an amazing @EFDevcon this week.

Share this Scrolly Tale with your friends.

A Scrolly Tale is a new way to read Twitter threads with a more visually immersive experience.
Discover more beautiful Scrolly Tales like this.

Keep scrolling