Build Multi-Party Confirmation UI

[KuchiMercy]

Complexity: Medium (150 points)

Description

Create the interface for multi-party escrow confirmations, showing confirmation status for all parties and enabling users to confirm milestone completion.

Requirements and Context

Background:
Escrows may involve multiple parties who must all confirm before release
Clear visibility into who has/hasn't confirmed reduces confusion
Confirmation UI must be intuitive and prevent accidental actions

Problem:
No interface for viewing party confirmation status
Cannot confirm escrow milestones
Multi-party status not clearly displayed

Success Criteria:
Confirmation section on escrow detail page
Party list with confirmation status indicators
Confirm button with confirmation dialog
Signature/message field for confirmation record
Progress indicator (e.g., "2 of 3 confirmed")
Disabled state when user already confirmed
Different UI for buyer vs seller roles
Transaction signing integration

Impact:
Enables multi-party escrow functionality
Provides transparency into confirmation progress
Prevents release disputes due to confusion
Suggested Execution
Fork and branch from main → feat/confirmation-ui
Create components in src/components/escrow/confirmation/:
ConfirmationSection.tsx
PartyConfirmationList.tsx
ConfirmationProgress.tsx
ConfirmDialog.tsx
Integrate into escrow detail page
Implement confirmation service in src/services/confirmation.ts
Build transaction builder for confirmation
Add loading states for confirmation action
Create success animation/feedback
Test and Commit

Testing Requirements:

Party list shows all parties with status
Progress indicator reflects confirmed count
Confirm button disabled if already confirmed
Confirmation dialog requires explicit action
Transaction signing flow completes
UI updates after successful confirmation
Error handling for failed confirmation

PR Must Include:
Screenshot of confirmation section (various states)
Screenshot of confirmation dialog
Video of confirmation flow

Example Commit Message

feat(frontend): build multi-party confirmation UI

• Create confirmation section for escrow detail
• Build party list with status indicators
• Implement confirmation dialog with signing
• Add progress indicator for multi-party escrows
• Handle confirmation states and errors

Closes #15

Guidelines

Require explicit confirmation (not single click)
Show clear feedback post-confirmation
Handle race conditions gracefully
Complete within one Wave cycle
PR description must include Closes #15

[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.

🤠 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

[Akshola00]

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

i would like to work on this, im a skilled frontend developer with experience in building multiple uis, please assign this task to me

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

[AbolareRoheemah]

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

Hello. I’m Roheemah, a frontend engineer with extensive experience in React, Next.js, and modern web technologies. I’m passionate about building intuitive, high-performance user interfaces and would love to tackle this issue. Thanks for considering my application!

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

[Faith-okereke]

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

Hi. This is a great match for me. I have experience building visually appealling UI with great UX and functionality. ETA is 24 hours. I aslo have experience building multi UI, modals and popups.

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

[ojaraa]

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

I am a frontend engineer with over 3 years of experience building modern web applications. I have experience working in health-tech firm and freelance. I enjoy turning complex requirements into clean, functional, and scalable user interfaces. As frontend dev, i pay keen attention to details to make sure i build responsive and functional websites and application. My tech stack include React, Tailwind, TypeScript, Next.js, JavaScript.
I would like to work on this issue because i have reviewed the issue and i have the experience and skill needed to resolve the issue, i can also get done in noting less than 34 hours.

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

[Chucks1093]

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

Hello, I am a fullstack developer. I’ve gone through the repo and the issue, and here’s how I’d solve it:

• Begin by adding a confirmation section to the escrow detail page so confirmation status is visible without navigating away.
• Build ConfirmationSection.tsx as the wrapper that reads escrow parties, current user role, and confirmation state.
• Render all parties in PartyConfirmationList.tsx with clear status indicators showing who has confirmed and who has not.
• Add ConfirmationProgress.tsx to display progress like “2 of 3 confirmed” and update it from shared state.
• Implement ConfirmDialog.tsx that requires explicit confirmation and an optional message or signature before proceeding.
• Disable the confirm action when the current user has already confirmed and show a role specific message for buyer or seller.
• Wire the confirm action to a confirmation service in src/services/confirmation.ts that builds and signs the transaction.
• Add loading, success feedback, and error handling so users always know the outcome of their action.
• Update the UI immediately after a successful confirmation to reflect the new state and prevent duplicate actions.

ETA: 18–24 hours

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

[Emmanex01]

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

Hi, I'm a frontend developer. I have reviewed the details of this issue. and it align within my skillset. I would love to work on it.

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

[Yunusabdul38]

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

Gm Am Yunus an full stack and a blockchain developer, have read the issue description and this match my skill set i will love to work on this and create a pr as soon as possible if am assigned this issue

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Yunusabdul38 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'd love to work on this issue.. I have read and understood the required assignment and will deliver accordingly.

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

[edehvictor]

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

Hi Team,
I can build the Multi-Party Confirmation UI. I will create a robust, transparent interface for tracking and executing escrow milestones.

Implementation Plan:

Component Structure: I will adhere to the suggested structure (ConfirmationSection, PartyConfirmationList, ConfirmDialog) in src/components/escrow/confirmation/.

UI/UX: Implement a clear Progress Indicator (e.g., "2 of 3 confirmed") and distinct visual states for Buyer vs. Seller.

Interaction: Build a Confirmation Dialog that requires explicit action to prevent accidental clicks, handling the async transaction signing state with proper loading feedback.

I am ready to start immediately.

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

[ReinaMaze]

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

Hello
I’d like to work on this issue. I’m a full-stack developer with experience building and maintaining web applications and working within existing codebases. I’ve contributed to open-source projects before and I’m comfortable following guidelines, meeting acceptance criteria, and delivering clean, reliable implementations.

I’m confident I can handle this task effectively and would be happy to be assigned.

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

[Marvelousmicheal]

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

i would like to work on this, im a skilled frontend developer with experience in building multiple uis, please assign this task to me

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