Walletconnect quick start
Your first WalletConnect connection needs an app and a compatible wallet with support for the chain you intend to use. The network carries messages between them, while your wallet manages its keys and signing.
Updated on
Check the specific wallet and chain combination
WalletConnect spans ecosystems including Ethereum and its L2s, Solana, Cosmos, Polkadot, and Bitcoin. This network coverage does not establish compatibility for every wallet and app pairing. Check the app's supported chains and your wallet's WalletConnect support for the chain your task requires.
Holding an asset in a wallet and connecting that wallet to an app are different capabilities. An asset balance alone does not confirm the connection will work. A different chain is a useful alternative only when the wallet and app support it and it serves the task you intend to complete.
Choose a QR code or supported app link
Open the app's wallet connection options. For QR pairing, scan its WalletConnect QR code with a compatible wallet's scanner to pass the connection information to the wallet. A supported deep link provides another way to open the request in a wallet, including on the same device. The available route depends on the wallet and app.
The wallet must approve the connection request to establish the connection. Review the intended app and requested chain before accepting. Opening a link or scanning a code is only part of that process.
Separate connection approval from asset permissions
A normal WalletConnect connection does not require entering a private key or recovery phrase into a website. Check the app's address as well as its displayed name; copied branding can disguise a phishing site.
Once connected, an app can send requests to your wallet. Signing a message, granting a token permission, and confirming a transaction have different effects. A cryptographic message signature can prove wallet control, but you still need to read what each request authorizes. Session encryption does not establish that the app or its request is trustworthy, and accepting a connection does not automatically give the app access to all your assets.
An Ethereum connection and a Solana mismatch
Assume a hypothetical app offers Ethereum and Solana connections, while a hypothetical wallet supports WalletConnect on Ethereum only. The selected chain and connection states described here are hypothetical too.
With Ethereum selected, both sides support the same chain. Suppose the wallet presents a connection request for the intended app and Ethereum. After you approve that connection, the app shows the expected account on Ethereum and the wallet lists the app as connected. Together, those observations show a successful connection in this example. They do not show that a payment or trade has occurred.
With Solana selected, the same setup has no supported wallet connection on that chain. Do not approve a request for an unexpected chain. Choose the app's Ethereum option only if it serves your intended task, or use a wallet with confirmed WalletConnect support for Solana. Rescanning a QR code cannot add chain support to the hypothetical wallet.
After establishing the compatible connection, check the account and chain again before responding to an asset permission or transaction request.