docs: correct Sponsored FPC address in getting started on testnet guide - #24471
Closed
critesjosh wants to merge 2 commits into
Closed
critesjosh wants to merge 2 commits into
critesjosh wants to merge 2 commits into
Conversation
danielntmd
pushed a commit
to danielntmd/aztec-packages
that referenced
this pull request
Jul 7, 2026
danielntmd
pushed a commit
to danielntmd/aztec-packages
that referenced
this pull request
Jul 7, 2026
…duces AztecProtocol#24471) (AztecProtocol#24472) ## What Reproduces the changes in AztecProtocol#24471 (originally opened from a fork) so it runs under the org's CI/merge tooling. Corrects the testnet **Sponsored FPC address** and the `v4.3.1` versioned getting-started page to the live `5.0.0-rc.2` testnet values. Two files, +5/−5 (identical to AztecProtocol#24471 — resulting blob SHAs `e7521e40cef` and `56c6a7445df` match): - `docs/docs-developers/getting_started_on_testnet.md` — `SPONSORED_FPC_ADDRESS` `0x261366…7880` → `0x1969946536f0c09269e2c75e414eef4e21a76e763c5514125208db33d7d944d7` - `docs/developer_versioned_docs/version-v4.3.1/getting_started_on_testnet.md` — install/warning version `4.3.1` → `5.0.0-rc.2`, `NODE_URL` `https://rpc.testnet.aztec-labs.com` → `https://v5.testnet.rpc.aztec-labs.com`, `SPONSORED_FPC_ADDRESS` `0x08b888…f765b` → the same `0x1969…944d7` ## Validation Verified against the **live rc.2 testnet** (`https://v5.testnet.rpc.aztec-labs.com`, rollupVersion `2787991301`) via `node_getContract`: - `0x1969946536…944d7` → **deployed** (version 2, contractClassId `0x095a9366d37ca82e92326aa9dea8c917d9a9c859ebdf6a116299c5a9e5f7ef3c`) — the real Sponsored FPC ✅ - `0x261366…7880` → **null** (not deployed) — the wrong value previously on `next` - `0x08b888…f765b` → **null** (not deployed) — the older wrong value in the versioned page ## Notes - Supersedes fork PR AztecProtocol#24471 — that one can be closed in favor of this. - The same wrong FPC (`0x2613…`) is also present on `v5-next`'s `getting_started_on_testnet.md`; a matching correction there is a separate small PR (not included here). --- *Created by [claudebox](https://claudebox.work/v2/sessions/59cd7d98b38b9d90) · group: `slackbot`*
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
The current
getting_started_on_testnetguide setsSPONSORED_FPC_ADDRESS=0x261366b3c0a9b4c30864629556cf282be409e6822b1f3a065fcb7e34f36d7880, but that contract is not deployed on the live testnet (nodehttps://v5.testnet.rpc.aztec-labs.com, version 5.0.0-rc.2). Following the guide as written fails atregister-contract/create-account.Fix
Point
SPONSORED_FPC_ADDRESSat the deployed canonical Sponsored FPC0x1969946536f0c09269e2c75e414eef4e21a76e763c5514125208db33d7d944d7.Verification
node_getContractagainsthttps://v5.testnet.rpc.aztec-labs.com:0x1969…944d7returns a deployed contract instance;0x2613…7880returns null.version-v5.0.0-rc.2docs snapshot, which already uses0x1969…944d7.Scope
Only the current
docs-developerssource had drifted; theversion-v5.0.0-rc.2snapshot (whattestnetdocs serve) is already correct. One-line change.NODE_URLwas already correct.Draft for review.