Skip to content

docs: point the contract standards at the Aztec Foundation's aztec-standards repo, and fix the private FPC salt - #25769

Merged
alejoamiras merged 4 commits into
nextfrom
worktree-docs-standards-links
Nov 5, 2026
Merged

alejoamiras merged 4 commits into
nextfrom
worktree-docs-standards-links

Conversation

@alejoamiras

Copy link
Copy Markdown
Contributor

What changed

  • The contract standards pages and the aztec.js getting-started tutorial now link to AztecProtocol/aztec-standards instead of the archived defi-wonderland/aztec-standards.
  • Links name main in the dev docs, the v6.0.0 tag in the v6.0.0 docs, and the v5.2.0 tag in the v5.2.0 docs.
  • The pages say the standards are maintained by the Aztec Foundation.
  • The standards overview names the npm package, @aztec-foundation/aztec-standards (dev and v6.0.0 docs).
  • In the dev and v6.0.0 docs, the AIP-20, AIP-721, AIP-4626 and Escrow code examples are requoted from aztec-standards v6.0.0, and the text around them now matches that code.
  • The AIP-4626 page now describes the vault as a standalone contract with a separate share token, and carries the repository's not-production-ready warning.
  • The standards overview and the getting-started tutorial now carry the repository's unaudited notice, instead of recommending the standards for production.
  • The Generic Proxy page notes that the contract is an internal test utility upstream, not a standard.
  • The private fee juice pages give the canonical PrivateFPC deployment salt as 1, the value the private-fee-juice package records, instead of 0. The per-deposit bridge salt is unchanged.
  • The v5.2.0 docs get only the new links, the maintainer wording and the salt fix.

…tec-standards repository

The aztec-standards repository under defi-wonderland is archived; the Aztec
Foundation now maintains the standards at AztecProtocol/aztec-standards.

- Source links name the Foundation repository: main in the dev docs, the
  v6.0.0 tag in the v6.0.0 snapshot, the v5.2.0 tag in the v5.2.0 snapshot.
- The pages say the standards are maintained by the Aztec Foundation.
- Dev docs and v6.0.0: the quoted AIP-20, AIP-721, AIP-4626 and escrow
  snippets are requoted from v6.0.0 (same commit as main), with the prose
  that described the old code. The AIP-4626 vault is now a standalone
  contract with a separate share token.
- The standards index and the getting-started tutorial carry the
  repository's unaudited notice instead of recommending the standards for
  production; the vault page carries its not-production-ready warning; the
  generic proxy page says it is an internal test utility upstream.
The private-fee-juice package records its canonical deployment salt as 1
in canonical-deployment.json (enforced by registerPrivateContract's
assertCanonical option), and has since package 5.0.0. The private fee juice
pages said 0. The heading, its anchor and the inbound link follow, in the
dev docs and the v6.0.0 and v5.2.0 snapshots. The per-deposit bridge salt
is unchanged.
…on wording, no dashes in the standards lists
@alejoamiras
alejoamiras requested a review from a team as a code owner November 5, 2026 18:03
@alejoamiras
alejoamiras merged commit d03294c into next Nov 5, 2026
16 checks passed
@alejoamiras
alejoamiras deleted the worktree-docs-standards-links branch November 5, 2026 19:46
alejoamiras added a commit that referenced this pull request Nov 8, 2026
…cs checks (#25775)

Fixes what the v6 release rehearsal turned up, plus a few gaps found
along the way:

- Outdated commands and Node.js versions in the tutorials. Each page now
states the Node.js minimum the Aztec installer enforces for its version,
and docs releases check it.
- Two lost migration notes, restored.
- An overstated claim in the recursive verification tutorial.
- The awesome-aztec description in llms.txt.
- Two docs checks that failed for the wrong reason.
- The v6 docs line now has the contract-standards links and private fee
juice salt that the main docs got in #25769.
- The Immutables page warns that the macro it uses has been archived.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants