Implement Application-Based Bounty Selection Flow (Model 2)

[0xdevcollins]

Feature: Complete Application-Based Bounty Selection Flow

Overview

While the frontend has partial Application model support, it is incomplete. The full Model 2 flow requires: proposal submission with portfolio, creator-side application review dashboard, applicant selection triggering exclusive claim, and escrow lock on selection. The contract's apply(), select_applicant(), submit_work(), and approve_submission() methods need proper frontend integration.

Depends on: #139 (TypeScript contract bindings)

---

Goals

• Contributors submit structured proposals (approach, timeline, portfolio)
• Creators review applications in a dashboard with comparison tools
• Selection triggers on-chain assignment via select_applicant()
• Selected contributor submits work via submit_work()
• Creator approves and releases escrow via approve_submission()

---

Contract Methods Used

BountyRegistry.apply(applicant, bounty_id, proposal)
BountyRegistry.select_applicant(creator, bounty_id, applicant)
BountyRegistry.submit_work(contributor, bounty_id, work_cid)
BountyRegistry.approve_submission(creator, bounty_id, points)

---

Implementation Details

1. Enhanced Application Form

Modify: components/bounty/application-dialog.tsx

• Structured fields: approach, estimated timeline, relevant experience
• Portfolio/past work links
• Proposal preview before submission
• Calls apply() contract method

2. Creator Application Review Dashboard

Create: components/bounty/application-review-dashboard.tsx

• List all applications with:
  • Applicant reputation score and tier
  • Proposal summary
  • Past completion stats
  • Timeline estimate
• Side-by-side comparison mode
• "Select" / "Decline" actions per applicant
• Selection calls select_applicant() on-chain

3. Post-Selection Work Submission

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

• Selected applicant sees "Submit Work" form
• Upload/link deliverables (stored as IPFS CID)
• Calls submit_work() on-chain
• Status moves to InReview

4. Creator Approval Panel

Create: components/bounty/submission-approval-panel.tsx

• View submitted work
• "Approve & Release Payment" with reputation points input
• "Request Revisions" with feedback
• Calls approve_submission() to release escrow

---

Files Affected

Modified

• components/bounty/application-dialog.tsx
• app/bounty/[bountyId]/page.tsx

Created

• hooks/use-bounty-application.ts
• components/bounty/application-review-dashboard.tsx
• components/bounty/submission-approval-panel.tsx

---

Acceptance Criteria

• Structured application form with proposal fields
• Creator sees all applications in review dashboard
• Selection triggers on-chain assignment
• Selected contributor can submit work
• Creator can approve and release payment
• Rejected applicants notified
• Full flow works end-to-end with contract calls

[linear]

BOU-156

[coderabbitai]

🔗 Related PRs

#60 - feat: Implement Model-Specific Claim/Apply/Join Actions [merged]
#90 - feat:implement sponsor review dashboard. [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!

[Abidoyesimze]

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

Hi maintainer, i'd like to work on this issue
Kindly assign this to me

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Abidoyesimze 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! 🚀

[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! 🚀

[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! 🚀

[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! 🚀

[drips-wave]

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

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