Proposal: Aztec Alpha Payload

Governance
1

The payload encoding the Alpha upgrade was deployed. Feeling honored to show it to you, allowing you to review and signal for it immediately.
Payload Address 0x780523FBa95e4Be0Fa09DA0fff5Fab3aBAE7B58e (AlphaPayload)
Repository AztecProtocol/aztec-packages/l1-contracts v4

All newly deployed contracts:

Contract/Library Address
Rollup 0xae2001f7e21d5ecabf6234e9fdd1e76f50f74962
HonkVerifier 0x70aedda427f26480d240bc0f4308cedec8d31348
Slasher 0x64e6e9bb9f1e33d319578b9f8a9c719ca6d46ebb
TallySlashingProposer 0xa4a38fd0108c00983e75616b638ff3321fd26958
SlashPayloadCloneable 0xaa43220b7eb7c8ffe75bc9c483f3c07b0a55b445
RewardBooster 0x1cbb707bd7b4fd2bced6d96d84372fb428e93d80
Inbox 0x8dbf0b6ed495baab6062f5d5365af3c1b2ed4578
FeeJuicePortal 0x2891f8b941067f8b5a3f34545a30cf71e3e23617
Outbox 0xc9698b7adef9ee63f3bf5cff38086e4e836579f0
EscapeHatch 0x8c189ead28d5987a48e522162f9225124d50ad1b
FlushRewarder 0xf1acfb0c6add7104e700b8fad3ea025dbb041f34
EmpireSlasherDeploymentExtLib 0x9E5acE73a6Bf6a5f7B568b097EEeeDa7ae4131e9
RewardExtLib 0x0965DcC1FB0e3E365bef711eCBc1F2a0cB42dccD
RollupOperationsExtLib 0x121Cf7910d5b0F7B61EB24C6E8F4F94AF7a2e53F
TallySlasherDeploymentExtLib 0x38637f83b5Cb11A48cC54C5BB6E2AfcF7B6ad6C5
ValidatorOperationsExtLib 0x723BE41F7477a1129b516b150603fE745FEE9E0E
AlphaPayload 0x780523fba95e4be0fa09da0fff5fab3abae7b58e

Contract explorer

To make reviews or simple source code surfing easier, i added the contracts to the L2BEAT disco contract explorer, where you can see the old (current) contracts, the payload and the new contracts, with some added descriptions and the source code nearby. Check it out here. I would recommend you to give the new contracts different colours than the old ones.

aztec alpha in disco ui
aztec alpha in disco ui3840×1961 1.19 MB

Sequencer Signaling

(recommended: environment variable)

To signal support for the Alpha payload persistently (survives node restarts), set the sequencer payload address via the environment variable:

# Add this to your .env (or docker-compose environment) and restart the node
GOVERNANCE_PROPOSER_PAYLOAD_ADDRESS=0x780523FBa95e4Be0Fa09DA0fff5Fab3aBAE7B58e

References

7 Likes
Alpha Upgrade is Ready for Proposal
2

:partying_face: :confetti_ball: :tada:
Awesome job!

Excited for Aztec Alpha!

3 Likes
3

The future of Ethereum is private. Aztec is making it inevitable! Congratz!:tada:

2 Likes
4

added some more tools and links to explore the deployed contracts!

4 Likes
5

Very cool. And very useful. Going to pick up a lot form this in terms of understanding and examples for our Aztec explorer

1 Like
6

The Aztec Labs team has thoroughly reviewed this proposal and found the deployed contracts to match what was made available to the community.

Bytecode verification

Each of the deployed contracts was verified using forge verify-bytecode against Etherscan. All contracts returned either a full match or a partial match. Partial matches were expected and they are due to differences in the metadata hash.

Payload actions

The payload executes exactly the six actions described in the proposal:

  1. Register the new Rollup in the Registry (making it canonical)
  2. Register the new Rollup in the GSE
  3. Enable rewards claiming on the new Rollup
  4. Update the Escape Hatch to the newly deployed contract
  5. Migrate claimable rewards from the old FlushRewarder to the new one
  6. Update the Governance execution delay to 30 days

Contract configuration

Configuration values of the deployed contracts were confirmed to match what was shared with the community.

Testnet validation

The same version of the protocol is live on testnet as release 4.1.0-rc.2 on the aztec-packages repository, producing blocks, proofs, and attestations. It will be promoted to a stable release 4.1.1 prior to the execution of the Alpha upgrade.

Security

For context on the security model and trust assumptions during the Alpha phase, please refer to this post: Alpha Network Security: What to Expect.

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.

5 Likes