Add wallet address validation and normalisation

[Lakes41]

Summary

Validate and normalise wallet addresses before they are used in API calls, admin role assignment, member lookup, and mock store keys.

Current Behaviour

Admin role assignment accepts any non-empty string, and the API client interpolates wallet addresses directly into paths. Mock mode stores addresses exactly as entered, so mixed-case or malformed values can create inconsistent member records.

Expected Behaviour

The frontend should reject malformed wallet addresses, normalise valid addresses consistently, and encode addresses safely before sending requests.

Suggested Implementation

Add shared address utilities using viem helpers where suitable. Apply them in the admin role assignment form, LiveAccessApi, MockAccessApi, Gated, and dashboard queries.

Files or Areas Likely Affected

• lib/api/live.ts
• lib/api/mock.ts
• lib/api/types.ts
• lib/utils.ts
• app/admin/members/page.tsx
• components/gated.tsx
• components/admin-guard.tsx

Acceptance Criteria

• Invalid wallet addresses are rejected before admin role assignment
• Valid addresses are normalised consistently in mock and live mode
• Dynamic address path segments are URL-encoded
• User-facing validation messages are shown in the admin form
• Existing mock mode demo behaviour remains usable

Additional Notes

Assumption: address normalisation should not break checksum addresses. Use viem utilities if they are already available through project dependencies.

[Menjay7]

Hi! I came across this issue and would love to work on it. I have experience with similar tasks and I'm confident I can investigate, implement a clean solution, and thoroughly test it before submitting a PR. If the issue is still open, I would appreciate it if you could assign it to me. Thank you!

[Swayymalcolm99]

hi maintainer

I have experience implementing secure input validation and normalization layers for blockchain applications.
I can add wallet address validation and normalization to verify address format, handle casing/format consistency, and reject invalid inputs before processing.
My approach ensures safer transactions, prevents user errors, and provides consistent wallet handling across the application.