DX-070: Write /get-started/testnet

[IbrahimIjai]

Context

The deployment is on testnet today (packages/contracts/contracts.json). A
reader must never be confused about whether the money is real, and must be able
to tell which network they are on without guessing.

Scope

• Which networks are supported, which is default, and how to tell at a glance in
  the interface.
• The testnet passphrase and RPC endpoint, sourced from the committed
  configuration rather than retyped.
• How to obtain testnet XLM and SO4 test assets, linking to the faucet guide.
• An explicit statement that testnet assets have no value and testnet state can
  be reset without notice.
• What changes when mainnet arrives, and what will not.

Acceptance criteria

• Network values match packages/contracts/contracts.json and are rendered
  from it where possible, not hardcoded.
• The "no value, may be reset" statement is unmissable on the page.
• Faucet and wallet pages are cross-linked.
• check:content and check:links pass.

Out of scope

• The faucet walkthrough itself (DX-080).

---

Spec: docs/dx_1/003_content_map.md §2 · Depends on: DX-069

[Abioladory123]

@Abioladory123 has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hello! I’d be happy to contribute to this task.

I’m comfortable picking up unfamiliar codebases, tracing existing behavior, and making focused changes without disrupting other functionality. I’ll take ownership of the implementation from understanding the requirements through testing and final verification.

I’d appreciate the opportunity to work on it.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Abioladory123 to this issue.

[Ay-obami]

@Ay-obami has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hello I'll like to work on this issue

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Ay-obami to this issue.

[drips-wave]

Congratulations, @Ay-obami! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

🧑‍💻 @Ay-obami: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊