Add cursor pagination to the event listing endpoint in src/routes/events.ts

[Jagadeeshftw]

📌 Description

src/routes/events.ts lists indexed events without a pagination mechanism, so clients polling for new events have no efficient way to page through a large backlog.

🧩 Requirements and context

• Add cursor-based pagination (e.g. by event id or block/timestamp) with a default and max page size.
• Return a nextCursor in the response when more results are available.
• Preserve stable ordering across pages even if new events are inserted mid-pagination.

🛠️ Suggested execution

1. Add cursor query-param parsing and a stable ORDER BY to the query in src/routes/events.ts.
2. Return nextCursor/hasMore in the response body.
3. Extend src/routes/events.test.ts with multi-page pagination coverage.

✅ Acceptance criteria

• Paginating through all pages returns every event exactly once, in stable order.
• nextCursor is omitted/null on the last page.
• Default page size is bounded and documented.

🔒 Security notes

Cursor values must not be guessable/incrementable in a way that lets a client infer internal row ids beyond what's already exposed.

📋 Guidelines

• Minimum 95% test coverage
• Clear documentation
• Timeframe: 96 hours

[Clement-coder]

@Clement-coder has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Hi,

I'm a full-stack software and blockchain engineer with experience building scalable web applications, backend systems, blockchain integrations, and open-source software.

I'd like to take ownership of this issue. I've reviewed the requirements and have a clear implementation plan to deliver a clean, scalable, and well-tested solution that meets all acceptance criteria and aligns with the project's architecture and standards.

I can start immediately and will provide timely updates throughout the implementation. Looking forward to contributing to the project.

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

[drips-wave]

Congratulations, @Clement-coder! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on July 30, 2026.

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

[Jagadeeshftw]

Thanks for applying here. Please also join our Telegram group here: https://t.me/+vTbe0hOUKrFhNTJl. It helps us keep communication clear while we review contributions.

[drips-wave]

This issue has been completed by @Clement-coder as part of the Stellar Wave Program's 7th Wave 🥳

😎 @Clement-coder: You earned 100 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.