Architecture Overview

The relayer sits between Tezos X EVM dApps and the Michelson runtime, acting as a translation layer that maps EVM calls to Tezos operations.

Flow diagram

Components

Component	Role
RelayerProvider	Implements EIP1193Provider, handles all window.ethereum calls
BeaconClient	Connects to Temple wallet via Beacon SDK
TezlinkClient	Talks to the Tezlink EVM JSON-RPC node (reads, proxying, block scans)
buildTezosToEvmCall	Use-case function that builds the Micheline calldata for the NAC gateway (call for bare transfers, call_evm for ABI calls)
EIP-6963 announcer	Broadcasts provider info for modern dApp wallet pickers

Address derivation

Every tz1 address has a deterministic EVM alias. The relayer asks the Tezlink EVM node for it via the tez_getTezosEthereumAddress RPC (tz1 → 0x alias) and uses the result as the account returned by eth_requestAccounts. The reverse mapping (0x alias → tz1) is exposed by the node as tez_getEthereumTezosAddress.

Wallet variant

The TezosX Wallet (extension and mobile) uses the same RelayerProvider and the same buildTezosToEvmCall builder, but instead of BeaconClient it passes its own TezosSigner — a self-contained Taquito-backed signer from @tezosx/wallet-core that implements the same ITezosWalletClient port. This eliminates the Temple dependency entirely. The wallet also injects a per-account PendingOpsStore into the provider so cross-runtime resolution state survives lock and service-worker eviction.

See the Wallet Architecture for the full runtime boundary diagram specific to the wallet extension.