Vitalik's rollup stages framework: Stage 0, 1 and 2 explained
Thread321 words
Breaks down Vitalik's framework for how much a rollup relies on trusting humans versus code, with requirements for each stage. Notes Polygon zkEVM as the only stage 1 rollup at the time.
Key claims
Stage 1 requires a security council of at least 8 members with a 75% threshold, majority external
Stage 2 requires upgrade delays of at least 30 days
Polygon zkEVM was the only stage 1 rollup at the time
0/ @VitalikButerin laid out a simple framework to make it easier to identify the extent to which a rollup depends on “trust a group of humans” vs “trust in code”
currently, @0xPolygon #zkEVM is the only "stage 1" rollup. But what does it mean?
🧵 (0/9)
x.com/sandeepnailwal/status/1660311029442650112
1/ let's have a look at how @VitalikButerin defines the different stages:
2/ Stage 0: Full Training Wheels
🔹 The project must identify as a rollup
🔹 All rollup transactions should go on-chain
🔹 A "rollup full node" should be present, ensuring independence and security
3/
🔹 User asset protection and withdrawal should be guaranteed
🔹 Operator's ability to freeze or steal users' assets is restricted
🔹 On-chain posting of new state roots can be done via a multisig, without active fraud proof or validity proof
4/ Stage 1: Limited Training Wheels
🔹 Active fraud proof or validity proof scheme in operation
🔹 A multisig-based override mechanism ("security council") may exist for emergency cases
5/
🔹 Stringent requirements for multisig: >= 8 participants AND >= 75% threshold
🔹 The majority of the participants must be external to the rollup operating organization
🔹 Upgrade mechanism may exist, subject to a mandatory activation delay
6/ Stage 2: No Training Wheels
🔹 Under bug-free code conditions, there should be no group that can post a state root other than the code output
🔹 Security councils can intervene only to adjudicate undeniable bugs
7/
🔹 Rollup must use independent implementations of its state transition function
🔹 Security council can temporarily intervene under certain conditions, such as "prover disagreement" or "prover stuck"
8/
🔹 Upgrades are allowed, but they must adhere to a mandatory delay of at least 30 days
9/ the framework is designed to support the continuous adoption of rollups with the intent to create a fair and transparent environment that ensures that users are aware of the underlying trust assumptions when interacting with early stage rollups
3 images on X
What came next · since 22 May 2023
Since then
Zero has written 1 more piece on the same subject since this one.