Implement Competition (Best Submission Wins) Bounty Flow

[0xdevcollins]

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-151

[coderabbitai]

⚠️ Possible Duplicate Issue(s)

• Application, Competition, and Milestone Submission Logic #52

🔗 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!

[zhaog100]

/attempt

[zhaog100]

/attempt

[zhaog100]

Hi! I'd like to work on this bounty.

My Plan:

• Analyze the requirements
• Implement the solution
• Submit PR within 24-48 hours

Payment Address:

• Platform: OKX
• Token: USDT (TRC20)
• Address: TGu4W5T6q4KvLAbmXmZSRpUBNRCxr2aFTP

Let's get this done! 🚀

[Jayrodri088]

@Jayrodri088 has applied to work on this issue as part of the Stellar Wave Program's 3rd wave.

I’ll implement the full Competition bounty flow (Model 3) with blind submissions, multi‑participant slots, creator judging, and winner selection that maps cleanly to approve_contest_winner() and finalize_contest(). For Contest bounties, I’ll update app/bounty/[bountyId]/page.tsx to show a “Join Competition” button with live slot count (“3/5 joined”), submission deadline countdown, and participant list (anonymous until reveal), replacing the standard claim flow.
​

I’ll create components/bounty/competition-submission.tsx for contestants (form to upload work CID, hidden from others), competition-judging.tsx for creators (post‑deadline grid of revealed submissions with “Select Winner” buttons setting payout amounts, consolation prizes, and “Finalize Contest”), and competition-status.tsx for unified state display (slots filled pre‑deadline, all submissions revealed after). A use-competition-bounty.ts hook will poll bounty state via contract bindings, handle SSE updates for real‑time reveal/judging, and batch contract calls. ETA: 10–12 hours for UI components, state management, contract integration, blind reveal logic, and responsive judging grid.

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

[Oluwaseyi89]

@Oluwaseyi89 has applied to work on this issue as part of the Stellar Wave Program's 3rd wave.

Hi Maintainer! I'd like to implement the complete Competition (Best Submission Wins) bounty flow on the frontend, including the "Join Competition" UI with participant count and deadline display, blind submission panel that hides submissions until deadline, winner selection interface with scoring rubric support for creators, and competition status components that reveal submissions after deadline and highlight winners once judged, all integrated with the Bounty Registry contract methods for claiming, submitting, approving winners, and finalizing contests.

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

[Jopsan-gm]

@Jopsan-gm has applied to work on this issue as part of the Stellar Wave Program's 3rd wave.

Hello maintainers 👋

I’ve reviewed this issue and the relevant parts of the codebase. I’m a junior full-stack developer with hands-on experience contributing to real-world open source projects across both Web2 and Web3 contexts. My work includes JavaScript/TypeScript-based stacks, React on the frontend, Node.js on the backend, as well as contributing to blockchain-related repositories, including smart contract logic and protocol-level features.

I’m comfortable reading and understanding existing codebases, reasoning about on-chain and off-chain interactions, and delivering clean, focused implementations aligned with the project’s conventions. I’m used to working through GitHub workflows, iterating based on feedback, and prioritizing maintainability and clarity.

This issue aligns well with my experience, and I believe I can provide a solid and reliable solution. If it’s still available, I’d be happy to take it.

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

[zhaog100]

Hi! I'd like to work on this bounty.

My Plan:

• Analyze the requirements
• Implement the solution
• Submit PR within 24-48 hours

Payment Address:

• Platform: OKX
• Token: USDT (TRC20)
• Address: TGu4W5T6q4KvLAbmXmZSRpUBNRCxr2aFTP

Let's get this done! 🚀