Feature: Sponsor Bounty Creation Flow

[Benjtalkshow]

Overview

The platform exposes a createBounty GraphQL mutation but has no UI route to actually create one. Sponsors can only view, review, and approve bounties; they cannot create them through the app. This is a critical missing flow that blocks any new sponsor from listing work on the platform.

---

Goals

• Allow authenticated sponsors to create bounties of all four types (FIXED_PRICE, COMPETITION, MILESTONE_BASED, lightning round)
• Validate inputs client-side (title, reward amount, deadlines, category)
• Wire to the existing createBounty mutation
• Surface success and error states clearly
• Redirect to the new bounty detail page on success

---

Implementation Details

1. Create the bounty creation route

Create: app/bounty/create/page.tsx

• Multi-step form (basic info → rewards/deadline → review)
• Type selector (FIXED_PRICE, COMPETITION, MILESTONE_BASED)
• Reward amount + currency picker (XLM, USDC, EURC)
• Deadline picker
• Optional bountyWindowId for Lightning Rounds
• GitHub issue URL field (required for FIXED_PRICE)
• Cover description (markdown editor optional)

2. Validation

• Min cover description length
• Reward amount > 0
• Deadline must be in the future
• For COMPETITION: require start/end dates
• For MILESTONE_BASED: require at least 2 milestones with payout split summing to 100%

3. Create the mutation hook

Create: hooks/use-create-bounty.ts

• Wraps the generated useCreateBountyMutation
• Invalidates bountyKeys.lists() on success
• Returns toast and redirect

4. Permission gating

Modify: components/global-navbar.tsx

• Show "Create Bounty" CTA only for authenticated users with sponsor role (or organization membership)

---

Files Affected

Created

• app/bounty/create/page.tsx
• hooks/use-create-bounty.ts
• components/bounty/bounty-create-form.tsx

Modified

• components/global-navbar.tsx

---

Acceptance Criteria

• Sponsors can create FIXED_PRICE, COMPETITION, and MILESTONE_BASED bounties from the UI
• Required fields are validated client-side before submission
• Successful creation redirects to /bounty/[id]
• Failed creation surfaces an inline error and keeps form state
• Non-sponsors do not see the Create CTA in the navbar
• Bounty list cache is invalidated on success

[linear]

BOU-185

[coderabbitai]

🔗 Related PRs

#30 - feat: Implement React Query hooks for managing bounties [merged]
#34 - feat: Implement API-driven bounty fetching and display with dedicated loading, empty, and error UI components. [merged]
#111 - Feat: implementation logic for single claim model [merged]
#113 - feat(graphql): add bounty and submission operations and queries [merged]
#117 - feat: add frontend hooks for submission mutations [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!

[snakefood3232]

I see the need to enable sponsors to create bounties in-app, addressing the creation flow via a multi-step form. I'd handle this by building the route with client-side validation and integrating the createBounty mutation, ensuring users are redirected upon success. I can have a PR ready in 4 days. I've built similar multi-step forms and GraphQL integrations in production React/Next.js apps.

[devsimze]

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

Hi maintainer, I'd like to work on this issue

Kindly assign me

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

[Danitello123]

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

I’m a smart contract and full-stack developer who turns complex ideas into secure, production-ready blockchain code.
With strong skills in Rust and Solidity, I build systems that are fast, safe, and built to last.
My experience with the Stellar SDK lets me ship real-world Web3 solutions that actually move value

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

[drips-wave]

Congratulations, @Danitello123! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on April 29, 2026.

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