Native rollups—superpowers from L1 execution

Layer 2
42

Not to go off on a tangent here, but I’d appreciate if you could point me to any technical writeups or other resources about this.

In my mental model, the user would sign multiple transactions for multiple rollups, then submit these to the (shared) sequencer. Then, how can the sequencer guarantee that they’ll either all execute or all revert? And since reverts are essentially triggered by information outside the EVM (by a previous revert on another rollup), how does this fit into normal EVM semantics?

43

True but the more revert logic you load into the sequencer contract the more gas you’ll use on the L1. My mental model for a lot of this design is that it’s meant to reduce the gas footprint in the block of interop (which would otherwise take up as much gas as a full L1 app)

2 Likes