# The week on Aztec: proposal 6 heads to its 16 November close with no votes against

Aztec's vote on zeroing checkpoint rewards for investor and employee ATP sequencers has 636M AZTEC Yea and none Nay ahead of its 16 November close. Release candidate 6.1.0-rc.1 is out; both networks stay on 6.0.0.

- Published: 2026-11-15T11:06:56Z
- Updated: 2026-11-15T11:06:56Z
- Chains: Aztec
- Source: https://bitbasic.com/aztec/proposals/6
- Web page: https://bitbasic.com/news/35-the-week-on-aztec-proposal-6-heads-to-its-16-november-close-with-no-votes
- By: BitBasic (https://bitbasic.com), run by BitNordic

Aztec's governance vote on ending checkpoint rewards for investor and employee ATP sequencers closes on 16 November 2026, so far without a single vote against. Separately, a release candidate for the next node version is out, but mainnet and testnet both stay on 6.0.0 for now.

## Proposal 6 closes on 16 November

Proposal 6 runs a payload called ZeroRegistryRewardsPayload. It is the on-chain vote on zeroing sequencer checkpoint rewards for the investor and employee ATP registries, which [BitBasic covered when voting opened](https://bitbasic.com/news/16-aztec-vote-on-ending-checkpoint-rewards-for-investor-and-employee-atp-sequencers). Voting opened on 9 November at 09:02 UTC and ends on 16 November at 09:02 UTC.

As of 15 November around 11:00 UTC, the chain showed 636M AZTEC voting Yea and none voting Nay. To pass, the proposal needs:

- at least 20% of voting power, and at least 100M AZTEC, to vote;
- Yea to beat Nay by more than 33% of the votes.

The votes cast so far meet both conditions. A passed proposal waits 2 days and can then be executed during the following 7 days. If the vote ends as it stands, execution could happen from about 18 November. Until a payload is executed, nothing changes for sequencers. Operators running from the investor or employee registries should follow the outcome, because it affects the rewards their checkpoints earn.

## 6.1.0-rc.1 published, no rehearsal announced

Aztec published release candidate 6.1.0-rc.1 to npm on 13 November 2026, at 19:50 UTC. Stable 6.0.0 is still the latest tag. Aztec's networks page still lists 6.0.0 as the version for both mainnet and testnet.

Aztec's docs say release candidates are for internal validation and testnet rehearsals. They tell operators to switch to an RC "only when an upcoming-release rehearsal is announced on Testnet". BitBasic found no such announcement and no release notes for this RC, so sequencer operators don't need to do anything yet. The docs also say stable releases aim for roughly one a month, usually mid-month.

## The network this week

On 15 November around 11:00 UTC:

- 3,063 sequencers were active, 189 were exiting and none were queued.
- 611.69M AZTEC was staked to sequencers.
- Checkpoints landed in 122 of the last 128 slots (95.3%), so the network rated as Healthy.

The 636M AZTEC in Yea votes is more than the 611.69M staked to sequencers. That suggests governance voting power counts more than sequencer stake alone.

Live figures are on the [Aztec dashboard](https://bitbasic.com/aztec) and the [Aztec sequencer list](https://bitbasic.com/aztec/validators).

## Sources

- [Aztec proposal 6 on BitBasic](https://bitbasic.com/aztec/proposals/6)
- [Aztec governance proposals on BitBasic](https://bitbasic.com/aztec/proposals)
- [Forum: zero sequencer checkpoint rewards for investor and employee ATP registries](https://forum.aztec.network/t/proposal-zero-sequencer-checkpoint-rewards-for-investor-and-employee-atp-registries/8694)
- [Aztec docs: networks and versions](https://docs.aztec.network/networks)
- [npm: @aztec-labs/aztec](https://www.npmjs.com/package/@aztec-labs/aztec)
- [Aztec network data on BitBasic](https://bitbasic.com/api/v1/chains/aztec/network)