Two ways to connect Tezos to EVM dApps.
TezosX Relayer
An injectable EIP-1193 provider that lets EVM dApps run unmodified on Tezos X. Delegates signing to Temple Wallet via the Beacon protocol.
- Injects window.ethereum on every page
- Translates EIP-1193 calls into Michelson-runtime operations
- Works with wagmi, RainbowKit, ethers.js
TezosX Wallet
A self-custodied wallet — Chrome extension and mobile app. Holds your keys locally and signs transactions itself — no Temple required.
- BIP-39 seed phrase, AES-256-GCM encrypted
- Michelson (tz1) and EVM-native (0x) accounts
- dApp approval popups with an EIP-1193 provider
- Mobile app pairs with dApps over WalletConnect
Everything a dApp expects. Powered by Tezos.
EIP-1193 Provider
Full window.ethereum implementation, dApps see a standard Ethereum provider.
EIP-6963 Discovery
Multi-wallet discovery protocol. Works with RainbowKit, wagmi, and modern dApp stacks.
NAC Gateway
Transactions routed atomically through the TezosX gateway, tz1 becomes your EVM identity.
Local Signing
The wallet signs Michelson-runtime operations locally via Taquito InMemorySigner — zero Temple dependency.
Chrome Extension
Two MV3 extensions for Chrome, Brave, and Firefox — Relayer and Wallet, both auto-injecting.
Testnet Ready
Built and tested on Tezos X testnet. Counter, faucet, and DEX interactions validated.
From tz1 to EVM in one flow
EVM dAppwagmi · ethers
EIP-1193 providerExtension · WalletConnect · Injected
NACGateway
EVM runtimeTezos XEVM dAppwagmi · ethersEIP-1193 providerExtension · WalletConnect · InjectedNACGatewayEVM runtimeTezos XUp and running in 3 steps
npm install && npm run build:ext
# Load packages/relayer/extension/ as unpacked
# extension in chrome://extensionsconst accounts = await window.ethereum.request({
method: 'eth_requestAccounts'
});
// → ['0x341af4…7cb2']await window.ethereum.request({
method: 'eth_sendTransaction',
params: [{ to: '0x…', value: '0xde0b6b3a7640000' }]
});