Repository navigation
B A R R E T E N B E R G · L 1 · 6 · 1 · 0
Date: 2026-11-19 · Tag: v6.1.0 · Baseline: v6.0.0 · Minor release, no protocol changes
npm: @aztec-foundation/bb.js@6.1.0 · crates.io: barretenberg-rs 6.1.0 · Noir: v1.0.0-rc.3 (unchanged)
Summary
v6.1.0 is a maintenance release on the v6 line. It brings Barretenberg hardening and memory work, a world-state fix, and the governance payload that configures per-registry sequencer rewards through the AZIP-31 reward calculator.
It does not change the protocol. Protocol circuits, verification keys, the VK tree, protocol contracts, genesis constants and the core L1 contracts (rollup, inbox, outbox, GSE, governance) are identical to v6.0.0. v6.0.0 and v6.1.0 interoperate.
Node operators and application developers should read the aztec-node release notes instead.
Who should upgrade
- Direct Barretenberg users (
bb,@aztec-foundation/bb.js,barretenberg-rs): recommended. The MSM and SRS checks below close input-validation gaps, and peak prover memory is lower. - Governance participants reviewing the registry rewards payload: the contracts and deploy script ship in this release.
- The Aztec network: no action needed.
Barretenberg
- MSMs reject inputs that need more points than they are given (#25854). The batch MSM used to truncate an oversized member silently, and the single-MSM paths disagreed with each other. All paths now reject it.
CommitmentKeyalready checked the bound, so production commitments were not affected. - SRS integrity checks are refactored (#25817). The BN254 CRS is checked against the pinned chunk hashes when a verification key is computed, and the result is cached per CRS.
bb verifystarts faster because the per-process check is cheaper. - Lower prover memory (#25731). Proofs and VKs are unchanged.
- Pippenger arena sizing fixes (#25680). Very large MSMs (around 2^23 points and up) no longer abort on the arena bound or over-reserve memory.
- Translator tail values are indexed by stride (#25874), a refactor with no proof change.
- bb.js starts with 40 pages of wasm memory instead of 37, to match the module's larger declared initial memory.
Behavior changes for direct callers
These only affect code that drives Barretenberg's lower-level APIs. The bb CLI, bb.js and barretenberg-rs handle both.
- Computing a verification key from a BN254 CRS that is not a whole number of 2^17-point chunks now throws. The native loaders and bb.js already round up; a caller that installs a CRS directly must supply whole chunks (#25817).
- A lookup entry that is absent from its table now fails during circuit construction, including VK construction, instead of later during proving (#25731).
World state
wsdbwrites always run on a separate thread (#25788).
L1 contracts
The core contracts are unchanged. New periphery contracts:
ZeroRegistryRewardsPayload(#25689, #25726): a governance payload that deploys a governance-ownedRegistryReductionCalculator, sets the checkpoint reward to zero for a list of ATP registries, and installs the calculator on the rollup.RegistryReductionCalculator,IATPandProbeLibmove fromtest/tosrc/periphery/.- The calculator resolves every checkpoint on its own instead of deduplicating repeated proposers, saving about 50k–66k gas per proof at a typical epoch (#25720).
DeployZeroRegistryRewardsPayload.s.soldeploys the payload on mainnet for sequencers to signal for (#25729).- Foundry moves to 1.8.5; the L1 build is bytecode-identical (#25677).
Noir and protocol circuits
Packable::unpackforboolnever fails (#25632): any non-zero field unpacks totrue, matchingDeserializeandFromField. No protocol circuit or protocol contract bytecode changes.noir_jsbuilds on Node 26 (#25694).
Build and CI
- v6 builds on the 3.2 build images and accepts wasi-sdk 27 or newer (#25679).
- The
labssubmodule is pinned to aztec-node'sv6branch (#25796).
Full diff: v6.0.0...v6.1.0