[V2 200pts] Add withdrawal confirmation modal with full address display and post-submission status screen

[portableDD]

Summary

Add a confirmation step to the withdrawal flow and a post-submission status tracking screen. Withdrawals move real money — users must explicitly confirm the destination address before submission, and must be able to track the withdrawal status after submission.

What Needs to Be Done

1. Withdrawal confirmation modal

Before calling POST /transactions/withdraw, show a confirmation modal:

You are withdrawing:
  500 USDC
  To: GABCD...WXYZ (full address shown, truncated for display)
  
This action cannot be undone. Funds sent to an incorrect address cannot be recovered.

[Cancel]   [Confirm Withdrawal]

• Show the full destination address (not truncated — user must verify it fully)
• Warning text about irreversibility must be visible
• "Confirm Withdrawal" button triggers the API call

2. Post-submission status screen

After successful POST /transactions/withdraw call:

• Show a "Withdrawal submitted" screen (not just a toast)
• Display: transaction ID, amount, currency, destination address, estimated processing time
• "View in transactions" link → navigates to /dashboard/transactions
• "Make another withdrawal" link → resets the form
• Do not navigate away automatically — let the user control the next step

3. components/dashboard/withdraw/withdrawal-confirmation-modal.tsx

• Props: amount, currency, destinationAddress, onConfirm, onCancel, isLoading
• Loading state on confirm button while API call is in flight
• Closes automatically on success (parent handles navigation to status screen)

4. components/dashboard/withdraw/withdrawal-success.tsx

• Shows after successful withdrawal submission
• Props: transaction: Transaction

Acceptance Criteria

• Confirmation modal appears before any API call is made
• Full destination address visible in confirmation (not truncated)
• Irreversibility warning is present in the confirmation modal
• Success screen appears after submission (not just a toast)
• Success screen shows transaction ID and all relevant details
• npm run build and npm run lint pass

---

⚠️ IMPORTANT — READ BEFORE SUBMITTING YOUR PR
Your pull request MUST target the v2 branch.
PRs targeting main or any other branch will not be reviewed and will not be merged.
Double-check your base branch before opening the PR:

Base branch: v2   ✅
Base branch: main ❌  → will be closed without review

Complexity: High — 200 points

[oscar24357]

@oscar24357 has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

hello maintainer, i would love to work on this issue, can you please assign me to it? Thank you

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

[CollinsKRO]

@CollinsKRO has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Good Day maintainer, pls assign me this issue. I'd love to work on it. Thanks.

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

[drips-wave]

Congratulations, @CollinsKRO! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 30, 2026.

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