Docs: Create mainnet launch readiness checklist

[CelestinaBeing]

Summary

There is no comprehensive checklist to validate that Trivela is ready for mainnet. Without a structured readiness review, critical gaps (security audit, TTL misconfiguration, single admin key, no monitoring) may be missed before launch. A public checklist also builds community confidence.

Problem

• No docs/MAINNET_CHECKLIST.md or equivalent
• No formal process for declaring mainnet readiness
• Contributors don't know what "done" looks like for mainnet

Acceptance Criteria

Create docs/MAINNET_CHECKLIST.md with sections and checkboxes covering:

Smart Contracts

• upgrade() entrypoint implemented and tested (issue Contracts: Add upgrade() entrypoint for mainnet Wasm upgrades #278)
• TTL values set for mainnet timing (issue Contracts: Optimize TTL values for mainnet ledger timing #279)
• Participant storage migrated to persistent storage (issue Contracts: Migrate participant storage from instance to persistent storage #280)
• 2-step admin transfer implemented (issue Contracts: Add governance multi-admin pattern to replace single admin key #281)
• All fuzz targets passing (issues Contracts: Add fuzz target for campaign contract registration logic #282)
• Formal security audit completed (external auditor, report linked)
• Contracts deployed and verified on mainnet

Backend

• Event indexer running against mainnet RPC (issue Backend: Implement Soroban event indexer worker #283)
• PostgreSQL or hardened SQLite configured (issue Backend: Add PostgreSQL support as alternative to SQLite #284)
• Database migration system in place (issue Backend: Add persistent job queue with retry and dead-letter support #286)
• Redis caching configured for multi-instance (issue Backend: Add distributed tracing with OpenTelemetry #288)
• Rate limits tuned for expected traffic
• All secrets rotated from testnet values
• Monitoring and alerting configured (issue Frontend: Add multi-wallet provider selector UI #290)

Frontend

• Mainnet contract IDs set in VITE_* env
• All Freighter/wallet errors surface clear user messages
• No hardcoded testnet references remain
• Performance: LCP < 2.5s, CLS < 0.1

Infrastructure

• Mainnet deploy pipeline with approval gates configured (issue Backend: Add load testing suite with k6 or Artillery #289)
• Backup strategy for campaign DB documented and tested
• Incident response runbook documented
• SECURITY.md published (issue Frontend: Add admin on-chain control panel (set_active, set_window, set_max_cap, set_merkle_root) #292)

References

• All linked issues above
• docs/DEPLOYMENT.md

[OlaBakare]

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

I would like to work on this issue because I can handle it

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

[Dataguru-tech]

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

Hi maintainer, I would like to work on this issue

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

[drips-wave]

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

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

[drips-wave]

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

😎 @Dataguru-tech: 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.