Skip to main content
Version: 0.7.0

dApp Compatibility

Tested dApps

dAppStatusWallet mechanismNotes
Tezos X EVM Faucet✅ Workingwindow.ethereum + EIP-6963Fully functional (first tested on the legacy shadownet, before the Previewnet rename)
IguanaDEX✅ Workingwindow.ethereumRequires testnet mode enabled in IguanaDEX settings
Hanji❌ Not connectingPrivy (EIP-6963)Wallet detected via EIP-6963, but connection fails — investigation ongoing
Superlend✅ WorkingwagmiEIP-6963
Uniswap❌ No testnetNo Tezos X Previewnet support

Known limitations

Hanji The relayer is correctly detected by Privy via EIP-6963, but the wallet connection does not complete. Current hypothesis: Hanji has no Previewnet mode — contracts are only deployed on mainnet. We are investigating whether the issue is network-side or connection-side. This is the only Privy-based dApp tested so far, so it is unclear whether the failure is Privy-generic or Hanji-specific.

MetaMask conflict If MetaMask is installed, it locks window.ethereum with configurable: false. Workaround: disable MetaMask on the site via its extension menu.

CSP restrictions Pages with strict Content Security Policy may block Tampermonkey's inline script injection. Solution: use the Chrome Extension injection method — the recommended method since v0.2.0.

Message signing personal_sign, eth_sign and eth_signTypedData* are rejected with EIP-1193 error 4200 — see API Reference → Not supported. dApps whose login flow requires SIWE cannot complete it through the relayer.

Temple pairing The Beacon pairing currently works with Temple mobile only — see Connect Wallet for the details and current status.

Wallet detection by stack

dApp stackDetection methodRelayer visible
Raw window.ethereumDirect property
wagmi v1window.ethereum
wagmi v2 + RainbowKitEIP-6963
ConnectKitEIP-6963
PrivyEIP-6963✅ Detected as injected wallet (connection completion varies by dApp — see Hanji above)
WalletConnect onlyQR code protocol❌ Out of scope

See also