Add cooldown enforcement to bonding curve trade functions

[Chucks1093]

Summary

Extend the bonding curve buy and sell functions with per-wallet cooldown enforcement, blocking trades within the creator-configured cooldown window after the last trade.

Scope

• cooldown_duration stored per key in creator config
• buy and sell functions check last_trade_time per wallet before executing
• set_cooldown(key_id, duration) — creator-only config update
• get_cooldown_status(key_id, wallet) — returns active flag and expires_at
• CooldownViolation error returned with time_remaining on blocked trade

Acceptance Criteria

• Trade blocked correctly within cooldown window
• Trade succeeds after cooldown expires
• set_cooldown validates duration within allowed range
• get_cooldown_status returns correct expires_at
• CooldownViolation error includes seconds_remaining

ETA

24 hours

[Okorie2000-code]

The issue description is clear, Maintainer I would love to work on this issue

[guptakumarranjeet150]

Hello team,

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

• Implement Add cooldown enforcement to bonding curve trade functions with thorough authorization verification and clean data structures.
• Cover contract calls with hermetic unit tests verifying events and token balances.

Ready to deliver a clean, tested PR within 12–24 hours. Please assign!

[funds0033-cmyk]

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

Pls kindly assign

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

[oscarj007]

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

Please assign me boss

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

[kaiser-dev777]

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

Hello, can I please work on this issue.
‎
‎While I am new to open-source contributions, I am assuring to apply a structured approach to resolve this task. Based on my review of the issue description and the repository structure, here is my technical workflow to tackle this:
‎
‎1. Environment Setup: I will clone the repository locally and verify that the build/development environment matches your documentation requirements.
‎2. Root Cause Analysis: I will locate the specific file types related to the bug and trace the source of the issue.
‎3. Implementation & Testing: I will apply the necessary fixes following your repository's existing styling and structural guidelines, ensuring no breaking changes are introduced.
‎4. Validation: I will perform local verification tests to confirm the issue is successfully resolved before submitting the Pull Request.
‎

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

[drips-wave]

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

🧑‍💻 @funds0033-cmyk: 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!

@funds0033-cmyk's PR #991 was approved and merged by @Chucks1093.

🏆 @funds0033-cmyk: You earned 40 FoxPoints for this contribution! Your current tier: Builder (1,499 total points). Track your full progress on GrantFox.

👏 Great work, @funds0033-cmyk! Keep contributing to accesslayerorg.