VEYRNOX · Learn · WalletConnect v2

WalletConnect v2

WalletConnect v2 is an open protocol that lets a wallet on one device connect to a dApp on another — most commonly a mobile wallet paired with a desktop dApp — over an end-to-end-encrypted relay. Version 2 introduced multi-chain sessions and a permissioned request model.

How it works

The dApp displays a QR code (or deep link) encoding a topic and a symmetric session key. The wallet scans it, establishes an encrypted channel through the WalletConnect relay, and negotiates the requested chains, methods, and events. Signing requests are pushed from the dApp to the wallet, which surfaces them for user confirmation and returns the signature over the same channel. Sessions persist across restarts and can be revoked from either side. The relay sees only encrypted traffic — it cannot read requests or signatures.

Why it matters

WalletConnect is how mobile self-custody wallets interact with the desktop dApp ecosystem. It eliminates the browser-extension attack surface (compromised extensions have stolen billions) while giving desktop users a keyboard-and-mouse UI. Version 2’s multi-chain sessions let a user connect once and hop between Ethereum, Solana, and other chains without re-pairing.

Related concepts

Frequently asked questions

Is WalletConnect the same as a browser extension?

No. WalletConnect is a device-to-device protocol; browser extensions run inside the browser. WalletConnect avoids extension-based malware.

Can WalletConnect see my keys?

No. The protocol sees encrypted messages between wallet and dApp; keys never leave the wallet device.

What if the WalletConnect relay is compromised?

The relay handles ciphertext; a compromised relay can cause denial of service but cannot read or modify content.

In Veyrnox

Veyrnox supports WalletConnect v2 for dApp connections. Every incoming request runs through transaction simulation and (on AI Security Protection) TIP checks before the confirmation prompt is shown.

Learn more →