Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

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

Abierto Apto para principiantes
  • ¿Algo no está bien?
#2,908 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
1/5
Tiempo estimado
Menos de una hora
Aptitud para principiantes
72/100
Tipo de issue
Documentación
Claridad
Bien especificado
Estado de actividad
Activo
Área
documentation

Línea de trabajo

El ejemplo está en la sección de explicaciones de campos de docs/platforms/anchor-platform/admin-guide/assets-and-client-wallets.mdx. Lee esa explicación genérica del ID de activo y el texto que la rodea, y luego añade una etiqueta de Stellar Testnet al ejemplo del emisor de USDC y una nota que indique que los emisores difieren entre Testnet y Mainnet. Enlaza la tabla de direcciones de contrato de USDC de Circle para los valores de producción. Se da por terminado cuando el ejemplo está etiquetado y el fixture de Testnet se mantiene sin cambios en el resto de la documentación.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
MDX
Estrellas
144
Forks
322
Merge medio
2 d 16 h
PR fusionados (30 d)
23

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de stellar/stellar-docs

Todos los issues de stellar/stellar-docs

Issues similares

Más issues de Documentation

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.