WalletConnect

Open the app you want to use, hit Connect, and pair your wallet in seconds. On desktop, scan the QR code with your mobile wallet; on mobile, tap the deep link and approve. Pick the account(s) you want to expose, confirm the networks you plan to use, and review the session details (app name, URL, and requested permissions). You can disconnect at any time from either the wallet or the app. If you juggle multiple accounts, switch them from your wallet without breaking the session—your app will update automatically.

When you transact, the app sends a request and your wallet shows a clear prompt. Check the to/from address, value, gas or fees, and data, then approve or reject. For approvals, set a spending cap instead of unlimited to limit risk. If the app asks to change networks, confirm the switch in your wallet or decline and stay put. For NFTs, confirm listing, mint, or transfer flows; for DeFi, verify swap routes and slippage; for governance, review the message before signing a vote. If something fails—stuck pending or wrong chain—cancel the request in the wallet, switch to the correct network, and retry. Using a hardware wallet via a companion app? Pair once, then approve on-device when prompted.

Building an app? Add a connect button with the WalletConnect Modal so users can choose any supported wallet. Initialize the client, request a session with the chains and methods you need (e.g., read balances, sign messages, send transactions), and listen for updates when users switch accounts or networks. Avoid over-scoping: ask only for the permissions you use. Show transaction previews and simulate outcomes where possible. Handle errors gracefully: expired pairings, rejected requests, or network mismatches should surface clear prompts with retry paths. For mobile users, support deep links so they return to your app after signing, and cache sessions so they reconnect instantly on reload.

For teams running multi-chain experiences, keep one session that spans the ecosystems you support and request capabilities per chain, not globally. Offer in-app controls to pick a network, and sync the UI with the wallet’s active chain. Periodically remind users to review allowances and disconnect unused sessions. If QR pairing stalls, refresh the code, check time sync, or try cellular instead of Wi‑Fi—some networks block relay traffic. For support desks, ask users for the app URL, wallet brand and version, chain ID, and a timestamp to trace issues. For security, require domain verification before enabling high-risk actions, disable blind signing where feasible, and log every request and signature with method, chain, and hash for audits.