- Connecting alone does not hand over your keys or move any money.
- The danger is in signatures: spending approvals and messages whose meaning is unclear.
- Check the site address and the bot name before you scan a QR code.
- After a transfer, close the session in your wallet's list of connections.
- Disconnecting a session does not cancel spending approvals you gave earlier.
What is WalletConnect and what can it do?
WalletConnect is an open protocol that links a wallet to a site or app through a QR code or a link. Once connected, the site sees your public address and can send signature requests to your wallet. It does not get your seed phrase or private keys and cannot send anything without your confirmation in the wallet.
There is a separate rule for QR codes: a connection code is tied to one session on one particular site. If you scan a QR code someone sent you in a chat, you connect your wallet not to your app but to the site of whoever sent it. Only scan a code you opened yourself on the screen of the service you meant to use.
So the question "is WalletConnect safe?" is really a different one: "is what I am about to sign safe, and is this the right site?" How a public address differs from a private key, and why you can share one but never the other, is explained in our article on public addresses and private keys.
What should you check before connecting?
Most thefts start before the first signature, with a fake site or app:
- the site address: letter by letter, with no extra characters or odd domains;
- for Nexus Pay: the @nexuspaymybot bot in Telegram and the nexuspayme.com site;
- where the link came from: not an ad, not a private message, not an "urgent email from support";
- the wallet itself: installed from the official app store, not from a link in a chat;
- the money in it: for trying new sites, a separate wallet with a small amount is handy.
How to tell a real site from a fake is covered in our article on spotting the real website, and fake wallets in our article on fake wallet apps.
What should you check in every signature request?
Read each request as if you were signing a bank payment: the action type (transfer or approval), the recipient, the amount, the network and the fee. Reject without hesitation:
- approve with an unlimited amount to an unknown address;
- setApprovalForAll, which grants access to every token in a collection;
- message signatures with fields like spender, value or deadline, which are a hidden spending approval (permit);
- requests that show up "on their own" while you were not doing anything on the site;
- a transfer to an address that does not match the one you expected.
How a transfer differs from a spending approval, and why that is the main safety line, is covered in our article on transfers versus approve.
| Stage | What to check | Red flag |
|---|---|---|
| Before connecting | Site address, bot name, where the link came from | A link from an ad or a private message |
| Connecting | The app name in the wallet window | The name does not match the site |
| Signing | Action type, recipient, amount, network | Unlimited approve, unreadable text |
| After the transfer | Transaction confirmed, session closed | New requests you did not expect |
| Once a month | List of connections and approvals | Forgotten sessions and old approvals |
How do you close a WalletConnect session afterwards?
A WalletConnect session can stay open for a long time, days or weeks. While it is open, the site can keep sending you new signature requests. It cannot execute them without you, but a stream of unexpected requests is fertile ground for a "tapped without looking" mistake.
Closing a session is simple: your wallet has a section for connected apps or WalletConnect sessions where you can disconnect the ones you do not need. Do it right after the transfer, and review the whole list once a month. Remember: disconnecting a session does not revoke approvals you gave earlier. Approvals are revoked separately, with a transaction in your wallet or through an approval checker in a block explorer.
How does wallet connection work in Nexus Pay?
For Ethereum, BNB Smart Chain and Arbitrum One, the standard WalletConnect window opens with a list of wallets. For Tron, you pick a wallet that supports Tron through WalletConnect or scan a QR code with any wallet that has a scanner.
The app builds only one kind of request: a token or network coin transfer to your own deposit address. It never builds approve, permit or setApprovalForAll, and Nexus Pay never receives your wallet's keys; you do the signing. Once credited, the coins sit in your Nexus Pay account. The service is custodial, and from then on they are protected by the rules on the security page. The feature itself is described on the top up from your wallet page.
What should you do if you signed something you should not have?
Act fast and in order. If you signed an approve or permit on a suspicious site, revoke it as soon as possible, in your wallet or through an approval checker in a block explorer. Close all WalletConnect sessions. If you suspect the wallet is compromised, move the remaining assets to a new wallet.
If you typed your seed phrase into any site, treat that wallet as lost: create a new one and move everything left to it immediately. To be honest, what is stolen through a signature is usually gone for good, because blockchain transfers are irreversible. Half a minute of checking before you sign is worth more than any rescue attempt afterwards.

