No mainnet stress test report — production readiness is unverified

[winsznx]

Priority: P1 · Area: Mainnet

docs/MAINNET_DEPLOYMENT.md documents the procedure but not empirical performance. There is no record of throughput under load: concurrent agents paying simultaneously, channel open/close latency distribution, dispute simulation. Mainnet milestones require evidence of production readiness.

Proposed fix: Write scripts/stress_test.ts running 50-100 simulated agent sessions on testnet concurrently, recording p50/p95/p99 latency for channel open, payment, and close. Publish docs/MAINNET_STRESS_TEST.md.

---

RouteDock Drip Wave 6 backlog.

[Kayce10]

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

Hello Maintainer, I have read through the project Issue can I solve it

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

[oscarj007]

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

Please maintainer,
Permit me to solve this issue for you

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

[AGWAM001]

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

Hello Maintainer, would love to take this issue

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

[boalambo]

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

Hello maintainer, I would like to work on this issue

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

[drips-wave]

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

🧑‍💻 @boalambo: 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 marked as completed by a Drips Wave moderator for @boalambo as part of the Stellar Wave Program's 6th Wave 🥳

Moderator's reason: [Auto-assessed] The contributor successfully addressed the issue by creating the requested stress test script and publishing a detailed performance report in the documentation. The PR also includes relevant SDK build fixes that ensure the test suite and project can run correctly.

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

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

ℹ️ Note: This issue was marked complete via moderation. Points were issued even though the GitHub issue remains open.