From 8bfd77df3b4b7ccef48999489736ad4f84b0a7e8 Mon Sep 17 00:00:00 2001 From: Josh Crites Date: Wed, 10 Jun 2026 12:26:55 -0400 Subject: [PATCH 1/2] docs: update sponsored fpc address --- .claude/skills/release-docs/SKILL.md | 10 ++++++---- .claude/skills/release-network-docs/SKILL.md | 3 ++- .../version-v4.3.1/getting_started_on_testnet.md | 2 +- docs/docs-developers/getting_started_on_testnet.md | 2 +- docs/docs/networks.md | 2 +- 5 files changed, 11 insertions(+), 8 deletions(-) diff --git a/.claude/skills/release-docs/SKILL.md b/.claude/skills/release-docs/SKILL.md index 6eb78293f32d..75c305769bb5 100644 --- a/.claude/skills/release-docs/SKILL.md +++ b/.claude/skills/release-docs/SKILL.md @@ -79,14 +79,14 @@ returned by the RPC (e.g. the network is still running `4.1.3` but the user wants to prepare docs for `4.2.0`), this is a **pre-release** docs preparation. Ask the user to confirm the target version, then use that version instead of `nodeVersion` throughout the remaining steps. The git tag for the target version -must still exist. Contract addresses from the RPC reflect the *current* network +must still exist. Contract addresses from the RPC reflect the _current_ network state (the old version); they are still valid if the upgrade reuses the same contracts, but ask the user to confirm whether any addresses will change at upgrade time. **Run all work on the tag, not `next`.** Cut on the tag so the snapshot reflects what shipped. Then stash, switch to `next`, pop. Backport any newer -docs from `next` into the snapshot as an explicit step *after* the cut. +docs from `next` into the snapshot as an explicit step _after_ the cut. ### Unversioned root pages @@ -116,9 +116,9 @@ VERSION= bash -i <(curl -sL https://install.aztec.network/) aztec get-canonical-sponsored-fpc-address ``` -Store the address for updating docs. +Store the address for updating docs. Be sure to update the address with the appropriate value wherever it appears in the versioned docs. -**Note:** The Sponsored FPC is only deployed on devnet. For mainnet and testnet releases, +**Note:** The Sponsored FPC is deployed on testnet and devnet. For mainnet releases, mark the SponsoredFPC row as "Not deployed" in the L2 Contract Addresses table. ### Step 5: Update Version Configs @@ -234,6 +234,7 @@ docs (Step 13), the generated content is included in the snapshot automatically. 1. **Triage existing TBD items.** Not all items under `## TBD` necessarily belong to the current release. Review each entry and decide whether it: + - Shipped in this release → move it under the new `## ` heading - Targets a future major version → move it under a new `## Unreleased (v)` heading (create this heading if it doesn't exist, placed between `## TBD` and @@ -250,6 +251,7 @@ docs (Step 13), the generated content is included in the snapshot automatically. 4. Check for missing migration items by analyzing the diff between the previous release tag and the new one: + ```bash git diff v..v -- yarn-project/ noir-projects/ ``` diff --git a/.claude/skills/release-network-docs/SKILL.md b/.claude/skills/release-network-docs/SKILL.md index eeaf2b6ce24e..2c0b07599e2d 100644 --- a/.claude/skills/release-network-docs/SKILL.md +++ b/.claude/skills/release-network-docs/SKILL.md @@ -144,13 +144,14 @@ in each table: - **L1 Contract Addresses table**: update all addresses from the RPC response, on-chain queries, and any additional addresses provided by the user. + - Mainnet: use `https://etherscan.io/address/0xADDR` link format - Testnet: use `https://sepolia.etherscan.io/address/0xADDR` link format - For contracts that are not deployed on this network, use `N/A` - **L2 Contract Addresses table**: update if any canonical protocol contract addresses changed (check the `protocolContractAddresses` from the RPC - response). SponsoredFPC is always "Not deployed" on mainnet and testnet. + response). SponsoredFPC is always "Not deployed" on mainnet. Also grep for any old addresses that may appear elsewhere in the docs: diff --git a/docs/developer_versioned_docs/version-v4.3.1/getting_started_on_testnet.md b/docs/developer_versioned_docs/version-v4.3.1/getting_started_on_testnet.md index 9d755acd9ae0..6bc673862b36 100644 --- a/docs/developer_versioned_docs/version-v4.3.1/getting_started_on_testnet.md +++ b/docs/developer_versioned_docs/version-v4.3.1/getting_started_on_testnet.md @@ -53,7 +53,7 @@ Set the required environment variables: ```bash export NODE_URL=https://rpc.testnet.aztec-labs.com -export SPONSORED_FPC_ADDRESS=0x254082b62f9108d044b8998f212bb145619d91bfcd049461d74babb840181257 +export SPONSORED_FPC_ADDRESS=0x08b888c4be63ed67f61a622fdd013ea028326bac22a8982a3b5a7e9ec62f765b ``` ### Step 2: Register the Sponsored FPC diff --git a/docs/docs-developers/getting_started_on_testnet.md b/docs/docs-developers/getting_started_on_testnet.md index 5f66aff0aa21..674850a5fab2 100644 --- a/docs/docs-developers/getting_started_on_testnet.md +++ b/docs/docs-developers/getting_started_on_testnet.md @@ -53,7 +53,7 @@ Set the required environment variables: ```bash export NODE_URL=https://rpc.testnet.aztec-labs.com -export SPONSORED_FPC_ADDRESS=0x254082b62f9108d044b8998f212bb145619d91bfcd049461d74babb840181257 +export SPONSORED_FPC_ADDRESS=0x08b888c4be63ed67f61a622fdd013ea028326bac22a8982a3b5a7e9ec62f765b ``` ### Step 2: Register the Sponsored FPC diff --git a/docs/docs/networks.md b/docs/docs/networks.md index ffa2d8261fe4..7c3a140925ca 100644 --- a/docs/docs/networks.md +++ b/docs/docs/networks.md @@ -85,7 +85,7 @@ Stable releases target roughly one per month, typically mid-month. Dates are not | **Class Registry** | `0x0000000000000000000000000000000000000000000000000000000000000003` | `0x0000000000000000000000000000000000000000000000000000000000000003` | | **MultiCall Entrypoint** | `0x0000000000000000000000000000000000000000000000000000000000000004` | `0x0000000000000000000000000000000000000000000000000000000000000004` | | **Fee Juice** | `0x0000000000000000000000000000000000000000000000000000000000000005` | `0x0000000000000000000000000000000000000000000000000000000000000005` | -| **SponsoredFPC** | Not deployed | `0x254082b62f9108d044b8998f212bb145619d91bfcd049461d74babb840181257` | +| **SponsoredFPC** | Not deployed | `0x08b888c4be63ed67f61a622fdd013ea028326bac22a8982a3b5a7e9ec62f765b` | ## Governance parameters From 2ed6d2b99bb8b9289f3ba6d5e2f56a25dc08623e Mon Sep 17 00:00:00 2001 From: Josh Crites Date: Wed, 10 Jun 2026 16:41:51 -0400 Subject: [PATCH 2/2] add reminder about funding testnet fpc --- .claude/skills/release-docs/SKILL.md | 1 + 1 file changed, 1 insertion(+) diff --git a/.claude/skills/release-docs/SKILL.md b/.claude/skills/release-docs/SKILL.md index 75c305769bb5..88d7a10b63b1 100644 --- a/.claude/skills/release-docs/SKILL.md +++ b/.claude/skills/release-docs/SKILL.md @@ -120,6 +120,7 @@ Store the address for updating docs. Be sure to update the address with the appr **Note:** The Sponsored FPC is deployed on testnet and devnet. For mainnet releases, mark the SponsoredFPC row as "Not deployed" in the L2 Contract Addresses table. +If the Sponsored FPC address changes for a testnet release, send a reminder that the new address must be funded on testnet. ### Step 5: Update Version Configs