Proposal: V5 Payload deployed

Governance
1

Here are the v5 payload and contracts. If you are a staked sequencer operator, please check the verified sources and start signaling ; )

For more info on v5 and this deployment, refer to the official thread: AZUP-2 is Ready for Proposal

name address
RewardExtLib 0xd6e890c615d6f99681a00771c20ed04516288898
ValidatorOperationsExtLib 0xe4f0b9769ca04a6e3d93b5ba732b5ad80797d411
SlasherDeploymentExtLib 0x8b4987f675403b32accfb8640a4a2af83846626d
RollupOperationsExtLib 0x516f010c9ab452d70e0c6f78b9e698249a66d2ac
RewardDistributor 0x555baac4757a89f1ce0c84fa35afe9dd7aa8e1d3
HonkVerifier 0x098f47c00f4df22a8030746eb11378236c24b4bc
Rollup 0x91ff8bbd8ebb07893010d50a48a1609e5ebd8e34
EscapeHatch 0xf459348962f5ea3a9a101826b03a2ce1f459e51a
V5UpgradePayload 0x1bbde48410bf7ad05208cd77de2bfb0e8f8803d8
Slasher 0xcd6855470a01abcd989126a1183fb50673952548
SlashingProposer 0x8a36b8f2ca71d8d8bd98e03ebf8b4d0939daf0ba
SlashPayloadCloneable 0x57576aba1932df7cc30f971acc9d4fc6e86b6e87
RewardBooster 0x4490cab7ce3499353e1b0090b9e530c1ad03b551
Inbox 0x7d4ef0676c2032bbcc09227501d34d86641ab8ca
FeeJuicePortal 0xaf73dd51d1eb8a079bb097f39c832cdd00ac691c
Outbox 0x5b062ab5fd3a66bc7e73b04ced38587673b6a2d7
FlushRewarder 0x5b98ca4dce7b59ccf241d12f81d3d2ecf14e410e

When you are ready to signal, add this to your .env (or docker-compose environment + compose.yml) and restart the node

GOVERNANCE_PROPOSER_PAYLOAD_ADDRESS=0x1bBde48410bF7Ad05208cD77dE2bFb0e8F8803D8

cheers

3 Likes
AZUP-2 is Ready for Proposal
2

The Aztec Labs team has thoroughly reviewed this proposal and found the deployed contracts to match the v5 protocol source.

Bytecode verification

Each of the deployed contracts, together with the V5UpgradePayload, was verified against bytecode compiled from source. All contracts returned either a full match or a partial match. Partial matches are expected and are due to differences in the metadata hash.

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:

0x2b3b6ea4412b9c8f6457a37f91a2870306f8641e07e16a49b68bda6f8bc02892

Protocol contracts hash:

0x2c075866eafc88a1f6f9addc7e337c6e64e45d1cb7fd7c0d612ebcec72aab2ca

Payload actions

The payload executes exactly the following actions, enumerated directly from the deployed payload’s getActions():

  1. Drain the in-service RewardDistributor’s full balance into the newly deployed RewardDistributor
  2. Register the new Rollup in the Registry (making it canonical)
  3. Point the Registry’s reward-distributor pointer at the new RewardDistributor
  4. Register the new Rollup in the GSE
  5. Activate the Escape Hatch on the new Rollup
  6. Migrate available rewards from the old FlushRewarder to the new one

Each action’s target and calldata was reconstructed from the contracts’ on-chain configuration and matched against the live payload.

Contract configuration

The new Rollup, RewardDistributor, EscapeHatch, and FlushRewarder that the payload is wired to match the addresses published in this proposal, and the deployed contracts’ configuration was confirmed to match what was shared with the community.

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.

3 Likes