Repository navigation
AZUP-2: Aztec Network v5 (retroactive) - #71
Draft
iAmMichaelConnor wants to merge 5 commits into
Draft
iAmMichaelConnor wants to merge 5 commits into
iAmMichaelConnor wants to merge 5 commits into
Conversation
Records the v5 rollup upgrade that executed on mainnet on 2026-07-14 (Governance proposal AztecProtocol#4) but was never filed here as the AZUP process requires. Every address is read back from the deployed contracts and cross-checked against Sourcify exact-match verifications; the verified source is byte-identical to the v5.0.0-rc.2 tag, whose payload source is copied into assets/azup-2/. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
…iled Names the refs used to read and confirm the deployed contracts: getter names from tag v5.0.0-rc.2, deployed source confirmed byte-identical to that tag via Sourcify, and unchanged at v5.0.0, v5.0.1 and the v5 branch head. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
…istry instances Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
…tion Copies DeployRollupForUpgradeV5.s.sol from tag v5.0.0-rc.2 next to the payload source, and records every rollup, escape hatch, slasher and entry-queue parameter read back from the mainnet and Sepolia contracts, all matching the script's expected-configuration table. Also records the genesis archive root. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
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
1 participant
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
Files AZUP-2, the v5 rollup upgrade, retroactively. It executed on mainnet on 2026-07-14 as Governance proposal #4 and was announced on the forum on 2026-06-29, but no
azup-2.mdwas ever merged here, which the AZUP process requires (payload merged into/AZUPsand tagged before deployment).What is in it
V5UpgradePayload0x1bBde48410bF7Ad05208cD77dE2bFb0e8F8803D8, the address sequencers signaled for) and theGSEPayloadwrapper thatGovernanceactually stores for proposal AZIP-1: Reduce Governance Execution Delay to 2 Days #4.submitRoundWinner/executetransactions with timestamps.DOM_SEP__CONTRACT_ADDRESS_V2 = 4099338721), the reduced protocol contract set, and the default public-setup allowlist.assets/azup-2/, per the process rule that AZUPs may not link outside this repo and the forum.How it was verified
v5.0.0-rc.2tag of aztec-packages (also unchanged atv5.0.0,v5.0.1and thev5branch head). The copied payload source hashes identically to Sourcify's.Needs a human
author/createdare set to the filer and the forum-post date; adjust if the original proposer should be listed.AuthRegistryinstances exist on mainnet L2 (5.0.0's and5.0.1+'s); the AZUP should say which is canonical.🤖 Generated with Claude Code