Skip to main content

WalletConnect

The extension speaks WalletConnect in addition to its injected provider — as the wallet side of a session. This covers dapps the injected provider can't reach: desktop apps, dapps on another device, or environments without extension support.

How a session forms​

  1. The dapp displays a WalletConnect pairing URI (QR code or link).
  2. The user pastes or scans it in Core Extension.
  3. Requests from the dapp — eth_sendTransaction, personal_sign, the usual surface — arrive over the relay and open the same approval screens as injected requests.

The permission and approval model is identical to injected connections; only the transport differs.

When to point users here vs. Core Mobile​

Both Core Extension and Core Mobile accept WalletConnect sessions. From the dapp side the integration is identical — one WalletConnect (Reown AppKit) setup serves both; users pick whichever Core they carry.