Harden wallet address display and handling across Members and Passes UIs

[Lakes41]

Difficulty: Advanced
Type: security

Background
Member management includes wallet info per the README's feature list, and wallet addresses are sensitive, easily-mistyped identifiers that are commonly mishandled in dashboards (full exposure, no checksum validation, easy-to-fumble copy actions).

Problem
Wallet addresses are likely rendered as raw full strings with no checksum/format validation on input, no safe copy-to-clipboard affordance, and no truncation/obfuscation strategy, increasing risk of shoulder-surfing exposure and admin data-entry errors (e.g., adding a malformed address for a member).

Expected outcome
Wallet addresses are validated on input (correct format/checksum for the supported chain), displayed truncated by default (e.g., 0x1234…abcd) with a full-reveal and copy-to-clipboard action, and any wallet-related admin action requires an explicit confirmation step.

Suggested implementation

• Add address format/checksum validation (e.g., EIP-55 for EVM addresses) to the member creation/edit form using a small utility in packages/integration-client.
• Build a reusable WalletAddress display component: truncates by default, expand-on-click, copy-to-clipboard with a success toast, and a link-out to a block explorer.
• Add a confirmation dialog for destructive/sensitive wallet-linked actions (e.g., changing a member's linked wallet).
• Add tests for the validation utility covering valid/invalid/edge-case addresses.

Acceptance criteria

• Invalid wallet addresses are rejected on input with a clear error
• Wallet addresses render truncated by default everywhere they appear
• Copy-to-clipboard works and is covered by a test
• Changing a member's wallet requires explicit confirmation

Likely affected files/directories

• apps/dashboard/app/members/
• apps/dashboard/components/ (new WalletAddress component)
• packages/integration-client/

[bridgetthnkechi87-cloud]

Hello Maintainer,

I would like to work on this issue.

I understand the goal is to make wallet handling safer in the member management flow by validating wallet addresses on input, avoiding full raw address exposure in the dashboard, and adding safer admin actions around wallet changes.

My approach would be to first review the existing member create/edit flow under apps/dashboard/app/members/ and the integration utilities in packages/integration-client/. Then I would add a focused wallet address validation utility, build a reusable WalletAddress display component that truncates by default with reveal/copy/link-out support, and add an explicit confirmation step for sensitive wallet changes.

I’ll also add tests for valid, invalid, and edge-case addresses, including copy-to-clipboard behavior where the project test setup supports it.

I’ll keep the PR focused on wallet validation, safe display, confirmation, and tests.

I’d be happy to take this up if assigned.

[grantfox-oss]

🦊 GrantFox — @bridgetthnkechi87-cloud has been assigned to this issue as part of the Official Campaign | FWC26 campaign!

Next steps:

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

Good luck! Track your progress on GrantFox.

[grantfox-oss]

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

@bridgetthnkechi87-cloud's PR #311 was approved and merged by @Lakes41.

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

👏 Great work, @bridgetthnkechi87-cloud! Keep contributing to Adamantine-guild.