Implement Competition (Best Submission Wins) Bounty Flow

[Benjtalkshow]

Feature: Implement Competition (Best Submission Wins) Bounty Flow

Overview

The Competition model (Model 3) allows multiple contributors to claim a bounty simultaneously, submit work blindly, and the creator selects the best submission. Only the winner receives payment. This flow is documented but completely unimplemented on the frontend.

Maps to approve_contest_winner() and finalize_contest() on the Bounty Registry contract.

Depends on: #139 (TypeScript contract bindings)

---

Goals

• Allow multiple contributors to claim competition bounties (up to max limit)
• Blind submission: hide submissions until deadline
• Creator evaluates all submissions after reveal
• Winner selection triggers escrow release
• Optional consolation prizes for runners-up

---

Contract Methods Used

BountyRegistry.claim_bounty(contributor, bounty_id)
  → Multiple claimants allowed for Contest type

BountyRegistry.submit_work(contributor, bounty_id, work_cid)
  → Each contestant submits independently

BountyRegistry.approve_contest_winner(creator, bounty_id, winner, payout_amount, points)
  → Can be called multiple times for consolation prizes

BountyRegistry.finalize_contest(creator, bounty_id)
  → Closes contest, prevents further approvals

---

Implementation Details

1. Competition Claim UI

Modify: app/bounty/[bountyId]/page.tsx

• For Contest-type bounties:
  • Show "Join Competition" button (not "Claim")
  • Display current participant count vs max (3/5 slots filled)
  • Show submission deadline countdown
  • List participants (without revealing submissions)

2. Blind Submission Panel

Create: components/bounty/competition-submission.tsx

• Submission form hidden from other participants
• Countdown to deadline
• After deadline: reveal all submissions simultaneously
• Display submissions in anonymous or randomized order (optional)

3. Winner Selection Panel (Creator View)

Create: components/bounty/competition-judging.tsx

• Grid/list of all submissions post-reveal
• Scoring rubric display (if defined)
• "Select as Winner" button per submission with payout amount
• "Award Consolation" for runners-up
• "Finalize Contest" button to close

4. Competition Status Display

• Before deadline: "X submissions received" (count only)
• After deadline: All submissions revealed
• After judging: Winner highlighted, results published

---

Files Affected

Modified

• app/bounty/[bountyId]/page.tsx
• components/bounty/bounty-card.tsx (competition badge + slot count)

Created

• hooks/use-competition-bounty.ts
• components/bounty/competition-submission.tsx
• components/bounty/competition-judging.tsx
• components/bounty/competition-status.tsx

---

Acceptance Criteria

• Multiple contributors can join competition bounties
• Slot count displayed (e.g., "3/5 joined")
• Submissions hidden until deadline
• All submissions revealed simultaneously after deadline
• Creator can select winner(s) and set payout amounts
• Contest finalization prevents further changes
• Consolation prizes supported

[linear]

BOU-183

[coderabbitai]

⚠️ Possible Duplicate Issue(s)

• https://github.com/boundlessfi/bounties/issues/141

🔗 Related PRs

#55 - feat-Implement Bounty Status Logic & Anti-Squatting [merged]
#60 - feat: Implement Model-Specific Claim/Apply/Join Actions [merged]
#110 - feat: Implement Earnings & Payout Tracking [merged]
#111 - Feat: implementation logic for single claim model [merged]
#119 - feat: implement submission draft system [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!

[devJaja]

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

Hey! I’d love to work on this issue. I’m a full-stack and smart contract developer with experience across 30+ blockchain projects, including Stellar. I enjoy collaborating on open-source tools and would be happy to help move this forward.

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

[snakefood3232]

I see you're looking to implement the Competition (Best Submission Wins) Bounty Flow, where contributors submit work blindly, and only the best submission is rewarded. I'd handle this by setting up the claim UI to show a "Join Competition" button and ensuring the submission panel hides work until the deadline. I’d create a judging panel for the creator to review submissions anonymously and select a winner. I can have a PR ready in 3 days. I've previously built similar competition-based systems using Next.js, ensuring a seamless user experience.

[Delightech28]

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

I'd like to work on this

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

[Chidubemkingsley]

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

I want to work on this issue because I recently completed a similar state-machine feature for a credit contract — a global draw freeze switch with admin controls, state transitions, and payout mechanics. That work is now merged and live.

Most applicants would be building this from scratch. I already have working patterns I can adapt: admin-only actions, submission deadlines (similar to my freeze/unfreeze toggle), winner selection (similar to admin state change), and secure prize payouts (similar to my reentrancy-guarded draw function).

I wrote 98+ tests for that credit contract, covering edge cases, auth failures, reentrancy attacks, and event verification. I would bring the same thoroughness to this competition bounty flow.

What I will deliver:

• Complete competition flow: create → submit → judge → select winner → claim prize
• Admin controls for winner selection and emergency pause
• Deadline enforcement with configurable periods
• Reentrancy protection on prize payouts
• Full test coverage (happy paths, edge cases, auth failures)
• Event emission for off-chain tracking

Timeline: 3-4 days for full implementation with tests and docs.

Reference: My recent PR on Creditra/Creditra-Contracts (feature/global-draw-freeze branch) shows my work quality — 98 tests, 10 files changed, production-ready code.

I'm confident I can deliver this competition flow efficiently and securely.

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

[morapay-app]

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

I am applying to work on this issue because it is a concrete, scoped improvement in boundlessfi/bounties that I can ship end-to-end with tests and clear acceptance criteria. The title (Implement Competition (Best Submission Wins) Bounty Flow) maps cleanly to a small implementation plan: reproduce the current behavior, add or adjust the minimal surface area (API/UI/config as appropriate), and verify with automated checks plus a short manual pass where needed. I will keep the change focused, document any assumptions, and open a PR that references this Wave issue for traceability.

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

[drips-wave]

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

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