The Aztec Labs team has thoroughly reviewed this proposal and found the deployed contracts above to match the v6 protocol source.
Bytecode verification
Each of the 18 deployed contracts, including the V6UpgradePayload, was verified against bytecode compiled from source. All 18 returned a full match, including the metadata hash. Immutable values and linked library addresses were checked against the deployed configuration.
Rollup verifier
The deployed HonkVerifier is the verifier pinned in the release source, and is the verifier produced by the v6 protocol circuits. Its verification key hash is:
0x1fd4eb1d14be45e05dc78c448eb4f29d7f63e4de95129c4a5e1058cd9837f8a6
The new Rollup is wired to this verifier.
Protocol constants
The protocol circuits and contracts were rebuilt from source and the resulting protocol constants confirmed. The deployed Rollup reports, on L1, exactly the values produced by the build:
VK tree root:
0x22fff5de6ce590153df4468f7f0b152188a803d91b3c9c648b91d93d5913f219
Protocol contracts hash:
0x0f54271c52865841a77aaa66036eed901aff22fdce9f08e123ec8b205c9854d7
Genesis archive root:
0x29eb2c527f8d45276430363214e6c8d709ef3f657a3670ebac3179373d41e5c4
Payload actions
The payload executes exactly the following actions, enumerated directly from the deployed payload’s getActions():
- Confirm that the v5 Rollup is still the canonical rollup
- Confirm that execution falls within the permitted execution window (UK weekdays, 08:00-17:00 London time)
- Draw 1,800,000 AZTEC from the RewardDistributor’s pool, reserved for the v5 Rollup
- Earmark that amount in the RewardDistributor for the v5 Rollup
- Lower the v5 Rollup’s checkpoint reward to 50 AZTEC, keeping its 70% sequencer share
- Install the Escape Hatch on the new Rollup
- Register the new Rollup in the Registry (making it canonical)
- Register the new Rollup in the GSE
- Migrate available rewards from the v5 FlushRewarder to the new one
- Raise the GSE’s proof-of-possession gas limit from 250,000 to 300,000
Disclaimer : This message is provided for informational and technical discussion purposes only. It does not constitute a recommendation, solicitation, or request to signal support for, vote on, approve, reject, or otherwise take any action with respect to any governance proposal. It expresses no view on how any token holder, sequencer, or participant should act or vote. Any governance action described can only occur through independent, decentralized Aztec Governance processes and at the discretion of token holders.