Dispute Flow UI

[dDevAhmed]

📚 Overview

Implement the user flow for opening, viewing, and participating in disputes on contested claims.

---

🎯 Objectives

• Allow users to open a dispute
• Display dispute status
• Allow staking during dispute

---

🧠 Scope

UI

• Open dispute modal / page
• Dispute status badge
• Dispute evidence view
• Stake and vote controls

Logic

• POST POST /disputes
• GET GET /disputes/:id
• POST POST /disputes/:id/vote

---

🎨 Design Reference

Follow canonical designs in:

truthbounty/designs/dashboard/6-claim-detail.png

---

✅ Acceptance Criteria

• User can open dispute
• Dispute state visible
• Voting works
• API integration complete

---

⏳ Complexity & Effort

Complexity: Medium
Estimated Effort: ~0.5–1 day

---

📌 Notes

This issue includes UI implementation and must follow canonical designs in the parent repository.

[drips-wave]

This issue has been added to the Stellar Wave Program and is worth 150 Points.

🧑‍💻 Interested in contributing? Apply to work on this issue on Drips Wave, earn points, and receive rewards.

Warning

Only applications submitted via the apply link above will be considered. Please do not apply by commenting on the issue or opening a PR directly.

🤠 Repo maintainers: You can manage this issue's Points and Complexity on your Maintainer Dashboard here. Please keep an eye on applications and respond quickly 💙

ℹ️ Learn more about Drips Wave

[Georgechisom]

@Georgechisom has applied to work on this issue as part of the Stellar Wave Program's 1st wave.

Hi, I love to work on this issue, please help assign it to me

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

[ussyalfaks]

@ussyalfaks has applied to work on this issue as part of the Stellar Wave Program's 1st wave.

I’d like to contribute by implementing the full user flow for disputes on contested claims. I’ll build the UI for opening a dispute (modal or page), clearly displaying dispute status, evidence, and staking/voting controls, all aligned with the canonical claim detail designs. On the logic side, I’ll integrate the required APIs to create disputes, fetch dispute details, and submit votes, ensuring state updates are reflected in the UI. I’ll also handle edge cases (e.g., invalid states or insufficient stake) and verify the experience is smooth, accurate, and consistent with the platform’s design and behavior.

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

[Chucks1093]

@Chucks1093 has applied to work on this issue as part of the Stellar Wave Program's 1st wave.

Hello DevAhmed, I would like to handle this.

I will implement the dispute UI flow on the claim detail page based on truthbounty/designs/dashboard/6-claim-detail.png, including an open dispute modal or page, a clear dispute status badge, an evidence view, and stake and vote controls.

I will wire the API calls for POST /disputes, GET /disputes/:id, and POST /disputes/:id/vote, type the payloads and responses, and handle loading, error, and success states so voting and staking actions give instant feedback without breaking the page.

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

[simplicityf]

@simplicityf has applied to work on this issue as part of the Stellar Wave Program's 1st wave.

I’d love to take this on since I enjoy building clean, high-stakes interfaces where precision matters. My plan is to bridge the UI and the API by implementing the dispute modal and voting logic exactly as the designs specify, ensuring the staking flow feels seamless for the user. I’ll make sure the state management is solid so the dispute status updates accurately across the dashboard as soon as the API responds.

ETA: 24hrs

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

[edehvictor]

@edehvictor has applied to work on this issue as part of the Stellar Wave Program's 1st wave.

Hi DevAhmed,

I would like to handle this issue. I can implement the Dispute Flow UI, ensuring users can seamlessly open, view, and participate in disputes while adhering to the canonical design.

Implementation Plan:

UI Components: I will build the Open Dispute Modal and Evidence View based on truthbounty/designs/dashboard/6-claim-detail.png. I will include clear Status Badges and interactive Stake/Vote Controls.

API Integration: I will wire the POST /disputes, GET /disputes/:id, and POST /disputes/:id/vote endpoints, strictly typing requests and responses to ensure type safety.

Feedback Loops: I will implement robust loading, error, and success states for voting and staking actions to ensure the interface provides instant feedback without reloading.

ETA: 4–8 hours (0.5–1 day).

I am ready to start immediately.

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

[Macnelson9]

@Macnelson9 has applied to work on this issue as part of the Stellar Wave Program's 1st wave.

Hi team, I’d like to work on this issue.

I’m a Frontend Developer who thrives at the intersection of UI polish + product usability, and I’ve shipped responsive components/pages using Next.js/React + Tailwind (including interactions, animations, and pixel-accurate Figma builds).

What I’ll deliver

Dispute Flow UI implemented to match the design/spec

Responsive behavior (mobile + desktop), no layout breakage

Hover/focus states + accessible semantics

Clean, reusable components and consistent styling

Approach

Review the design/spec and existing code patterns

Build the UI + interactions

QA on multiple breakpoints + open a PR with screenshots/video

If assigned, I’ll start immediately and share progress updates in the PR.

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

[MJ-RWA]

@MJ-RWA has applied to work on this issue as part of the Stellar Wave Program's 1st wave.

I’d like to work on this issue. I have experience implementing interactive dispute and voting flows in React, including modals/pages, status tracking, staking actions, and API integrations.

I can build the dispute UI (open dispute, status badge, evidence view, stake & vote controls) and wire it to the /disputes APIs while following the canonical claim detail designs. This fits well within the 0.5–1 day scope.

Please assign this issue to me so I can get started.

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

[Obiajulu-gif]

@Obiajulu-gif has applied to work on this issue as part of the Stellar Wave Program's 1st wave.

GM maintainer, I would love to implement the Dispute Flow UI end-to-end (open dispute → view dispute → stake/vote) following the canonical claim-detail design, with clean state management, strong UX feedback, and complete API integration.

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

[tali-creator]

@tali-creator has applied to work on this issue as part of the Stellar Wave Program's 1st wave.

I’ve carefully gone through the issue description and taken time to understand the existing codebase and expected outcome. Based on my experience and the scope of this task, I’m confident I fully understand what needs to be done and how it fits into the project’s overall architecture.

I’m a full-stack Stark developer with 4+ years of hands-on experience, and I’m very confident in my ability to deliver a solid, production-ready solution. I’m 100% certain I can complete this task within 24 hours while maintaining code quality, clarity, and alignment with the project’s standards. I’d be glad to take this on and contribute effectively if assigned.

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

[akordavid373]

@akordavid373 has applied to work on this issue as part of the Stellar Wave Program's 1st wave.

I’d like to implement the Dispute Flow UI. I have extensive experience building interactive flows involving modals, state-dependent buttons, and API integrations.

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

[delfinacorr]

@delfinacorr has applied to work on this issue as part of the Stellar Wave Program's 1st wave.

Hello, I would love to take care of the issue. I am a full-stack developer with extensive experience in this area, and it would be a pleasure to resolve it. Thank you very much.

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

[drips-wave]

Congratulations, @edehvictor! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on January 31, 2026.

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