[backend] contractController/ContractUpgradeController list endpoints have no pagination

[Wilfred007]

Description

Both contractController.getContracts() and ContractUpgradeController.listContracts() return the full result set with no pagination. As the number of deployed contracts per organization grows, these endpoints will become slow and return increasingly large payloads.

Where

backend/src/controllers — contractController.getContracts, ContractUpgradeController.listContracts

Acceptance Criteria

• Add page/limit pagination to both endpoints, consistent with other list endpoints
• Add tests asserting paginated responses

[leocagli]

Hi, I'd like to work on this issue. I can add pagination validation (max limit, positive offset checks) to the list endpoints in contractController and ContractUpgradeController. Could you assign me?

[ndyugwu]

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

let me at this

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

[Hassanmovic98]

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

I will fix this scalability bottleneck by adding structured pagination to both contract list endpoints.I will target getContracts and listContracts controllers in backend/src/controllers.I will extract standard page and limit query parameters from the incoming requests.The query layer will enforce consistent pagination defaults if parameters are omitted.This implementation will replace full database scans with bounded, paginated payload windows.The change protects backend memory resources and improves API response times as data grows.I will ensure both endpoints return structured pagination metadata along with the results array.I will write integration tests verifying the exact behavior of page sizing and offsets.The tests will explicitly assert item limits and verify correct boundary calculations.I understand backend API optimization patterns and can implement this cleanly.

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

[Ryjen1]

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

I would like to work on this issue. Happy to contribute

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

[drips-wave]

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

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