TL;DR
azteclabs DockerHub org, not aztecprotocol). Update your watch/pull sources.v6.0.0-rc.1 is Testnet-only. Mainnet binaries ship ~Oct 18, two days before the Mainnet upgrade, for security reasons (see below). Deployment is otherwise identical to the Mainnet stable release.v6 is a new rollup instance - not just a software update. Upgrading and running on the new Testnet is optional but recommended before the upcoming upgrade on Mainnet.
Node software, PXE, Aztec.nr and Aztec.js development and their documentation is moving to a new repository — github.com/aztec-labs-eng/aztec-node. Version 6 of the node software will be released from this new repo, not from the aztec-packages monorepo. Images are now published to the azteclabs DockerHub org instead of aztecprotocol
This is true for both Testnet and Mainnet releases.
Why the split?
AztecProtocol/aztec-packages(unchanged location) will remain the home for protocol-owned code: L1 contracts, circuits, and Barretenberg. This repository will be maintained by the Aztec Foundation.aztec-labs-eng/aztec-node(new) is now the home for Aztec Labs owned code: the node software, PXE, AztecJS and AztecNR. This repository will be maintained by Aztec Labs.
| Date | |
|---|---|
| September 28th | v6 Testnet goes live. Optional but recommended to test your Mainnet setup. |
| October 7th | v6 Mainnet governance signalling starts. Sequencers set GOVERNANCE_PROPOSER_PAYLOAD_ADDRESS |
| ~ October 18th | Aztec Labs release the v6.0.0 sequencers will run on Mainnet. We'll reach out directly with exact timing. |
| October 20th | v6 expected live on Mainnet. |
The image v6.0.0-rc.1 is available here. This is the image to use for Testnet v6 after Sept 28th.
<aside> ⛔
DO NOT USE THIS IMAGE TO RUN SEQUENCERS ON MAINNET
</aside>
Testing your setup with v6.0.0-rc.1 is basically a dry run for the real upgrade on Mainnet, come October 20th.
Critical vulnerability fixes are developed in a private repository. Releasing binaries that contain security fixes make it easier for an attacker to exploit them. In order to give users and infrastructure operators maximal time to migrate, binaries ship as late as possible to when they’re actually needed.
Mainnet v6 upgrade is expected to execute on October 20th, and the binaries you need to run sequencers on the v6 hard fork will be made available on October 18th.