[Backend] — Prediction History CSV Export

[Olowodarey]

Labels: backend, enhancement, predictions

Problem

Users cannot export their prediction history for record-keeping or tax purposes; data is only available through paginated API reads.

Requirements

1. Add GET /predictions/export returning a streamed CSV of the caller's predictions.
2. Support date-range filtering.
3. Stream results to avoid loading all rows into memory.
4. Set correct content-type and attachment headers.

Acceptance Criteria

• The endpoint returns a valid CSV of the user's predictions.
• Date filtering narrows the export correctly.
• Large exports stream without excessive memory use.
• Tests cover header, content, and filter behavior.

Files

backend/src/predictions/predictions.controller.ts, backend/src/predictions/predictions.service.ts, backend/src/predictions/dto

[morelucks]

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

Hello,

I’m a smart contract and full-stack developer interested in contributing to this issue.

I have experience contributing through OnlyDust and have participated in Drips Wave 1, Wave 2, Wave 5, as well as the GrantFox beta campaign.

My technical background includes Rust, Soroban, Cairo, Solidity, and TypeScript, with a focus on building secure, scalable, and maintainable blockchain applications.

Based on the scope of this issue, I’m confident I can deliver a complete and well-tested solution within 24 hours of assignment. I prioritize clean code, clear documentation, and efficient implementation.

I’d appreciate the opportunity to contribute and help move this issue forward.

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

[Emmanuellsensai]

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

I'd like to work on this issue.

Plan:

• Add a GET /predictions/export endpoint in predictions.controller.ts that accepts optional date-range query params.
• Implement streaming CSV generation in predictions.service.ts using Node streams to avoid loading all rows into memory.
• Add DTO validation for date-range filtering in the dto folder.
• Set response headers for content-type (text/csv) and attachment (Content-Disposition).
• Add unit tests covering endpoint response, CSV format, date filtering, and memory-efficient streaming.

I'll wait for assignment before opening a PR.

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

[nayt9]

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

Hello sir , my name is Nathan. I’m smart contract developer, and I’d love to contribute to this project. I’m comfortable working with modern frontend tools and blockchain technologies, and I can deliver tasks quickly often within 24 hours.
Please let me know how I can get started or if there are any issues suitable for a first contribution.

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

[abdullahilateefat03-boop]

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

Hello maintainers,
I’m interested in taking up this issue. I have experience in Full-stack web development. After reviewing the issue requirements, I believe I can implement a proper solution and follow the project guidelines.
Kindly assign the issue to me.
Thanks.

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

[Danitello123]

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

Good day maintainer
Please kindly assign me this issue

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

[chi797]

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

Good day maintainer
Please kindly assign me this issue

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

[devsimze]

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

Hi I'd like to work on this issue

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

[drips-wave]

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

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