quota-paymaster-v5.0.1-revision.2

Aztec ecosystem packages 5.0.1-revision.2, targeting Aztec 5.0.1. All packages are published with npm provenance attestations via a tokenless OIDC pipeline that re-runs the full test matrix before publishing.

📦 Packages

Package	What it is
@alejoamiras/quota-paymaster	Quota paymaster (QuotaFpc): allowlist-scoped, per-day-quota fee sponsorship — contract + SDK + operator library

🚀 Install

Use 5.0.1-revision.2 with an Aztec 5.0.1 node/sandbox — @aztec/* peer dependencies install automatically. This release is also available under the latest dist-tag.

bun add @alejoamiras/quota-paymaster@5.0.1-revision.2

Verify provenance end-to-end: npm audit signatures

📣 aztec-standards has moved

The Aztec Foundation now owns and publishes aztec-standards as @aztec-foundation/aztec-standards (repo: AztecProtocol/aztec-standards). @alejoamiras/aztec-standards is retired and will receive no further releases — migrate to the Foundation package.

⚠️ Compatibility notes at 5.0.1

• No package-local API changes in private-fee-juice or aztec-benchmark in the initial 5.0.1 release. (revision mode / -revision.N dispatches: hand-edit this section before releasing — it describes 5.0.1, not your fix.)
• Upstream Aztec 5.0.1 includes two breaking changes enforced through the exact @aztec/* peers: the fee payer must be set in the non-revertible phase (#24479), and note-history validation helpers are re-siloed/renamed (#24644).
• The canonical PrivateFPC address CHANGED at 5.0.1 (recompiled bytecode): the 5.0.1 canonical address is 0x1a6d21ce5fd80137df0e99632a4ca17e58a42dc8f6c08191a96ca8ae907a1bc0. The 5.0.0 address 0x257aa8701e8801b2c03a6b03cdf385c4fa9200efda1dc41f94a905980efc86e9 is STALE for 5.0.1 — funds bridged to a stale-version address are unrecoverable. Always read the address from the canonical-deployment.json of the version you install.

📚 Docs & migration

• Per-package usage: private-fee-juice · aztec-benchmark · quota-paymaster
• Migrating from @defi-wonderland/*: scope swap — migration table

Only quota-paymaster changed in this release. Not published at this version (unchanged, still on their previous release): @alejoamiras/aztec-benchmark @alejoamiras/private-fee-juice

quota-paymaster-v5.0.1-revision.1

Aztec ecosystem packages 5.0.1-revision.1, targeting Aztec 5.0.1. All packages are published with npm provenance attestations via a tokenless OIDC pipeline that re-runs the full test matrix before publishing.

📦 Packages

Package	What it is
@alejoamiras/quota-paymaster	Quota paymaster (QuotaFpc): allowlist-scoped, per-day-quota fee sponsorship — contract + SDK + operator library

🚀 Install

Use 5.0.1-revision.1 with an Aztec 5.0.1 node/sandbox — @aztec/* peer dependencies install automatically. This release is also available under the latest dist-tag.

bun add @alejoamiras/quota-paymaster@5.0.1-revision.1

Verify provenance end-to-end: npm audit signatures

📣 aztec-standards has moved

The Aztec Foundation now owns and publishes aztec-standards as @aztec-foundation/aztec-standards (repo: AztecProtocol/aztec-standards). @alejoamiras/aztec-standards is retired and will receive no further releases — migrate to the Foundation package.

⚠️ Compatibility notes at 5.0.1

• No package-local API changes in private-fee-juice or aztec-benchmark in the initial 5.0.1 release. (revision mode / -revision.N dispatches: hand-edit this section before releasing — it describes 5.0.1, not your fix.)
• Upstream Aztec 5.0.1 includes two breaking changes enforced through the exact @aztec/* peers: the fee payer must be set in the non-revertible phase (#24479), and note-history validation helpers are re-siloed/renamed (#24644).
• The canonical PrivateFPC address CHANGED at 5.0.1 (recompiled bytecode): the 5.0.1 canonical address is 0x1a6d21ce5fd80137df0e99632a4ca17e58a42dc8f6c08191a96ca8ae907a1bc0. The 5.0.0 address 0x257aa8701e8801b2c03a6b03cdf385c4fa9200efda1dc41f94a905980efc86e9 is STALE for 5.0.1 — funds bridged to a stale-version address are unrecoverable. Always read the address from the canonical-deployment.json of the version you install.

📚 Docs & migration

• Per-package usage: private-fee-juice · aztec-benchmark · quota-paymaster
• Migrating from @defi-wonderland/*: scope swap — migration table

Only quota-paymaster changed in this release. Not published at this version (unchanged, still on their previous release): @alejoamiras/aztec-benchmark @alejoamiras/private-fee-juice

quota-paymaster-v5.0.1

@alejoamiras/quota-paymaster@5.0.1 — first publish. QuotaFpc quota paymaster (allowlist-scoped, per-day-quota fee sponsorship: contract + SDK + operator library), extracted from dark-forest-aztec with a chain-verified class-id lineage. Attested via provenance (npm audit signatures).

private-fee-juice-v5.0.1

@alejoamiras/private-fee-juice@5.0.1 — first publish under the new package name (renamed from @alejoamiras/aztec-fee-payment, functionally equivalent to aztec-fee-payment@5.0.1-revision.1). Attested via provenance (npm audit signatures).

v5.0.1-revision.1

Aztec ecosystem packages 5.0.1-revision.1, targeting Aztec 5.0.1. A revision of 5.0.1 — same Aztec target (versions are lockstep, so we can't bump the number), shipping repo-side security hardening. Both packages are published with npm provenance attestations via a tokenless OIDC pipeline that re-runs the full test matrix before publishing.

🔧 What's in 5.0.1-revision.1

@alejoamiras/aztec-fee-payment — SDK security hardening (deferred audit findings, opt-in, no default-behavior change for existing callers):

• F-001 — optional maxAcceptableGasCost ceiling on estimateGasSettings (a client-side cap independent of the node, since the FPC deducts the full max with no refund) + a one-time warning when it's omitted.
• F-002 — opt-in assertCanonical on registerPrivateContract (a fail-closed salt/address check before registering) + canonical-deployment.json exported as a package subpath.
• F-003 — removed the unused artifactRegistry module.
• F-004 — stopped shipping the test-only Counter artifact/binding.

Test/benchmark infrastructure (no shipped-code change): the local counter_contract Noir crate was removed and replaced by the stock upstream @aztec/noir-contracts.js SimpleToken as the sponsored application. No contract (.nr) logic changed — the PrivateFPC canonical address is unchanged (0x1a6d21ce5fd80137df0e99632a4ca17e58a42dc8f6c08191a96ca8ae907a1bc0).

@alejoamiras/aztec-benchmark — no functional change; it rides the lockstep revision.

⚠️ Adopting the fixes — you must pin exactly

5.0.1-revision.1 is a prerelease and sorts below 5.0.1 in semver:

• A ^5.0.1 (or ~5.0.1) range will not resolve to it, and existing lockfiles do not move when latest moves.
• To take the security fixes, pin the exact version:

bun add @alejoamiras/aztec-fee-payment@5.0.1-revision.1

Because of this, @alejoamiras/aztec-fee-payment@5.0.1 (the un-fixed base) is deprecated — install 5.0.1-revision.1 instead. (@alejoamiras/aztec-benchmark's latest remains 5.0.1; only fee-payment carries the security revision on latest.)

🚀 Install

Use 5.0.1-revision.1 with an Aztec 5.0.1 node/sandbox — @aztec/* peer dependencies install automatically.

bun add @alejoamiras/aztec-fee-payment@5.0.1-revision.1
bun add -D @alejoamiras/aztec-benchmark@5.0.1-revision.1

Verify provenance end-to-end: npm audit signatures

📣 aztec-standards has moved

The Aztec Foundation now owns and publishes aztec-standards as @aztec-foundation/aztec-standards (repo: AztecProtocol/aztec-standards). @alejoamiras/aztec-standards is retired and will receive no further releases — migrate to the Foundation package.

⚠️ Compatibility notes (inherited from Aztec 5.0.1)

• Upstream Aztec 5.0.1 includes two breaking changes enforced through the exact @aztec/* peers: the fee payer must be set in the non-revertible phase (#24479), and note-history validation helpers are re-siloed/renamed (#24644).
• The canonical PrivateFPC address at 5.0.1 is 0x1a6d21ce5fd80137df0e99632a4ca17e58a42dc8f6c08191a96ca8ae907a1bc0 (unchanged in this revision). The 5.0.0 address 0x257aa8701e8801b2c03a6b03cdf385c4fa9200efda1dc41f94a905980efc86e9 is STALE for 5.0.1 — funds bridged to a stale-version address are unrecoverable. Always read the address from the canonical-deployment.json of the version you install.

📚 Docs & migration

• Per-package usage: aztec-fee-payment · aztec-benchmark
• Migrating from @defi-wonderland/*: scope swap — migration table

v5.0.1

Aztec ecosystem packages 5.0.1, targeting Aztec 5.0.1. Both packages are published with npm provenance attestations via a tokenless OIDC pipeline that re-runs the full test matrix before publishing.

📦 Packages

Package	What it is
@alejoamiras/aztec-fee-payment	Private Fee Payment Contract (FPC) + TypeScript SDK
@alejoamiras/aztec-benchmark	Benchmark CLI + CI tooling (circuit gates, DA/L2 gas, proving)

🚀 Install

Use 5.0.1 with an Aztec 5.0.1 node/sandbox — @aztec/* peer dependencies install automatically. This release is also available under the latest dist-tag.

bun add @alejoamiras/aztec-fee-payment@5.0.1
bun add -D @alejoamiras/aztec-benchmark@5.0.1

Verify provenance end-to-end: npm audit signatures

📣 aztec-standards has moved

The Aztec Foundation now owns and publishes aztec-standards as @aztec-foundation/aztec-standards (repo: AztecProtocol/aztec-standards). @alejoamiras/aztec-standards is retired and will receive no further releases — migrate to the Foundation package.

⚠️ Compatibility notes at 5.0.1

• No package-local API changes in aztec-fee-payment or aztec-benchmark in the initial 5.0.1 release. (Hotfix/-revision.N dispatches: hand-edit this section before releasing — it describes 5.0.1, not your fix.)
• Upstream Aztec 5.0.1 includes two breaking changes enforced through the exact @aztec/* peers: the fee payer must be set in the non-revertible phase (#24479), and note-history validation helpers are re-siloed/renamed (#24644).
• The canonical PrivateFPC address CHANGED at 5.0.1 (recompiled bytecode): the 5.0.1 canonical address is 0x1a6d21ce5fd80137df0e99632a4ca17e58a42dc8f6c08191a96ca8ae907a1bc0. The 5.0.0 address 0x257aa8701e8801b2c03a6b03cdf385c4fa9200efda1dc41f94a905980efc86e9 is STALE for 5.0.1 — funds bridged to a stale-version address are unrecoverable. Always read the address from the canonical-deployment.json of the version you install.

📚 Docs & migration

• Per-package usage: aztec-fee-payment · aztec-benchmark
• Migrating from @defi-wonderland/*: scope swap — migration table

v5.0.0

Aztec ecosystem packages 5.0.0, targeting Aztec 5.0.0. All three packages are published with npm provenance attestations via a tokenless OIDC pipeline that re-runs the full test matrix before publishing.

📦 Packages

Package	What it is
@alejoamiras/aztec-standards	Standardized Aztec contracts: token (AIP-20), vault (AIP-4626), NFT, escrow, dripper, proxy
@alejoamiras/aztec-fee-payment	Private Fee Payment Contract (FPC) + TypeScript SDK
@alejoamiras/aztec-benchmark	Benchmark CLI + CI tooling (circuit gates, DA/L2 gas, proving)

🚀 Install

Use 5.0.0 with an Aztec 5.0.0 node/sandbox — @aztec/* peer dependencies install automatically. This release is also available under the latest dist-tag.

bun add @alejoamiras/aztec-standards@5.0.0
bun add @alejoamiras/aztec-fee-payment@5.0.0
bun add -D @alejoamiras/aztec-benchmark@5.0.0

Verify provenance end-to-end: npm audit signatures

⚠️ Breaking changes at 5.0.0

• aztec-standards: the legacy dist/… deep-import mirror is removed — switch deep imports to the identical artifacts/… paths (target/*.json and deployments.json are unchanged).
• Aztec 5.0.0 upgrade: local PXE state resets on first open (upstream schema change) — re-register accounts and re-sync.

📚 Docs & migration

• Per-package usage: aztec-standards · aztec-fee-payment · aztec-benchmark
• Migrating from @defi-wonderland/*: scope swap + dist/… imports move to artifacts/… — migration table

v5.0.0-rc.2

Aztec ecosystem packages, released in lockstep with Aztec 5.0.0-rc.2 — the first release from this repository, continuing Wonderland's aztec-standards, aztec-fee-payment and aztec-benchmark under the @alejoamiras scope. All three packages are published with npm provenance attestations via a tokenless OIDC pipeline that re-runs the full test matrix (340 Noir TXE tests + 40 integration tests + benchmarks) before publishing.

📦 Packages

Package	Version	What it is
@alejoamiras/aztec-standards	5.0.0-rc.2	Standardized Aztec contracts: token (AIP-20), vault (AIP-4626), NFT, escrow, dripper, proxy — compiled artifacts + TypeScript bindings
@alejoamiras/aztec-fee-payment	5.0.0-rc.2	Private Fee Payment Contract (FPC) + TypeScript SDK for sponsoring transaction fees privately
@alejoamiras/aztec-benchmark	5.0.0-rc.2	Benchmark CLI + CI tooling for Aztec contracts (circuit gates, DA/L2 gas, proving time)

🚀 Install

Package versions track the Aztec version they support — use 5.0.0-rc.2 with an Aztec 5.0.0-rc.2 node/sandbox. @aztec/* peer dependencies install automatically (npm ≥ 7 / bun).

# bun
bun add @alejoamiras/aztec-standards@5.0.0-rc.2
bun add @alejoamiras/aztec-fee-payment@5.0.0-rc.2
bun add -D @alejoamiras/aztec-benchmark@5.0.0-rc.2

# npm — same coordinates; @rc dist-tag also points at this release
npm install @alejoamiras/aztec-standards@rc

Verify the supply chain end-to-end (checks the provenance attestations):

npm audit signatures

⚡ Quick start

aztec-standards — use the compiled contract bindings against a local network (aztec start --local-network):

import { TokenContract } from '@alejoamiras/aztec-standards/artifacts/src/artifacts/Token.js';

const token = await TokenContract.deploy(
  wallet, 'Private Token', 'PT', 18, /* minter */ owner, /* initial_supply_commitment */ 0n,
).send().deployed();

Raw Noir artifacts ship too: @alejoamiras/aztec-standards/target/token_contract-Token.json.

aztec-fee-payment — sponsor fees through the fully-private FPC:

import {
  FPCFeePaymentMethod,
  registerPrivateContract,
} from '@alejoamiras/aztec-fee-payment';

const fpc = await registerPrivateContract(wallet, salt); // no deployment tx needed
const paymentMethod = new FPCFeePaymentMethod(fpc.address, wallet);

aztec-benchmark — add a [benchmark] table to your Nargo.toml pointing at benchmarks/*.benchmark.ts files, then:

aztec-benchmark --suffix _base            # writes benchmarks/<name>_base.benchmark.json
aztec-benchmark --suffix _new --skip-proving   # gates + gas only (fast, CI-friendly)

Each package's README has the full API surface and examples.

🔁 Migrating from @defi-wonderland/*

Swap the scope — import subpaths are byte-compatible with the legacy tarball layout:

- "@defi-wonderland/aztec-standards": "4.2.0"
+ "@alejoamiras/aztec-standards": "5.0.0-rc.2"

Full migration table (including the benchmark CI workflows) in the repository README.

🔍 Notable in this release

• Aztec 5.0.0-rc.2 support: address constructors migrated to the new *Unsafe API (fromBigIntUnsafe, fromStringUnsafe), ContractInstance.contract_class_id → original_contract_class_id.
• Monorepo consolidation: the three packages now share one lockfile, lockstep versioning, and a single-command Aztec bump (bun scripts/bump-aztec.ts <version>).
• Supply-chain hardening: tokenless OIDC publishing with provenance, 7-day dependency quarantine, SHA-pinned CI actions, and a dependency-confusion fix in the benchmark GitHub Action.