One view.
Every relayer.
Compare Ethereum and BNB Smart Chain relayers, on-chain stake, fees, queue load and endpoint health in a single read-only dashboard.
Relayer directory
How to become a Tornado Cash relayer
Relayers broadcast withdrawal transactions for users and deduct network costs plus a disclosed service fee from the withdrawal amount. Registration is decentralized and requires reliable infrastructure, ENS configuration and TORN stake.
Official Tornado Cash documentation summary ↗Review risks and responsibilities
Assess server security, worker-key custody, operating costs, uptime expectations and the laws that apply to your jurisdiction before running a public service.
Deploy the relayer software
Run the open-source Ethereum relayer, expose a stable HTTPS endpoint and monitor its status response. Using your own RPC nodes is strongly recommended.
Configure ENS records
Create an ENS domain, configure the required mainnet relayer subdomain and publish the endpoint URL in the expected TXT record format. Add optional chain-specific records for BSC and other networks.
Register worker addresses
Workers submit withdrawal proofs and transactions. Register Ethereum mainnet workers, protect their private keys and keep enough native gas token available.
Stake at least 2,000 TORN
The current documented listing threshold is 2,000 TORN. Keep additional stake available because registry charges are deducted as the relayer processes withdrawals.
Verify and register
Validate the URL, ENS TXT records, worker configuration, service fee and stake, then submit registration through the decentralized Relayer Registry interface.
Relayer setup, ENS records, workers and staking
The official Tornado Cash guide describes relayers as independent operators that submit withdrawal transactions on behalf of users. A relayer pays the network gas cost, deducts that cost from the withdrawal amount and may charge a separately disclosed service fee. This allows a withdrawal to be broadcast without requiring the recipient address to already hold the chain’s native gas token.
To appear in the decentralized relayer registry, an operator first deploys the open-source relayer service behind a stable HTTPS endpoint. The guide strongly recommends reliable RPC infrastructure. The operator then creates an ENS domain, configures the mandatory Ethereum mainnet relayer subdomain and publishes the relayer URL in the required TXT record. Support for BNB Smart Chain and other sidechains is optional and uses chain-specific ENS records and compatible relayer software.
Ethereum mainnet workers are the addresses that submit withdrawal proofs and transactions. Their keys must be protected and funded with enough ETH for gas. The official guide’s eligibility note states that at least 2,000 TORN must be locked to be included in the Tornado Cash UI, while governance can change the threshold at any time. Because the archived guide also contains an older stake figure in a later section, operators should verify the current on-chain registry requirement before registration.
How relayers are selected
The interface retrieves registered relayers and weights selection using stake and service fee. More stake improves the score while a higher fee reduces it, then a relayer is selected probabilistically.
Operate for reliability
Use redundant workers, monitor endpoint health, keep RPC access stable and maintain enough TORN and native gas token so your relayer remains eligible and responsive.
Relayer FAQ
What is the minimum TORN stake?
The current documentation describes a 2,000 TORN listing threshold. Governance may change it, so check the live registry value before registration.
Is BNB Smart Chain support mandatory?
No. Ethereum mainnet is the core registration path. BSC and other sidechains are optional and require the corresponding relayer software and chain-specific ENS records.
Why run a private RPC node?
A self-operated RPC reduces dependency on public providers, improves reliability and gives the operator greater control over capacity, monitoring and privacy.