Repository navigation
AZUP-3: Aztec Network v6 - #72
Merged
Merged
Conversation
Skeleton for the v6 upgrade proposal, scoped per issue AztecProtocol#60. Records the payload's current action list and flags that the contract address domain separator on `next` is still v5's (DOM_SEP__CONTRACT_ADDRESS_V2 = 4099338721) and must be bumped before the v6 release candidate; the protocol fee margin decision and the public-setup allowlist are marked TBD. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
…ages PR Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Lists each included AZIP (22-30) with the change it makes in v6, and gives the payload's eight mainnet actions in AZUP-1's Contract / Function / Effect format, including the 1.8M AZTEC reservation for v5 and the v5 checkpoint reward cut from 500 to 50 AZTEC. Motivation covers the Fast Inbox, provider exits, protocol fee capture and the Glamsterdam timing. Testnet details, contract addresses, protocol constants, signaling config and open questions are removed.
v6 deploys with no calculator set, so every proposer still earns the default reward; a policy that uses one needs its own AZIP and AZUP. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
…s cap Adds the cap increase to 300,000 as payload Action 9. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
AZIP-34 specifies the existing Actions 3 and 4 (the 1.8M AZTEC v5 earmark and the 50 AZTEC v5 checkpoint reward), so those actions now cite it. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
…tions - Glamsterdam gas constants is AZIP-35 (governance AztecProtocol#68), not AZIP-28 - link merged AZIP-29 and AZIP-30 by relative path - abstract counts the two payload-only AZIPs alongside the ten in the rollup - add author, payload/contract table, pinned-verifier note, sequencer signaling config, Sepolia placeholder and open questions
The limit is 5% of the remaining validator set over Governance's withdrawal delay (votingDelay / 5 + votingDuration + executionDelay, about 9.6 days with mainnet's current configuration), not 7 days. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
docs(azup-3): describe the v6 AZIPs and payload actions
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
iAmMichaelConnor
marked this pull request as ready for review
October 8, 2026 20:22
iAmMichaelConnor
marked this pull request as ready for review
October 8, 2026 20:22
iAmMichaelConnor
changed the title
koenmtb1
approved these changes
Oct 9, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds
AZUPs/azup-3.md, the upgrade package that moves Aztec Network from the v5 rollup to v6. It bundles the AZIPs scoped in #60 plus the later additions, and specifies the governance payload that makes v6 canonical.What the document contains
V6UpgradePayloadcontract, its deploy script, what the script deploys, and the nine actions in execution order:RegistryGSEGOVERNANCE_PROPOSER_PAYLOAD_ADDRESSsetting sequencers use to signal for the proposal.Governance.execute, action ordering constraints, and the payload's test coverage.Still to be filled in
Payload address, v6 release branch and Etherscan link, Sepolia addresses and proposal id, and the audit section. These are recorded once the payload is deployed.
🤖 Generated with Claude Code