Stellar testnet vs futurenet vs mainnet differences page

[truthixify]

Tier: S (½-1 day) Type: writing

Context

Three networks. Subtly different. Developers waste hours figuring out why something that worked on testnet broke on futurenet (or vice versa). One reference page settles it.

Scope

Write docs/reference/stellar-networks.mdx:

• Comparison table: passphrase, RPC URL, Horizon URL, friendbot, reset frequency, Soroban version, supported features
• When to use each (testnet for stable demos, futurenet for new protocol features, mainnet for production)
• How to switch (CLI commands, SDK config)
• Common gotchas migrating between them

Acceptance criteria

• Reference page committed
• Comparison table accurate as of date stamp
• Linked from quickstart + SDK Stellar page

Files to start with

• New: docs/reference/stellar-networks.mdx

[ajulaybeeb]

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

Hi Maintainer, I have reviewed the description of the issue and would like to hop on this issue and deliver ETA

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

[AbdulmalikAlayande]

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

Hi maintainer, Please I will like to work on this issue to build the documentation page explaining the differences between Stellar testnet, futurenet and mainnet

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

[drips-wave]

Congratulations, @AbdulmalikAlayande! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 30, 2026.

🧑‍💻 @AbdulmalikAlayande: 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 🌊

[truthixify]

@AbdulmalikAlayande Assigned. Welcome to wave 6.

Quick expectations:

1. Branch from develop (auto-default now).
2. Open a draft PR within ~3 days.
3. Update at least every 5 days; silence costs the assignment.
4. Acceptance criteria in the issue body are the merge bar.

Ask on the issue if anything is ambiguous before building.