Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Label the Circle USDC issuer example as Stellar Testnet in the Anchor admin guide

Open Beginner friendly
  • Is something wrong?
#2,908 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
72/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Domain
documentation

Research direction

The example sits in the field-explanations section of docs/platforms/anchor-platform/admin-guide/assets-and-client-wallets.mdx. Read that generic asset-ID explanation and the surrounding text, then add a Stellar Testnet label to the USDC issuer example and a note that issuers differ between Testnet and Mainnet. Link Circle's USDC contract-address table for production values. Done when the example is labeled and the Testnet fixture is left unchanged elsewhere in the docs.

Written by the indexing model from the issue text.

Description

raven

[!NOTE]
Automated notice: Stellar Raven filed this issue from its automated evaluation pipeline. The issue includes evidence and a public source record. Please verify the live surface before you act.

Finding

The Anchor Platform admin guide uses Circle's Testnet USDC issuer without a network label.
Its asset-ID explanation says the example represents Circle USD.
The page does not identify that issuer as Testnet or distinguish the Mainnet issuer.
Readers can copy a valid Testnet asset ID into Mainnet instructions.

The example is valid on Testnet.
The verified defect is its missing network scope, not an invalid issuer address.

Evidence

The Assets and Wallet Clients guide gives this example:

stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5

The source snapshot has the same network-free explanation.
The page contains no Testnet, Mainnet, or network qualification.
Both live reads succeeded on 2026-10-09.
This observed commit does not establish the first commit that omitted the label.

Circle's current address table assigns the displayed issuer to Stellar Testnet.
It assigns a different issuer to Stellar Mainnet:

GA5ZSEJYB37JRC5AVCIA5MOP4RHTM335X2KGX3IHOJAPP5RE34K4KZVN

A downstream consumer copied this issuer into a Mainnet answer.
That mistake does not prove that this page was the only cause.

A source scan found 51 occurrences of the Testnet issuer.
The path-payment example explicitly labels it Stellar Testnet.
Several create-account examples use TESTNET_USDC_ISSUER.
Those labeled examples do not support a broader wrong-address claim.
The smallest verified correction belongs in this admin guide's generic asset-ID explanation.

Additional recorded evidence:

Recommendation

Label the example as Circle USDC on Stellar Testnet.
State that asset issuers differ between Testnet and Mainnet.
Link Circle's current issuer table for production configuration.

Keep the Testnet issuer in development examples.
Check repeated generic issuer explanations for missing network labels.
Do not replace Testnet fixture addresses across the docs with Mainnet addresses.

Source Record

Raven recorded this finding as sd-057 (stellar-docs, discovered 2026-10-09).

Public source record: improvements/stellar-docs/sd-057-anchor-admin-usdc-network-label.md

Immutable source snapshot: 6f2ddd72b3a2

Resolution Handoff

When you deploy a fix, link the resolving issue or pull request to the source record.
Then notify Raven through:

https://github.com/stellar-experimental/stellar-raven/issues/new?template=upstream-improvement-ready.yml&title=%5Bupstream-ready%5D%20sd-057%3A%20

Include the finding ID and the resolving issue or pull request.
Include the deployed version or timestamp. Include the smallest live recheck.
Raven verifies the live surface before it sets the finding to fixed-upstream.
An issue closure or merged pull request does not prove the fix.
A separate reviewer repeats the live check before Raven retires the active finding.
Raven keeps a commit-pinned snapshot when one is available.

Dominant language
MDX
Stars
144
Forks
322
Avg merge
2d 16h
Merged PRs (30d)
23

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from stellar/stellar-docs

All issues in stellar/stellar-docs

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.