Milestones for rollups taking off training wheels

The article proposes a three-stage milestone schema for rollups to categorize how heavily they rely on temporary "training wheels," meaning multisig controls that can force outcomes if the code has bugs. Stage 0 requires that all rollup transactions be posted on-chain, that an independently runnable full node exist, and that users can ensure withdrawals without operator cooperation, with a simple multisig allowed for posting state roots. Stage 1 requires a running fraud or validity proof system with practical authority over accepted state roots, and permits a security council override only if it is 6 of 8 or stricter with at least a quorum-blocking group outside the operating organization. Stage 2 requires that, if the code has no bugs, no group of actors can post a state root other than the code's output, with upgrades requiring a delay of at least 30 days.