Build cooldown status API for rate-limited creator keys

[Chucks1093]

Summary

Implement an endpoint that returns the current cooldown state for a wallet/key pair, including time remaining, so the client can enforce trading restrictions accurately.

Scope

• GET /keys/:keyId/cooldown?wallet= — returns active flag, expires_at, seconds_remaining
• Cooldown state indexed from last trade event per wallet per key
• Cooldown policy (duration) returned alongside status
• Batch endpoint GET /cooldowns?wallet=&keys= for portfolio page
• Cache per wallet/key pair with TTL equal to cooldown duration

Acceptance Criteria

• Single endpoint returns correct active flag and seconds remaining
• Batch endpoint handles up to 50 key IDs per request
• Cooldown policy duration returned correctly from contract config
• Cache expires precisely when cooldown ends
• Post-trade hook invalidates cooldown cache for the trader

ETA

12 hours

[guptakumarranjeet150]

Hi maintainers,

I would love to take this on. My planned approach:

• Deliver Build cooldown status API for rate-limited creator keys with proper loading/error states and clean component architecture.
• Test across viewport breakpoints and ensure 0 TypeScript or linting errors.

I am ready to start immediately—please feel free to assign this to me!

[ponmileleke54-dev]

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

I would like to work on this

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

[Solvecraft000]

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

Tbh, this really caught my attention, I’d love to take this on! I’m a full-stack engineer experienced in modern web development, APIs, debugging, and open source projects. I’ve got the skills to tackle this. Assign it to me, and I’m ready to get started!

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

[Samuel-21-eng]

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

I would like to work on this one

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Samuel-21-eng to this issue.

[ChukwuebukaJohnDev]

@ChukwuebukaJohnDev 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 issue please assign

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

[drips-wave]

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

🧑‍💻 @Samuel-21-eng: 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 🌊