Mainnet launch readiness checklist + go/no-go tracking

[truthixify]

Labels: Stellar Wave, stellar, governance, drips, help-wanted
Tier: M (2–4 days)
Type: governance

Context

We've never decided what "ready for Stellar mainnet" means. Right now there's an implicit "we'll know when we see it." That's not a process; it's vibes. For a contract that will hold real user funds, we need an explicit, public checklist.

This issue is a governance document, not code.

Scope

Produce contracts/stellar/MAINNET_READINESS.md — a living checklist with explicit pass/fail criteria for each item:

Code quality

• All four contract audits (#01, #02, #03, #04) complete with zero unresolved Critical or High findings.
• Property-based fuzz tests (#05) running nightly with no failures for 30 days.
• Wasm size budget (#17) under threshold for every contract.
• SAC compatibility matrix (#15) signed off.
• Reproducible build attestation (#18) working in CI.

Operations

• Deployment script (#07) tested on futurenet, dry-run-tested for mainnet.
• Upgrade governance (#11) decision finalized and signers configured.
• Multisig hardware-wallet setup verified by independent third party.
• Incident response runbook written.
• On-call rotation defined.

Ecosystem

• SDK tagged at semver-stable release.
• Docs reflect mainnet contract addresses.
• Demo deployable against mainnet (toggle on Stellar wallet).
• Spectre agent verified end-to-end on a small mainnet test transaction.

Communication

• Blog post draft published as preview.
• Status page monitoring mainnet endpoints.
• security@usewraith.xyz email actively monitored.
• Bounty program live with payment infrastructure.

Risk acknowledgments

• Documented list of "known limitations of v1" — features that won't be in mainnet launch (e.g., social recovery, vault contract). Each with rationale.

Sign-off

• Maintainer team consensus recorded.
• Date-stamped go/no-go meeting minutes committed.

Acceptance criteria

• MAINNET_READINESS.md committed.
• Each line item links to its tracking issue or PR.
• A GitHub project board mirrors the document so progress is visible.

Why this matters

When we DO launch on mainnet, we want the document to read as a confidence builder: "every box is checked, here's the link to each piece of evidence." When we DON'T launch, the document tells us exactly why.

[Nemenwq]

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

Hello maintainer, I have reviewed the task description and will like to work on this issue please. ETA: 6hours. Thank you

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

[drips-wave]

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

🧑‍💻 @Nemenwq: 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]

Resolved by #31 (merged into develop).

[drips-wave]

This issue has been completed by @Nemenwq as part of the Stellar Wave Program's 5th Wave 🥳

😎 @Nemenwq: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.