Add a buy cooldown configuration input on the creator dashboard to set the per-wallet buy delay

[Chucks1093]

Summary

Creators can set a buy cooldown period on-chain but have no UI for it. A cooldown input on the creator dashboard settings tab should let creators set a delay in minutes between consecutive buys by the same wallet.

Scope

• Add a Buy Cooldown section to the creator dashboard settings tab
• Show the current cooldown duration converted from ledgers to minutes
• Render a number input for minutes (0 = no cooldown, max 60 minutes)
• Convert the input to ledger units (approximately 1 ledger per 5 seconds) before submitting
• Submit via the set_buy_cooldown contract function and show a success toast on confirmation

Acceptance Criteria

• Current cooldown displayed in minutes on mount
• Input constrained to 0–60 minutes
• Minutes converted to ledger units correctly before submission
• Success toast shown after contract confirmation
• 0 minutes shown as 'No cooldown' in the display

ETA: 12 hours

---

Coordinate on Telegram

[Teejay2696]

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

I can fix this

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

[johnvin489-cloud]

@johnvin489-cloud has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

I’ve worked on similar issues before, I can deliver a perfect solution to this issue

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

[Abyy8]

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

Hi Maintainer, I’ve reviewed the issue and I’d like to work on it. I can add the buy cooldown settings to the creator dashboard, including the current cooldown display, input validation, ledger conversion, contract submission, and confirmation toast.

I’ve noted the 12-hour ETA and will make sure the work is delivered on time, with the required acceptance criteria covered.

Please consider assigning this issue to me. Thank you.

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

[ugoocreates-pixel]

@ugoocreates-pixel has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hello, I would love to take on this issue. I'm a software engineer with over 4 years experience. and i'm confident I can resolve this issue

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

[Outlaw1299]

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

I can work on this, please assign this issue to me

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

[Ultra-Tech-code]

@Ultra-Tech-code has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hi Maintainer, I’m a web3 fullstack developer. I’ve reviewed issue #411 and understand the requirements. I’d like to implement this and submit a clean PR.

My approach:

• Add admin-only settlement proposal and approval flows.
• Store proposals with the proposing admin and repayment details.
• Require approval from a different admin before settlement execution.
• Prevent self-approval with SameAdminApproval.
• Emit proposal and approval events and clear the proposal after execution.
• Add comprehensive tests covering authorization, self-approval, execution, events, and storage cleanup.

Kindly assign this issue to me.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Ultra-Tech-code to this issue.

[BaseDev-Eth]

@BaseDev-Eth has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

hello maintainer, i would love to work on this issue

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

[edehvalentine236-jpg]

@edehvalentine236-jpg has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hello maintainer kindly assign

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

[Ranjeet2063]

Hi maintainers, I would love to take up this issue.

I am a senior Web3 frontend engineer (#1 contributor on Mova Store with 28 successfully merged PRs), specializing in Next.js, React, TypeScript, Tailwind CSS, and Freighter/Stellar wallet integrations.

🎯 Technical Execution Plan for Issue #889:

1. Component Design & UI State: Implement Issue #889 with clean component decoupling, responsive layouts, accessible forms/modals, and robust loading/skeleton/error boundaries.
2. Web3 & Client Logic: Wire real-time state streams, optimistic UI updates, and seamless Freighter wallet transaction signatures with user-friendly error alerts for rejections/timeouts.
3. Comprehensive Test Suite: Add component and unit tests (Vitest / Jest + React Testing Library) verifying state changes, input sanitization, and edge-case rendering.
4. Production Verification: Confirm zero TypeScript errors (noImplicitAny), zero ESLint/Prettier warnings, and clean production build (pnpm build).

⚡ Commitment:

• Ready to deliver a clean, production-ready PR within 12–24 hours.
• Quick turnaround on maintainer suggestions or review comments.