Decentralized Dispute Resolution Flow

[Benjtalkshow]

Feature: Dispute Resolution Workflow for Bounties

Overview

To handle disagreements between sponsors and contributors, we need a formal dispute resolution workflow. This will allow a third-party reviewer to mediate conflicts and make fair decisions.

---

Goals

• Allow contributors or sponsors to raise disputes on bounty applications or submissions
• Track dispute status in the system
• Provide reviewers with a clear interface to see both sides and resolve disputes
• Improve trust and transparency in the platform

---

Implementation Details

1. Update Types for Dispute Status

Modify: types/participation.ts

• Add a new DISPUTED status to:
  • Application
  • Submission
• Ensure the status integrates seamlessly with existing status workflows

---

2. Add Raise Dispute Button

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

• Add a "Raise Dispute" button for active participants
• On click:
  • Trigger dispute creation workflow
  • Optionally prompt for reason/details
• Only visible for eligible users (e.g., the contributor or sponsor involved)

---

3. Create Dispute Review Page

Create: app/dispute/[disputeId]/page.tsx

• Dedicated page for reviewers
• Display both sides of the dispute:
  • Contributor submission / application
  • Sponsor feedback / context
• Provide reviewer actions:
  • Approve contributor
  • Approve sponsor
  • Request additional info (optional)
• Track final decision and update relevant statuses

---

Files Affected

Modified

• types/participation.ts
• app/bounty/[bountyId]/page.tsx

Created

• app/dispute/[disputeId]/page.tsx

---

Acceptance Criteria

• Disputed status is correctly reflected for applications and submissions
• Eligible users can raise disputes from the bounty page
• Reviewers can view both sides and make decisions
• Status updates propagate correctly after resolution
• UI is clear and accessible for both participants and reviewers

---

Testing Notes

• Test raising disputes for active bounties
• Verify reviewer page shows complete context
• Validate dispute resolution updates all affected entities
• Check permissions: only authorized users can raise disputes or review them

---

Additional Notes

• Consider adding notifications for both parties when a dispute is raised/resolved
• Log disputes for audit and transparency
• Keep the workflow extensible for future dispute types or mediation steps
• Ensure accessibility and responsive design for reviewer interface

[linear]

BOU-148

[coderabbitai]

🔗 Related PRs

#38 - Feat/project details page [merged]
#55 - feat-Implement Bounty Status Logic & Anti-Squatting [merged]
#88 - feat: Implement bounties detail page [merged]
#90 - feat:implement sponsor review dashboard. [merged]
#111 - Feat: implementation logic for single claim model [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!

[hinzwilliam52-ship-it]

I've designed a fix for this issue and am preparing a pull request. Ill post the link here in a moment once i am done

[hinzwilliam52-ship-it]

I have opened a Pull Request with the fix here: #136

Thanks!

[zhaog100]

/attempt

[zhaog100]

/attempt