[TESTING] Write performance tests for verify endpoint under load

[dev-fatima-24]

Priority: medium

Description

The public verify endpoint is the most frequently called endpoint and must perform well under load. Performance tests should establish a baseline and catch regressions.

Acceptance Criteria

• Load test simulates 100 concurrent requests to GET /v1/verify/:wallet
• P95 response time is under 500ms with caching enabled
• P95 response time is under 2000ms without caching
• Test is implemented with k6 or Artillery
• Results are stored as a CI artifact for comparison

[chiscookeke11]

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

Hello Sir,

I recently came across the issue regarding writing performance tests for the verify endpoint under load, and I’m very interested in contributing to this project.

I have experience working with backend systems, API performance testing, and load testing tools such as k6 and Artillery. I also understand how to establish performance baselines and detect regressions in high-traffic endpoints.

From reviewing the issue, I understand the goal is to ensure the verify endpoint maintains strong performance under concurrent load conditions. I’m confident I can contribute to:

• Writing load tests simulating 100 concurrent requests to GET /v1/verify/:wallet
• Implementing performance scenarios with and without caching enabled
• Validating P95 response time thresholds (under 500ms with cache, under 2000ms without cache)
• Setting up k6 or Artillery test scripts aligned with CI execution
• Configuring CI artifacts to store and compare test results for regression tracking

I focus on building reliable test systems that help maintain backend performance and stability under real-world conditions. I’m a fast learner, highly motivated, and available to get started immediately.

I would appreciate the opportunity to contribute and would be glad to discuss the next steps.

Thank you for your time and consideration. I look forward to hearing from you.

Best regards,
Chinedu

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

[daree-dev]

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

Would like to work on this issue

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

[drips-wave]

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

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