Tangem WalletConnect Safety Guide: dApp Verification, Transaction Simulation, Token Approvals and Revocation

Tangem WalletConnect lets a Tangem card or ring authorize actions in decentralized applications without exposing its private key. That protects the key but does not make every website, smart contract or requested permission safe. Before connecting, verify the dApp domain, wallet and network. Before signing, inspect the transaction simulation, token movements, spender and approval limit. After use, disconnect the WalletConnect session and separately revoke any onchain permissions that should not remain active.

Last reviewed: October 30, 2026. Tangem app features, WalletConnect behavior, supported networks, Blockaid checks and approval-management tools can change. Treat the current Tangem app, card confirmation, official Help Center and blockchain data as controlling information. Never enter a seed phrase or private key into a dApp. This independent guide is educational and is not affiliated with Tangem, WalletConnect or Blockaid.

What Tangem WalletConnect does

WalletConnect is a communication protocol between a wallet application and a decentralized application. It lets a dApp send connection, message-signing and transaction requests to Tangem Wallet. The Tangem app displays the request, and the user authorizes supported signing operations with a Tangem card or ring.

The private key remains inside the Tangem device. The dApp receives only the public account information allowed by the session and the signatures the user deliberately approves. This design prevents a dApp from directly reading the private key, but it cannot protect a user who signs a transaction granting dangerous rights.

What WalletConnect does not guarantee

An encrypted connection is not a security audit of the destination. WalletConnect does not guarantee that:

• the website is the official dApp rather than a convincing clone;
• the selected smart contract is free from bugs or malicious logic;
• an approval is limited to the current transaction;
• a swap, deposit, bridge or staking product is economically sound;
• the contract cannot be upgraded or compromised later;
• the user selected the intended wallet and blockchain network;
• a transaction will be reversible after confirmation.

Hardware-backed signing protects key custody. It does not decide whether the requested action is wise.

Understand the five components

Supported networks can change

Tangem currently documents WalletConnect support for Solana and many EVM-compatible networks, including Ethereum, BNB Smart Chain, Polygon, Arbitrum, Base, Optimism and Avalanche. The live list is broader and can change with app releases.

Support in Tangem does not prove that a particular dApp supports the same network or transaction type. An EVM address can look identical on several chains while balances, token contracts and contract state are completely separate. Confirm the network in the dApp and Tangem before every signature.

Mobile and desktop connection flows

Connecting on a mobile device

1. Open the official dApp in its supported browser or application.
2. Select Connect wallet.
3. Choose WalletConnect and Tangem.
4. Review the connection details in Tangem.
5. Approve only if the domain, wallet, networks and permissions match.

Connecting from a computer

1. Open the verified dApp website and choose WalletConnect.
2. Generate a fresh QR code.
3. Open the WalletConnect scanner in Tangem Wallet.
4. Scan the QR directly from the trusted screen.
5. Review the complete connection request before tapping Connect.

Do not send the QR code to “support” or scan a code received in a direct message. A QR code is an encoded connection request, not proof of who created it.

Verify the dApp domain before opening WalletConnect

Phishing sites copy colors, logos, pool data and wallet buttons. Inspect the full domain before connection:

• open it through a trusted bookmark or official project documentation;
• check spelling, top-level domain and unexpected subdomains;
• do not rely on a paid search advertisement;
• compare contract links with the project’s official documentation;
• look for a recent compromise notice through another trusted channel;
• avoid links promoted through unsolicited private messages.

HTTPS protects traffic to the domain. It does not prove that the domain belongs to the intended protocol.

How Tangem describes dApp verification status

Tangem can display a verification or risk status when a WalletConnect session is proposed.

A verified status is evidence about identity or reputation at a point in time. It does not guarantee that every smart contract is safe, every parameter is correct or the frontend has not just been compromised.

Know Your dApp and Blockaid checks

Tangem describes a Know Your dApp process supported by Blockaid. The wallet can check a dApp URL and relevant contract data against security information, identify known phishing or malicious infrastructure and produce warnings for higher-risk interactions.

Security analysis can include known-address reputation, code patterns, function inspection and transaction behavior. This reduces exposure to known scams but cannot make a new, unknown or carefully designed attack impossible. Treat “no warning” as the absence of a detected warning, not a certificate of safety.

What a dApp learns when you connect

A normal session can disclose the public address you selected, its network and publicly visible activity. From that address, a dApp or analytics provider can inspect blockchain balances and history. It does not need the private key to do so because blockchain data is public.

The session also lets the dApp send requests for review. Those requests still require the applicable Tangem authorization, but repeated or misleading prompts can pressure a user into approving the wrong action. Disconnect sessions that are no longer needed.

A connection is not a transaction

Several actions can appear consecutively and should be reviewed separately:

1. Connection: establishes a WalletConnect session.
2. Message signature: signs data that may authenticate, create an order or authorize another action.
3. Token approval: records permission for a spender contract.
4. Protocol transaction: swaps, deposits, bridges, stakes or transfers assets.
5. Revocation: changes an existing permission onchain.

Approving the connection does not mean later prompts are automatically safe. Reject any step whose purpose differs from what you initiated.

How a Tangem dApp transaction is signed

A typical workflow is:

dApp creates an unsigned request
→ WalletConnect delivers it to Tangem
→ Tangem decodes and may simulate it
→ user reviews the human-readable effects
→ card or ring authorizes the signature
→ signed request returns for broadcast
→ blockchain executes the confirmed transaction

The private key never has to leave the card or ring. However, the resulting signature is valid authority. If it authorizes a token transfer or allowance, the hardware wallet will not later reverse the consequences.

Transaction simulation explained

Transaction simulation attempts to execute the proposed action in a model of the current blockchain state without first broadcasting the real transaction. It can estimate balance changes, contract calls, transfers and failures.

A useful simulation can reveal:

• tokens expected to leave the wallet;
• tokens expected to arrive;
• an approval or operator permission;
• an NFT transfer;
• a call to an unexpected contract;
• a likely revert;
• known malicious recipient or spender behavior.

Simulation is based on a particular state and model. The chain can change before execution, and not every complex protocol effect is easy to summarize. If simulation fails or is unavailable, risk is less visible—not automatically absent.

Transaction verification and the displayed result

Tangem’s WalletConnect security material describes transaction verification that combines the original request, simulation result and validation information in a signed package. The purpose is to reduce the risk that a transaction changes between preview and signing.

This integrity protection does not judge whether a price is fair, a yield is sustainable or a protocol will remain solvent. It helps connect the displayed effects to the request being signed; the user must still decide whether those effects are acceptable.

How to read the transaction preview

Check every field available:

• Action: swap, send, approve, permit, deposit, stake, bridge or NFT operation.
• Wallet: the intended Tangem account, not another saved wallet.
• Network: the intended chain and native gas asset.
• Token contract: the real asset, not merely a familiar symbol.
• Amount out: the maximum value leaving the wallet.
• Amount in: the expected result, with slippage and protocol conditions understood.
• Recipient or spender: the address receiving funds or authority.
• Approval limit: exact, custom or unlimited.
• Gas: network cost, separate from asset value and protocol fees.
• Warnings: any suspicious domain, address or behavior notice.

Reject the request if the preview shows an unexplained outflow, a different network, an unknown spender or a much broader permission than the planned action.

What is a token approval?

Many EVM tokens use an allowance model. The token owner signs an approval that permits a specific spender contract to transfer up to a defined amount. A later protocol transaction can use that allowance.

Approval: USDC allows Router X to spend up to 100 USDC
Swap: Router X uses the available allowance to perform the trade

The approval is not the swap. Cancelling the swap or closing the website may leave the allowance active.

Exact, custom and unlimited approvals

For a one-time action, a bounded approval generally limits potential loss. Unlimited approval can be a deliberate convenience choice for a repeatedly used protocol, but it should never be accepted without recognizing its persistent scope.

Why an old unlimited approval can become dangerous

A legitimate contract today can be affected later by:

• a smart-contract exploit;
• an upgrade to malicious or flawed logic;
• a compromised administrator or governance process;
• a vulnerable router or integration;
• future tokens deposited into the approved account;
• a user forgetting which spender holds authority.

Periodically review allowances for valuable accounts rather than waiting for a protocol incident.

Permit signatures also require scrutiny

A permit can authorize token spending through a signed message, sometimes without a separate approval transaction and gas payment at the signing step. “This is only a signature” does not mean “this has no financial effect.”

Review the token, owner, spender, amount, nonce, deadline and network. Reject a permit with an unknown spender, unexpected unlimited value or long deadline that does not match the intended workflow.

NFT approvals can cover an entire collection

NFT standards include item-specific approvals and broader operator permissions. An action such as setApprovalForAll can let an operator transfer every supported NFT in a collection owned now or acquired later.

Before listing or using an NFT marketplace, determine whether the request concerns one token or all assets managed by that contract. Revoke unused marketplace and lending permissions after the intended workflow.

Message signatures can create enforceable rights

dApps use message signatures for login, orders, permits, NFT listings and offchain authorization. A message may cost no gas but still be submitted later by another party.

Check the requesting domain, wallet, chain context, purpose, asset, price, spender and expiry. Reject unreadable messages or requests presented as harmless “verification” when their contents cannot be reconciled with official documentation.

Verify token and contract identity

Token symbols and names are not unique. Compare the full contract address with an official project source and open it in the correct network explorer. Check whether the spender shown in the approval matches the documented router or protocol contract.

A familiar dApp can route through several contracts. Identify the actual spender rather than assuming every address used by the frontend is equally trusted. If the project does not document a surprising address, pause and investigate.

Gas cost is not the value at risk

An approval transaction can cost only a small gas fee while granting control over a large token balance. The wallet’s network-fee line therefore does not measure the financial exposure of the permission.

Ask three separate questions: how much gas will be paid, what assets will move now, and what assets can the spender move later?

Disconnecting a WalletConnect session

In Tangem Wallet, active sessions can be managed through the WalletConnect area. A user can select a session and disconnect it or disconnect all sessions. Ending the session prevents that connection from delivering new requests.

Disconnect after completing a one-time workflow, especially on a shared computer or when a dApp is no longer used. A stale session is not equivalent to handing over the private key, but removing unnecessary communication paths reduces confusion and unwanted prompts.

Disconnect does not revoke token approvals

A spender can use an existing allowance according to its contract logic even when the dApp no longer appears in the WalletConnect list. This is why session cleanup and approval cleanup are separate tasks.

How to revoke a smart-contract approval

1. Identify the network on which the approval exists.
2. Open the official approval checker for that network or another carefully verified tool.
3. Connect the correct Tangem address through WalletConnect.
4. Display all relevant ERC-20, ERC-721 or ERC-1155 permissions.
5. Compare each spender with the original transaction and protocol documentation.
6. Select Revoke for a permission that should no longer exist.
7. Review the revoke transaction, network and gas in Tangem.
8. Authorize it with the card or ring.
9. Wait for confirmation and recheck the allowance onchain.

A revocation costs gas because it changes blockchain state. Do not revoke randomly named contracts without identifying their purpose; an active protocol position may depend on a permission for normal management or exit.

Choose an approval checker carefully

Tangem’s Help Center identifies explorer-based token approval checkers for Ethereum, BNB Smart Chain, Polygon, Arbitrum and Optimism, and references Revoke.cash for several other supported networks. Availability and supported standards can change.

Open the tool from the official block explorer or a verified bookmark. A fake revocation site can present its own malicious approval. The fact that you are trying to improve security does not make the next signature automatically safe.

Post-dApp cleanup routine

1. Check whether the intended transaction confirmed or failed.
2. Review actual token and NFT balance changes in the correct explorer.
3. Cancel any open dApp orders through the protocol’s documented method if needed.
4. Disconnect the WalletConnect session.
5. Review approvals created during the session.
6. Revoke one-time or excessive allowances.
7. Save transaction hashes for accounting and incident review.
8. Monitor the address if any request or result was unexpected.

What to do after a suspicious connection

If you only connected

Disconnect the session, reject all pending requests and inspect the address history for any action you may have signed. Merely displaying a public address is different from granting onchain authority.

If you signed an approval or permit

Disconnect, identify the exact spender and revoke the permission on the correct network. Review approvals across relevant token and NFT standards, then confirm the revocation onchain.

If assets moved or remain at immediate risk

Prepare a new trusted wallet, preserve enough native gas and move unaffected assets through a carefully verified plan. A malicious allowance may compete with your transactions. Do not accept private-message “recovery” offers or reveal seed words.

Already confirmed blockchain transfers cannot normally be cancelled. Revocation protects remaining authority; it does not reverse a completed theft.

Factory reset is not an approval-revocation tool

Resetting a Tangem device removes its keys and wallet state. It does not send a blockchain transaction and therefore cannot remove token allowances, cancel orders or return transferred assets.

Never reset the last usable device unless a verified backup or new-wallet migration already protects access. If a wallet is believed compromised, move assets to a newly generated wallet; recreating the same key from the same seed recreates the same address and approvals.

Separate savings from dApp activity

Wallet segmentation reduces the effect of a mistake. A user can maintain a long-term storage wallet with no dApp approvals and a separate operational wallet funded only for planned interactions.

This does not make the operational wallet safe, but it limits the value exposed to an unknown contract. Avoid holding unrelated high-value tokens or NFTs at the address used for experimental protocols and airdrop claims.

High-risk warning signs

• The dApp asks for a seed phrase, private key or “wallet synchronization.”
• The domain differs by one character or arrived through an advertisement.
• Tangem labels the dApp or address suspicious.
• The requested network is unrelated to the intended action.
• An airdrop asks for unlimited approval or NFT approval-for-all.
• The simulation shows assets leaving without an expected return.
• The spender is not documented by the protocol.
• A message signature has no readable purpose or expiry.
• Support contacts you first and sends a new QR code.
• A small “verification fee” must be paid before withdrawal.
• Repeated signature prompts appear after the action was cancelled.

Pre-connection checklist

• The dApp URL came from an official, independently verified source.
• The complete domain and verification status were reviewed.
• The correct Tangem wallet and public address are selected.
• Requested networks are necessary for the intended action.
• The dApp’s official contract information is available.
• No seed phrase or private key is requested.
• The wallet contains only an acceptable amount at risk.
• The reason for opening a session is specific and current.

Pre-signature checklist

• The action matches what was initiated.
• Wallet, network and token contracts are correct.
• Recipient or spender is expected.
• Token and NFT outflows are fully explained.
• Approval amount and duration are acceptable.
• Expected output and slippage are understood.
• Gas is available on the correct network.
• Simulation shows no unexplained balance change.
• No malicious-address or high-risk warning appears.
• The Tangem device remains physically under the user’s control.

Troubleshooting WalletConnect

The QR code expired

Reload the verified dApp and create a fresh WalletConnect request. Do not use a screenshot sent by another person.

The required network has not been added

Add the network through the Tangem app’s normal workflow, then reconnect. Verify its native gas token and the dApp’s supported network.

Tangem shows the wrong network

Reject the request. Change the network in the dApp and reconnect rather than hoping the contract address is equivalent across chains.

The transaction does not appear in Tangem

Check the active session and network. Disconnect a stale session and create a new request from the official site.

The dApp is unverified

Verification may be incomplete rather than malicious, but do not proceed until domain and contract identity can be established independently.

Simulation is unavailable or failed

This removes a safety signal. Do not interpret it as a clean result. Cancel unless you can decode and verify the raw action through trusted tools.

An approval remains after disconnecting

This is expected because the permission exists onchain. Use an appropriate approval checker and submit a separate revocation.

Common Tangem WalletConnect mistakes

• Trusting a blue checkmark without reading the requested action.
• Assuming a protected private key makes every signature harmless.
• Selecting the wrong saved Tangem wallet.
• Ignoring the network because the EVM address looks identical.
• Accepting unlimited approval merely to save one future gas fee.
• Confusing Disconnect with Revoke.
• Signing an unreadable permit or listing message.
• Approving all NFTs when only one item was intended.
• Using a long-term savings wallet for experimental dApps.
• Resetting a card before migrating assets or preserving recovery.
• Interacting with a scam token in an attempt to remove it.
• Following recovery instructions from direct messages.

Frequently asked questions

Is WalletConnect safe with Tangem?

WalletConnect preserves hardware-backed signing, but safety still depends on the dApp, contract, permission and user’s review. Verify every domain and request.

Does WalletConnect see my private key?

No. The private key remains in the Tangem device. The dApp receives public account information and signatures you authorize.

Can a dApp spend tokens just by connecting?

A normal connection alone does not grant token-spending authority. A signed approval, permit or transaction can. Existing approvals may already allow a contract to spend.

What does a verified dApp mean?

It means the domain passed the relevant verification checks. It does not guarantee every contract action, price or future protocol state.

Can a verified dApp still be compromised?

Yes. Frontends, administrators, contracts and integrations can be attacked after verification. Read every transaction.

What does transaction simulation show?

It estimates contract execution and balance changes before broadcast, helping reveal transfers, approvals, errors and suspicious effects.

What is Blockaid in Tangem?

Blockaid provides security data and transaction analysis used for dApp reputation, simulation and malicious-interaction warnings in supported Tangem workflows.

What is a smart-contract approval?

It is an onchain allowance authorizing a spender contract to transfer a defined token amount on behalf of the owner.

Is unlimited approval dangerous?

It creates broader and persistent exposure if the spender is compromised or abused. Prefer a bounded amount when practical.

What is a permit signature?

It can authorize token spending through signed data, sometimes without an approval transaction at the signing moment. Review it as carefully as an onchain approval.

Does disconnecting revoke approvals?

No. Disconnecting closes the WalletConnect session. Onchain approvals must be revoked with a separate blockchain transaction.

Does revoking cost gas?

Yes. Revocation changes contract state and therefore requires the network’s native gas asset.

Can Tangem stop a malicious transaction?

Tangem can warn, decode and simulate supported requests, but the user can still authorize a harmful action. No detection system catches every attack.

What should I do after connecting to a scam dApp?

Disconnect, reject further requests, inspect signed activity and revoke any approvals. If funds remain at immediate risk, migrate them to a new wallet through a verified plan.

Does factory reset remove token permissions?

No. Permissions remain onchain. Reset affects the local device keys and can destroy access if recovery is not available.

Why does Tangem show a different network?

The dApp request may be configured for another chain. Reject it, change the dApp network and reconnect.

Should I use my main savings wallet with dApps?

Separating long-term storage from dApp activity limits the amount exposed to approvals and contract risk.

Can a legitimate dApp ask for my seed phrase?

No. A dApp does not need a seed phrase or private key to connect through WalletConnect. Such a request is a scam.

Final assessment

Tangem WalletConnect keeps the private key inside the card or ring and adds dApp verification, human-readable previews and transaction simulation. Those controls materially improve visibility, but they do not replace user review.

Safe use requires two separate cleanups: disconnect unnecessary sessions and revoke unnecessary onchain permissions. The strongest routine is to verify the domain before connecting, verify every asset movement and spender before signing, prefer limited approvals, isolate dApp funds from savings and act immediately when a request differs from the intended transaction.

Official Tangem resources

• Tangem Blog — official product updates, app changes and security explanations.
• Tangem — What’s New in WalletConnect — official connection workflow, transaction simulation, KYDA and Blockaid features.
• Tangem Help Center — Tangem & dApps — current networks, connection and signing steps, verification statuses, disconnect and revocation guidance.
• Tangem — Scam Detection with Blockaid — transaction decoding, simulation, approval warnings and malicious-address detection.
• Tangem — Give and Revoke Smart Contract Permissions — limited and unlimited approvals plus the documented revocation workflow.
• Tangem Security and Research — official security research, audit announcements and threat explanations.
• Tangem App and Firmware Changelog — current app versions and changes to WalletConnect or security features.