What is WalletConnect?
WalletConnect is an open protocol that lets a mobile software wallet (hot wallet) talk to desktop dApps without a browser extension. It pairs your phone and a dApp session using either a QR code or a deep link, then relays JSON-RPC requests for signing transactions and messages. The main benefit is convenience: you keep private keys on your phone while authorizing actions from a desktop interface.
In my experience this flow balances usability and self-custody well. But remember: convenience adds exposure compared with a hardware wallet.
Quick step-by-step: how to use WalletConnect with Trust Wallet
Here’s a practical, repeatable flow for how to use WalletConnect with Trust Wallet (the steps below assume you have a funded software wallet and the Trust Wallet app installed).
- Open the desktop dApp (Uniswap-style or other DeFi dApp) and click Connect > choose WalletConnect.
- A WalletConnect QR code appears on the desktop.
- Open Trust Wallet on your phone, tap Settings (or the DApps/Browser area) and choose WalletConnect or Scan QR code.
- Scan the desktop QR code with your phone camera and confirm the session in the wallet (review requested permissions).
- Approve account access. The dApp now sees your address and can request signatures (you must approve each transaction on your phone).
If your desktop shows a deep-link button instead of a QR code, and you’re connecting from a mobile browser, choose the deep link. But if you see an error like “wallet connect deep link not supported,” switch to QR scanning or open the dApp in a different browser.
Want step-by-step install help first? See the install on iPhone and install on Android guides.
Mobile QR vs deep link: which flow to use
- QR code: Best when you’re sitting at a desktop and your phone can scan the code quickly. Reliable. Works across most wallets.
- Deep link: Convenient when you open the dApp on mobile and want the wallet app to open directly. Faster, but sometimes blocked by the browser or the wallet if versions are mismatched.
And yes, the deep link flow sometimes fails even when everything seems up to date. That’s usually the browser or the dApp’s WalletConnect implementation. So keep the QR fallback in mind.
Mobile vs extension vs desktop — which form factor
Here’s a short comparison of common setups and trade-offs.
| Use case |
Mobile (Wallet + WalletConnect) |
Browser extension |
Desktop native dApp (rare) |
| Best for |
Mobile-first DeFi, quick approvals |
Power users, multi-account workflows |
Large tooling (analytics, trade grids) |
| Security |
Private keys on device (hot wallet) |
Keys in browser extension (hot wallet) |
Varies (often connected to extension) |
| UX for dApps |
Approve on phone, view on desktop |
Approve in-browser popup |
Depends on app |
| Network switching |
Quick but a mobile tap |
Fast, single-click |
Usually manual |
Short sentence. Longer explanation follows: if you swap tokens daily, the WalletConnect flow saves steps because you can use a desktop interface while still signing on your phone.
Security, permissions and revoking sessions
WalletConnect sessions persist until you disconnect them. That means a compromised phone or careless session approvals are real risks. I believe the most common mistake people make is approving token allowances without checking the contract call (approve with unlimited allowance is common). What I’ve found: always review the method and the amount the dApp is requesting.
Checklist when connecting
- Review requested methods (eth_sendTransaction, personal_sign, etc.).
- Check which accounts and chains are being requested.
- Avoid unlimited token approvals unless you understand the smart contract.
- Use the wallet’s session list to disconnect after use.
Disconnect a session: open Trust Wallet > Settings (or WalletConnect panel) > Active Sessions > tap Disconnect. Want to remove approvals too? Use a revoke tool or follow our revoke approvals and allowances guide.
WalletConnect security note: modern versions encrypt session traffic through a relay and rotate keys, but the human layer matters most — do not approve unexpected signatures.
Troubleshooting: walletconnect qr code, wallet connect deep link not supported and more
Common problems and quick fixes.
- QR code won’t scan: clean the camera lens, increase screen brightness, or open the dApp full-screen on desktop. If scanning still fails, try taking a screenshot and use the wallet’s "Scan from image" (if available).
- wallet connect deep link not supported: this usually means the browser failed to hand off the special URL to your wallet app. Remedy: open the dApp in a different mobile browser (Chrome vs Safari), update the wallet app, or use the QR code fallback. But if the app still blocks the link, reinstalling the wallet sometimes clears stale URL handlers.
- Stuck session: if a session shows as connected but the dApp can't see updated balances, try disconnecting and reconnecting. Also verify you’re on the same network (Ethereum mainnet vs an L2).
If you run into persistent problems, check troubleshooting and our walletconnect guide.
Practical tips for DeFi: swaps, staking, bridges
If you swap often, a dApp with a good aggregator can save you money (fewer hops, better routes). When you confirm a swap, inspect the function call in the approval screen (you’re approving a specific contract call, not giving access to random addresses). I once approved an allowance I didn’t mean to; it took extra steps to revoke, and that taught me to always set expiration or exact amounts.
Staking and liquid-staking flows usually open approval windows and then a stake/lock transaction. The wallet will prompt for two or more signatures in sequence — that’s normal. For cross-chain bridges, WalletConnect simply signs the required transactions; the bridge itself is the bigger security decision. See our bridging cross-chain and gas-fees pages for more.
Who should use this setup — and who should look elsewhere
Best for:
- Mobile-first users who want desktop dApp UI and self-custody.
- People who approve transactions regularly but still want to keep private keys on their phone.
Not for:
- Users who prioritize hardware-level key security above all else (use a hardware wallet instead).
- People who can’t be diligent about disconnecting sessions or revoking allowances.
If you’re unsure, read our security-features and backup-recovery guides before connecting.
FAQ
Q: Is it safe to keep crypto in a hot wallet?
A: Hot wallets trade some security for convenience. They’re fine for everyday DeFi activity if you follow best practices (strong device security, seed phrase offline, revoke approvals when needed). For large holdings, consider a hardware wallet.
Q: How do I revoke token approvals after connecting via WalletConnect?
A: Use our revoke-approvals-and-allowances guide or a reputable revoke tool. Disconnecting a session does not automatically revoke token approvals (those are smart contract allowances).
Q: What happens if I lose my phone?
A: Restore your wallet on a new device using your seed phrase (see lost-phone-recovery). After restoring, immediately revoke any unused approvals and disconnect unknown sessions.
Final thoughts and next steps
WalletConnect is a practical bridge between phone-held private keys and powerful desktop dApps. It’s not magic — it’s an encrypted messaging channel that still relies on you to approve the right things. In my experience, the convenience pays off if you pair cautious habits with regular cleanup (disconnect sessions, revoke approvals).
Ready to try it? If you need help getting the app set up, follow the install on iPhone or install on Android guide, then return here for the step-by-step pairing flow. And remember: always double-check approval screens before tapping confirm.
