How to connect Exodus wallet to dApps? (Web3 Browser)

Understanding WalletConnect Integration

1. Exodus supports WalletConnect v2.0 protocol through its dedicated @exodus/walletconnect-sign-client library, enabling secure session handshaking between dApps and wallet instances.

2. The integration follows strict separation of roles: dApps act as Proposers initiating connection requests, while Exodus functions as Responder validating and approving sessions.

3. Compatibility spans browser environments, Node.js runtimes, and React Native mobile contexts—ensuring consistent behavior across desktop and mobile Web3 interfaces.

4. Session metadata—including peer name, icons, and supported chains—is exchanged during handshake to establish context-aware permissions before any signature request.

5. All cryptographic operations occur locally within the Exodus process; no private keys or recovery phrases ever leave the user’s device or browser extension sandbox.

Navigating the DApp Browser Interface

1. Within the Exodus desktop or mobile app, locate and tap the DApp Browser icon—typically found in the bottom navigation bar or main sidebar menu.

2. Enter a valid dApp URL directly into the address field or select from preloaded categories such as DeFi, NFT marketplaces, or DAO governance tools.

3. Upon loading, the dApp detects Exodus via injected ethereum provider and triggers a connection prompt inside the Exodus UI overlay.

4. Users see a clear summary of requested permissions: network access, account exposure, and transaction signing scope—no hidden approvals are permitted.

5. Tapping “Connect” initiates WalletConnect pairing; a QR code appears for mobile users scanning from desktop, or direct session link appears for browser extension users.

Approving Transactions and Sign Requests

1. Once connected, any dApp action requiring on-chain interaction—such as swapping tokens or minting NFTs—triggers a native Exodus confirmation screen.

2. Each request displays full transaction details: recipient address, value, gas parameters, and decoded function call if ABI is available.

3. Users may reject, adjust gas fees, or proceed with signature using their local password or biometric authentication—no remote relay occurs.

4. For EIP-1559 transactions, Exodus auto-calculates priority fee suggestions based on real-time network congestion data sourced from multiple RPC endpoints.

5. Signed payloads are returned directly to the dApp via WalletConnect session channel without intermediaries or third-party relayers.

Managing Active Connections

1. Access the Connected dApps section from Exodus settings to view all live WalletConnect sessions grouped by domain and last activity timestamp.

2. Each entry shows chain ID, connected accounts, and permission level—read-only access differs from full signing capability in visual indicators.

3. Revoking a session terminates the WalletConnect pairing immediately and invalidates all associated session keys on both client and dApp sides.

4. Sessions persist across app restarts unless manually revoked or expired due to inactivity timeout set by the dApp’s WalletConnect configuration.

5. Exodus enforces strict origin validation: only domains verified during initial pairing can initiate subsequent sign requests—preventing domain-spoofing attacks.

Troubleshooting Common Connection Failures

1. If the dApp fails to detect Exodus, verify that the browser extension is pinned, enabled, and not blocked by ad/tracker blockers interfering with window.ethereum injection.

2. On mobile, ensure location services are enabled—some dApps require geolocation for compliance checks before allowing connection initiation.

3. A blank or frozen QR code screen often indicates mismatched WalletConnect version support; confirm the dApp uses v2.0-compatible client libraries.

4. Repeated “session rejected” messages may stem from clock skew—Exodus validates JWT timestamps with ±30 second tolerance, requiring accurate device time sync.

5. When encountering “unsupported chain” errors, manually switch Exodus to the required network in Settings > Networks before reconnecting—the dApp cannot force chain switches post-pairing.

Frequently Asked Questions

Q: Does Exodus inject window.ethereum in all browsers?Yes, Exodus injects a standards-compliant Ethereum provider object into Chrome, Brave, Edge, and Firefox when installed as an extension. Safari requires manual provider selection via dApp UI due to browser policy restrictions.

Q: Can I connect the same Exodus wallet to multiple dApps simultaneously?Yes, Exodus maintains independent WalletConnect sessions per dApp domain. Each session operates with isolated permissions and cannot access data from other active connections.

Q: Why does my dApp show “Wrong Network” after connecting?This occurs when the dApp expects a specific chain ID (e.g., 1 for Ethereum Mainnet) but Exodus is currently set to a different network like Polygon or Arbitrum. Switch networks inside Exodus before reconnecting.

Q: Is it safe to approve a dApp connection request from an unknown domain?No. Exodus displays the full domain name during approval. Never grant access to typosquatted or obfuscated URLs—even if they visually resemble legitimate dApps.