How to send tokens from Trust Wallet using WalletConnect v2?

Connecting Trust Wallet via WalletConnect v2

1. Open the decentralized application (DApp) you wish to interact with and locate the wallet connection button, typically labeled “Connect Wallet” or “Connect.”

2. Select Trust Wallet from the available wallet options. If Trust Wallet does not appear, choose “WalletConnect” manually.

3. A QR code will appear on the DApp interface. Launch Trust Wallet on your mobile device and tap the wallet icon in the top-right corner to open the WalletConnect scanner.

4. Scan the QR code displayed on the DApp screen. The connection request will appear inside Trust Wallet for confirmation.

5. Tap “Approve” to establish a secure, encrypted session between the DApp and your Trust Wallet using WalletConnect v2 protocol standards.

Initiating Token Transfers Through Connected DApps

1. Once connected, navigate within the DApp to the section where token transfers are supported—such as swap interfaces, bridge portals, or NFT marketplaces.

2. Enter the recipient address, select the token from your Trust Wallet balance list, and specify the amount. Ensure the token is ERC-20, BEP-20, or another supported standard compatible with the target chain.

3. Review all transaction parameters including gas fee estimates, network selection, and slippage tolerance if applicable.

4. Confirm the action inside the DApp. A signature request will be pushed to Trust Wallet.

5. Unlock Trust Wallet and approve the transaction signature. Your private key never leaves the device during this process.

Verifying Token Balances and Contract Addresses

1. Within Trust Wallet, go to the “Assets” tab and scroll down to find the token in question. If it does not appear, tap “Add Custom Token” and input the correct contract address, symbol, and decimals.

2. Cross-check the contract address against Etherscan, BscScan, or the relevant blockchain explorer to confirm authenticity and avoid counterfeit tokens.

3. Verify that the token’s network matches the one selected in the DApp interface—mismatched networks cause failed transactions or irreversible loss.

4. Confirm whether the token requires manual approval before transfer. Some DApps auto-approve; others require an explicit “Approve” transaction first.

5. Monitor pending transactions under the “Activity” tab in Trust Wallet to track status and confirm on-chain inclusion.

Security Considerations During WalletConnect Sessions

1. Never share your 12-word recovery phrase with any website, DApp, or individual—even if prompted by a seemingly official interface.

2. Reject connection requests from unrecognized or misspelled domains, especially those mimicking popular platforms like Uniswap or Blur.

3. Disable unused WalletConnect sessions manually inside Trust Wallet under “Settings > Connected Sites” to limit exposure surface.

4. Avoid granting unlimited allowances; use tools like Revoke.cash to inspect and reduce token approvals after completing transfers.

5. Ensure your Trust Wallet app is updated to the latest version supporting WalletConnect v2’s enhanced encryption and session expiration features.

Frequently Asked Questions

Q: Can I send tokens directly from Trust Wallet without connecting to a DApp?A: Yes. Use the built-in “Send” function inside Trust Wallet. Select the token, enter the recipient address, and confirm with your PIN or biometric authentication.

Q: Why does my token not show up after connecting via WalletConnect v2?A: WalletConnect only establishes communication—it does not auto-import tokens into your wallet interface. You must manually add them using their contract address.

Q: Is it safe to approve a token allowance on a new DApp?A: Only after verifying the DApp’s domain, smart contract audits, and community reputation. Unlimited allowances pose high risk even on legitimate platforms.

Q: Does WalletConnect v2 support multi-chain token transfers natively?A: No. WalletConnect v2 handles session management and signing across chains but does not execute cross-chain swaps. That functionality depends on the DApp’s integration with bridges or aggregators.