Aztec's v6 migration starts from a new rollup deployment

Aztec's v6 operator guidance describes a fresh rollup deployment rather than carrying v5 chain state into the new version. Operators need a new data directory and updated artifact locations and configuration names.

The guide supports preparing a v6 node in standby while governance determines when it becomes canonical. A healthy standby endpoint does not mean the node has begun attesting.

That is a useful distinction during protocol migrations: process health, configuration compatibility and participation in the canonical network are separate checks. Operators running multiple replicas also need to preserve the signing history that prevents conflicting signatures.