Build leaderboard endpoint for top creator keys by holder count and volume

[Chucks1093]

Summary

Create a leaderboard endpoint that ranks creator keys by holder count, trading volume, and price performance across configurable time windows.

Scope

• GET /keys/leaderboard accepts sort_by param: holder_count, volume_24h, volume_7d, price_change
• Returns top N keys with rank, key metadata, and sort metric value
• Results cached with 60s TTL per sort dimension
• Limit param accepted up to configured maximum
• Tied ranks handled with secondary sort by creation date

Acceptance Criteria

• Leaderboard ranked correctly for all supported sort dimensions
• Tied ranks broken correctly by creation date
• Results cached per sort dimension with 60s TTL
• Limit param respected up to configured maximum
• Response under 150ms with valid cache

ETA

12 hours

[2ndwave09]

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

Please can I get this fixed? I am very good at what I do. I have read through and understand what needs to be done. I will ensure everything aligns perfectly with your existing contribution guidelines.

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

[ife-daniel]

@ife-daniel has applied to work on this issue as part of the Stellar Wave Program's 9th wave.

Hi maintainer, I would like to work on this

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

[VictorEzenma]

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

I would like to work on this issue

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

[Zikrullah001]

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

I’d like to work on this issue

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

[sojetunde8]

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

I can fix this.

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

[drips-wave]

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

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

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox!

@VictorEzenma's PR #1003 was approved and merged by @Chucks1093.

🏆 @VictorEzenma: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (408 total points). Track your full progress on GrantFox.

👏 Great work, @VictorEzenma! Keep contributing to accesslayerorg.

[drips-wave]

This issue has been completed by @VictorEzenma as part of the Stellar Wave Program's 9th Wave 🥳

😎 @VictorEzenma: You earned 150 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.