Skip to main content
This page covers what to try when Intention Exchange (app.intention.xyz), the flagship perpetual futures DEX on the Intention L1, will not connect to your wallet.
Intention Exchange has not yet launched to mainnet. The flow described below is the planned behavior. Testnet builds may surface slightly different error text; the underlying causes are the same.

​
Supported wallets

The first release will support browser wallets that expose a standard EVM-compatible signing interface, hardware wallets routed through those extensions, and a set of mobile wallets connected over a QR pairing relay. The canonical list of wallets that have been tested end-to-end will be published on this page at launch. Until then, assume that anything implementing the common browser injection interface will work and that anything claiming WalletConnect v2 support will work for mobile pairing.

​
Common reasons the connect flow fails

Work through these in order; the cheaper checks are first.
  1. The wallet extension is disabled or blocked. Browser privacy extensions, enterprise policies, and private-browsing modes sometimes block script injection from extensions. Open the wallet extension directly and confirm it reports the site as “connected” or at least “visible.” If the wallet does not even see the tab, the page has not been allowed to call into it.
  2. Multiple browser wallets are fighting over the injection slot. When two or more extensions expose the same global object, only one wins, and the app will talk to whichever one won. Temporarily disable the wallets you are not using and reload the page.
  3. The wallet is on the wrong network. If the wallet is pointed at a chain Intention does not recognize, the connect step can succeed while the first transaction fails. Switch the wallet to the Intention network (or the testnet, if you are on the testnet build) before you click connect.
  4. The wallet does not expose the signing scheme we need. Session signatures use a typed-data scheme that some older wallet builds do not support. Update to the latest version and retry.
  5. The page was opened over an unusual origin. If you loaded the app from a proxy, a mirror, or a local development build, the wallet may refuse to connect. Use the canonical URL.

​
What to try, in order

  • Reload the page with the wallet extension unlocked.
  • Disconnect any stale sessions from the wallet side and try again.
  • Restart the browser if the wallet still refuses to appear.
  • Try a different supported browser (Chrome, Firefox, Brave) as a control.
  • If none of the above work, capture a screenshot of the browser console and send it to support@intention.xyz along with your wallet name, wallet version, and browser version.