WalletConnect (wallet connection)

When you press connect wallet on a dApp, two things can happen. With a browser extension, the site talks to the wallet directly in the same browser. With a mobile or separate wallet, the site usually shows a WalletConnect QR code or deep link; scanning it opens an encrypted session relayed through a network of servers, so the dApp can send requests and the wallet can answer them.

Connecting by itself only shares your public address and network. Every transfer, token approval or signed message still requires an explicit confirmation in the wallet. That is why connection is widely used for logins, such as Sign-In with Ethereum, and why the same wallet can serve dozens of dApps.

The danger lies in what you sign after connecting. Drainer sites ask for a connection and then present approvals or permit signatures disguised as claims or verifications. Sessions can stay active for long periods, so review and disconnect old ones in the wallet's settings. Disconnecting stops new requests but does not cancel approvals already granted; those must be revoked on chain.