Make wallet and chain configuration environment-driven

[Lakes41]

Summary

Allow supported chains, RPC URLs, and wallet connector options to be configured without editing source code.

Current Behaviour

lib/wallet/providers.tsx hard-codes mainnet, base, and sepolia, uses default transports, and configures only an injected connector. This limits deployment flexibility and makes live environments harder to tune.

Expected Behaviour

Deployments should be able to choose supported chains and RPC URLs through environment variables while preserving safe defaults for local development.

Suggested Implementation

Create a wallet configuration module that parses public environment variables, builds the wagmi chain and transport config, and exposes connector settings. Add validation and fallbacks for mock mode.

Files or Areas Likely Affected

• lib/wallet/providers.tsx
• lib/wallet/config.ts
• .env.example
• README.md
• components/wallet/connect-button.tsx

Acceptance Criteria

• Supported chains can be configured without changing source code
• RPC URLs can be provided per supported chain
• Invalid chain or RPC configuration fails clearly in development
• Mock mode continues to work with default configuration
• README and .env.example document wallet configuration

Additional Notes

Do not add private RPC credentials to client-exposed environment variables unless the provider explicitly supports browser-safe public keys.

[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!

[ZuLu0890]

I would like to work on this issue