Add a watchlist panel for pinned counterparties or assets to components/dashboard/dashboard-page.tsx

[Jagadeeshftw]

Description

Users who transact repeatedly with the same counterparties or hold specific assets have no way to pin them for quick reference on components/dashboard/dashboard-page.tsx; every check requires filtering the full transaction or asset list. A watchlist panel lets users pin a small set of addresses or assets and see their latest balance/activity at a glance.

Requirements and context

• Add a watchlist widget letting users pin/unpin a counterparty address or asset from transaction rows
• Persist the pinned list per-account via the existing wallet-context storage pattern
• Show the latest known balance or last-activity timestamp for each pinned item
• Must be accessible (WCAG 2.1 AA), responsive, and consistent with existing design tokens
• Should be tested and easy to review

Suggested execution

Fork the repo and create a branch

git checkout -b feature/dashboard-watchlist-panel

Implement changes

• Update/Write: components/dashboard/dashboard-page.tsx
• Add/Update tests: components/dashboard/dashboard-page.test.tsx
• Add documentation: design/dashboard-redesign.md
• Annotate accessibility (contrast, keyboard nav, ARIA)
• Validate responsive behavior across breakpoints (sm 640, md 768, lg 1024, xl 1280)

Test and commit

• Run tests: pnpm test (or repo's test command)
• Cover edge cases (empty/error/loading, long text, dark mode)
• Include before/after screenshots and accessibility notes

Example commit message

feat: add a watchlist panel for pinned counterparties and assets

Guidelines

• WCAG 2.1 AA compliance
• Clear documentation and spec hand-off
• Timeframe: 96 hours

[ifygreg01-best]

@ifygreg01-best has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

i would love to work on this issue, already gone through the description and have experience with it, please assign me submit in 6hrs

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

[Binali223]

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

Hi! I'd like to take this issue. I can start right away. Thanks

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

[drips-wave]

Congratulations, @ifygreg01-best! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on July 30, 2026.

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

[drips-wave]

This issue is assigned to @ifygreg01-best via the Stellar Wave Program.

Other assignees have been removed. To reassign, please unassign the current contributor through Drips Wave first.