How to use WalletConnect to link Trust Wallet to a dApp?

WalletConnect Connection Flow

1. Navigate to the target dApp interface on your desktop or mobile browser. Most decentralized applications display a prominent Connect Wallet button, typically located in the top-right corner of the page.

2. Click the button and select WalletConnect from the list of available wallet options. A dynamic QR code will appear on screen, uniquely generated for this session.

3. Open Trust Wallet on your smartphone. Tap the Browser tab at the bottom navigation bar, then press the QR scanner icon positioned in the upper-right corner.

4. Align your device’s camera with the QR code displayed by the dApp. Ensure sufficient lighting and stable framing for successful detection.

5. Upon successful scan, Trust Wallet presents a connection prompt showing the dApp’s name, requested permissions, and associated blockchain network. Review all fields carefully before proceeding.

6. Tap Connect to approve the session. The dApp interface updates immediately to reflect the authenticated state, displaying your wallet address and enabling further interaction.

Trust Wallet Internal DApp Browser Behavior

1. When accessing a dApp directly through Trust Wallet’s built-in browser, the standard WalletConnect flow may not trigger as expected due to URI handling limitations within the embedded WebView.

2. The browser may misinterpret WalletConnect deep links such as wc:00e46b69-d0cc-4b3e-b6a2-cee442f97188@2, redirecting instead to a generic search result rather than launching the WalletConnect handler.

3. This behavior is specific to the internal rendering engine and does not affect external browsers like Chrome or Firefox on the same device.

4. Developers integrating with Trust Wallet’s internal browser must implement fallback logic—such as detecting user agent strings and offering alternative connection methods—to maintain usability.

5. No modification to the dApp’s core WalletConnect client initialization is required; the issue resides entirely in how the embedded browser processes intent-based URIs.

Security Validation During Session Initiation

1. Every WalletConnect session begins with end-to-end encrypted communication established between the dApp and Trust Wallet using elliptic curve cryptography.

2. The QR code contains only a temporary pairing topic and relay server endpoint—not private keys, seed phrases, or account identifiers.

3. All transaction signing occurs locally inside Trust Wallet. The dApp receives only the signed payload, never raw cryptographic material.

4. Users retain full control over permission scope: Trust Wallet explicitly lists whether the dApp requests address exposure, transaction approval, or message signing capabilities.

5. Revoking access is instantaneous via Trust Wallet’s Settings > WalletConnect > Manage Sessions menu, severing all active channels without requiring dApp-side coordination.

Transaction Signing Workflow

1. After connection, initiate any on-chain action within the dApp—such as swapping tokens on PancakeSwap or minting an NFT on Blur.

2. The dApp constructs a transaction object compliant with Ethereum or compatible chain standards and forwards it through the WalletConnect session.

3. Trust Wallet displays a detailed modal showing recipient address, value, gas fee estimate, and contract interaction parameters.

4. Users must manually confirm each signature request. No automatic approvals are permitted—even for repeated interactions with the same dApp.

5. Once confirmed, Trust Wallet signs the transaction offline and returns the RLP-encoded result to the dApp, which broadcasts it to the relevant blockchain network.

Frequently Asked Questions

Q: Can I connect multiple wallets to the same dApp simultaneously using WalletConnect?Yes. WalletConnect supports concurrent sessions across different wallet instances. Each connection generates a unique session ID and operates independently.

Q: Does Trust Wallet store my session history after I close the app?Session metadata persists locally unless manually cleared. Reopening Trust Wallet restores active connections if the dApp remains online and the session has not timed out.

Q: Why does the QR code sometimes fail to scan even under good lighting?Common causes include aggressive ad-blockers interfering with QR generation, browser zoom levels distorting pixel alignment, or outdated WalletConnect SDK versions emitting malformed payloads.

Q: Is there a way to verify the authenticity of a dApp before scanning its QR code?Always cross-check the dApp’s domain against verified bookmarks or official social media announcements. Never scan QR codes from unsolicited messages or third-party forums.