Aztec, the privacy-focused Ethereum layer-2, reached L2Beat Stage 2 after its governance system voted to remove admin control over the rollup contract. The move strips any single party—including the team itself—of unilateral power to upgrade or pause the system.
L2Beat's decentralization tiers measure how much control centralized actors retain over a rollup's core infrastructure. Stage 2 is the highest rating and requires that upgrades flow through transparent, on-chain governance with measurable community participation. By revoking admin keys, Aztec cleared that bar: the contract code is now frozen unless token holders vote to change it.
This matters because most layer-2 teams operate differently. They typically hold admin keys—the ability to upgrade contracts, pause transactions, or redirect funds—either in a multisig wallet or behind a timelock. Those controls are sold as safety rails during early operation. They also embed a hard dependency: users must trust the team indefinitely, or until those keys are formally surrendered.
Aztec's move is not symbolic. It creates a real technical constraint. Once admin keys are revoked on-chain, they cannot be recovered. Any future change to the rollup's logic requires a governance vote and execution through the approved upgrade path. If governance stalls or splits, so does the protocol. The trade-off is concrete: decentralization gains rigidity.
For users, Stage 2 means the rollup cannot be rewritten on a whim. For Aztec's team, it means they can no longer unilaterally patch bugs, respond to security findings, or adjust parameters without waiting for a vote. The governance system becomes the bottleneck and the guarantee.
L2Beat does not rate rollups on throughput, privacy guarantees, or UX. Its criteria focus on the locus of control: who can modify the code, who can pause the system, who holds sequencer power. Stage 2 is a statement about structural decentralization, not performance or security.
Aztec's privacy architecture—the core product—is separate from this governance decision. Revoking admin keys does not alter how the rollup obscures transaction details. It simply means that choice is now locked in by code, not by team policy.