Two ways to connect Tezos to EVM dApps.
TezosX Relayer
An injectable EIP-1193 provider that bridges Ethereum dApps to Tezos X. Delegates signing to Temple Wallet via the Beacon protocol.
- Injects window.ethereum on every page
- Converts EVM calls to the Michelson runtime operations
- Works with wagmi, RainbowKit, ethers.js
TezosX Wallet
A standalone Chrome extension wallet. Holds your Tezos keypair locally and signs transactions itself — no Temple required.
- BIP-39 seed phrase, AES-256-GCM encrypted
- Self-custodied — no external wallet needed
- dApp approval popups with full EIP-1193
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 L1 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
TempleBeacon · tz1
RelayerEIP-1193
NACGateway
EVM runtimeEVM dAppsTempleBeacon · tz1RelayerEIP-1193NACGatewayEVM runtimeEVM dAppsUp and running in 3 steps
# Build
cd packages/relayer && node build.mjs
# Or: <script src="/dist/relayer.iife.js"></script>const accounts = await window.ethereum.request({
method: 'eth_requestAccounts'
});
// → ['0x341af4…7cb2']await window.ethereum.request({
method: 'eth_sendTransaction',
params: [{ to: '0x…', value: '0xde0b6b3a7640000' }]
});