[PRODUCT INTEGRITY][DASHBOARD] Remove simulated deposits, withdrawals, and transaction history

[Obiajulu-gif]

Summary

Authenticated financial widgets display fabricated transactions and mark deposits or withdrawals complete after client-side timers. Users can be shown balances and success states that have no ledger or provider backing.

Repository evidence

• components/dashboard/funds-management.tsx:49-94 seeds fake transactions and :97-120 simulates a completed deposit.
• components/dashboard/loan/withdrawal-system.tsx:44-81 renders another hard-coded financial history.

Scope

• Load transaction history from the authenticated ledger API.
• Route mutations through real payment/withdrawal state machines and show pending, confirmed, failed, and unavailable states.

Acceptance criteria

• Production builds contain no fabricated financial records or timer-based success transitions.
• Every displayed transaction links to an authoritative record.

Tests

• Cover empty, loading, provider pending, confirmed, failed, reversed, and stale states.

Non-goals

• Redesigning dashboard visuals.

[privexlabs]

I have experience with React and API integration. I’ll replace simulated financial data with authenticated ledger/payment APIs, handle pending, confirmed, failed, and unavailable states, and add tests for key transaction states.

[grantfox-oss]

🦊 GrantFox — @privexlabs has been assigned to this issue as part of the Third Campaign campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #195)
2. Your PR will be reviewed by the Chainmove maintainers

Good luck! Track your progress on GrantFox.

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox as part of the Third Campaign campaign!

@privexlabs's PR #229 was approved and merged by @Obiajulu-gif.

🏆 @privexlabs: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (742 total points). Track your full progress on GrantFox.

👏 Great work, @privexlabs! Keep contributing to Chainmove.