Skip to content
Crypto.world

The Ledger

Aztec Says Alpha V6 Passed Governance Vote, Enters Execution Delay

Aztec holders approved Alpha V6 in a governance vote reported on October 22, 2026, and the network entered an execution delay. The proposed upgrade would move Aztec from its V5 rollup to V6, with the payload still to be executed before V6 becomes canonical.

Aztec Says Alpha V6 Passed Governance Vote, Enters Execution Delay

Aztec holders approved its Alpha V6 upgrade in a governance vote announced October 22, 2026, and the network entered an execution delay ahead of launch. The announcement, reproduced by TradingView from Aztec’s account, did not give an official launch date. Approval is a step in the governance process, not activation of the new rollup: the upgrade payload must still be executed.

A new rollup and a governance payload

AZUP-3, dated September 21, proposes moving Aztec from its V5 rollup to a new V6 rollup. The upgrade package includes 12 governance proposals, or AZIPs, and a payload that registers V6 as canonical. The proposal says V6 is deployed ahead of the proposal, owned by governance and inactive until the payload is executed.

“This upgrade package moves Aztec Network from the v5 rollup to a new v6 rollup that implements ten AZIPs, and its payload carries out two more (AZIP-33 and AZIP-34).”

— The authors of AZUP-3 write.

The forum post describing the proposal’s governance process lists four stages: deploy the V6 contracts, have sequencers signal support, hold a tokenholder vote, then execute the payload after the delay. The October 22 announcement reports that the vote passed and the delay began. It does not say the payload has executed or that V6 is already canonical.

Faster messages and changed rewards

One proposed change, the Fast Inbox, is designed to reduce the wait for L1-to-L2 messages. AZUP-3 says the current process waits for the Inbox tree to seal and then for a two-checkpoint lag, taking 24 to 108 seconds. Under V6, messages would stream into blocks as nodes observe them on Ethereum, with a target of about 12 to 30 seconds.

The proposal also changes how the 500 AZTEC checkpoint reward is divided. The sequencer share rises from 70% to 90%, or from 350 to 450 AZTEC per checkpoint. The block-reward prover pool falls from 150 to 50 AZTEC per checkpoint; fee-based prover revenue is unchanged. Total checkpoint emissions remain 500 AZTEC.

V6 would also let staking providers exit the positions they operate, with a shared rate limit intended to prevent exits from being used to swing a governance vote. Another change raises the proof-of-possession gas cap for new validators from 250,000 to 300,000.

V5 reserve supports migration

Before registering V6 as canonical, the payload earmarks 1.8 million AZTEC for V5 and reduces V5’s checkpoint reward from 500 to 50 AZTEC. AZUP-3 estimates that, at 1,200 checkpoints per day, the reserve can fund V5 sequencing and proving for 30 days. The provision is intended to keep the older rollup operating while users migrate. The proposal says V5 can no longer draw rewards from the RewardDistributor once V6 is canonical; registering V6 makes it canonical.

For now, the announcement establishes that the vote passed and the execution delay began; it does not establish that the payload has run. The proposal’s listed changes would take effect through that execution, which makes the delay part of the path between approval and V6 becoming the canonical rollup.

Sources

  1. Original source Aztec Protocol (GitHub) github.com

Other pages read

  1. TradingView News tradingview.com
  2. Aztec Forum forum.aztec.network

Related stories

Explore

More articles