📊 Feat: NFT Analytics & Aggregation Service

[Cedarich]

Title: feat(analytics): implement collection stats and floor price history
Complexity Score: 200 points

Description
Provide historical data analysis for collections, such as volume over time, floor price trends, and holder distribution.

Requirements and Context

• Entities: CollectionStats (date, volume, floor_price, sales_count).
• Aggregation: A scheduled job should calculate these stats daily/hourly from the Sales history.
• API: Endpoints to fetch charts data (e.g., [timestamp, value]).

Suggested Execution

1. Create AnalyticsService.
2. Implement a Cron job that runs at midnight.
3. Query the Sale entity to sum volumes and find min price for each collection.
4. Save results to CollectionStats.
5. Expose GET /collections/:id/stats.

Test and Commit

• Test aggregation logic with mock sales data.
• Commit Message: feat(analytics): implement collection stats and floor price history

---

[rosemary21]

@rosemary21 has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

I’d love to work on this issue because analytics is where product value really becomes visible to users. Collection-level insights like volume over time, floor price trends, and holder distribution directly impact user decision-making and platform engagement. Implementing a reliable aggregation pipeline for this data is both technically interesting and strategically important.

This task is especially appealing because it sits at the intersection of backend engineering, data modeling, and performance optimization. Designing a scheduled aggregation job that computes metrics from raw Sale records into a structured CollectionStats entity requires careful thinking around

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

[Agbasimere]

@Agbasimere has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

Can I work on this?

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

[aadviksinghdebug]

@aadviksinghdebug has applied to work on this issue as part of the Stellar Wave Program's 3rd wave.

Hi
I’d like to work on this issue if it’s available. I’m a full-stack Web2 & Web3 developer with solid open-source experience and can start working on it right away.

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

[drips-wave]

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

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

[aadviksinghdebug]

@Cedarich please review my PR

[drips-wave]

This issue has been marked as completed by a Drips Wave moderator for @aadviksinghdebug as part of the Stellar Wave Program's 3rd Wave 🥳

Moderator's reason: [Auto-assessed] The contributor has implemented all requirements from the issue including the entity, a cron-based aggregation service, and the API endpoints. The PR has been open for over 24 hours (6 days) with no maintainer response, and the code quality appears high with comprehensive unit tests included.

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

[Oluwaseyi89]

Closed for re-implementation