✳flâneur — a map of the web's best reading

dba: L1s vs. L2s, Rollups vs. Integrated, General-purpose vs. App-specific

dba.xyz · 3,323 words · saved by 1 readers

We need a better understanding of what architectures to build and when. Otherwise, we'll continue to get a mish-mash of confusing infrastructure that no user can understand or interact with. This is the most common mistake I see: As noted in Eclipse's introductory post ahead of their upcoming mainnet launch: There's often a false dichotomy presented between the modular rollup vision vs. the ability to have a single chain with massive scale, parallelized execution, and shared state. "Modular" is often conflated with "app-specific", which would lead you to believe that rollups mean a world of many fragmented and low-throughput chains. We challenge that idea. Rollups and L2s are not bad UX. Fragmented rollups and L2s are bad UX. Properly designed rollups and L2s should improve UX. All chains can eventually adopt the best tech (e.g., DAS + ZK) if it proves useful. As discussed in my last report Do Rollups Inherit Security?, the distinction we're left with then is roughly the following: Sol

L1s vs. L2s, Rollups vs. Integrated, General-purpose vs. App-specific - DBA Skip to content DBA Reader Controls Hide Switch to white theme Switch to yellow theme Switch to black theme Aa Width Export to PDF L1s vs. L2s, Rollups vs. Integrated, General-purpose vs. App-specific Jon Charbonneau 12.8.23 14 min read Loading the Elevenlabs Text to Speech AudioNative Player... Thank you to Mert Mumtaz and Neel Somani for valuable feedback and review. Introduction This short post will describe the concrete tradeoffs of: L1s vs. L2s Rollups vs. integrated App-specific vs. general-purpose We need a bett

Explore this link on the map →

related reading