ZeroFi’s zXMR route currently ends on Sepolia
ZeroFi’s bridge currently routes zXMR to Ethereum Sepolia, so it is not a backed asset on Ethereum Mainnet; check for a mainnet deployment before sending funds.
The Blocktape Editors 2 min read 83860b

No: ZeroFi’s current bridge routes zXMR to Ethereum Sepolia, not Ethereum Mainnet. The bridge interface lists Sepolia as the destination and shows chain ID 11155111, while Ethereum Mainnet uses a different network. That distinction determines where the token can be received and used.
What network does ZeroFi support for zXMR?
ZeroFi’s bridge interface currently lists Sepolia as the Ethereum destination for zXMR. Sepolia is a test network: its ETH is for testing, and a token issued there is separate from any token with the same name or ticker on Mainnet.
The route is designed to convert native Monero (XMR) into an ERC-20 token on an EVM network, then reverse the process to redeem XMR. The bridge’s listed network matters because an Ethereum wallet can connect to multiple networks while showing different balances and contracts on each. The fuller zerofi guide covers the destination cases integrators need to distinguish.
Can I transfer zXMR to a Mainnet wallet?
You can switch a wallet to Ethereum Mainnet and attempt to add a token contract, but that does not move the Sepolia token or make it redeemable there. Ethereum keeps separate balances and contract state on each network; the same address can exist on both, yet the assets at that address are not shared.
A token shown by a wallet is only a display of a contract balance on the selected chain. It does not establish that the token is backed, supported by a bridge, or accepted by an application. A Mainnet token using the zXMR name could be unrelated to ZeroFi’s Sepolia token, so check the network and contract address against ZeroFi’s own current interface before interacting.
How can I check whether zXMR is available on Mainnet?
Look for an explicit Ethereum Mainnet route in ZeroFi’s bridge interface and verify the destination network before initiating a transfer. The interface should identify the chain and the relevant token contract; a wallet’s token label alone is not enough.
- Confirm the bridge destination says Ethereum Mainnet, not Sepolia.
- Check the chain ID shown by the bridge and wallet; Sepolia’s listed ID is 11155111.
- Verify the zXMR contract address from the bridge while connected to the stated network.
- Check that the bridge offers a redemption route back to native XMR for that same deployment.
Wrapping also involves two different chains and a bridge process: XMR is deposited on Monero, while zXMR is issued on the destination EVM chain after the required processing. Redemption reverses those steps. A testnet route can demonstrate that flow without establishing Mainnet support or providing a Mainnet-backed asset.
For now, treat ZeroFi zXMR as a Sepolia token and use it only on that network. Mainnet use becomes possible only if ZeroFi lists and supports a Mainnet deployment; check its bridge interface for that change before sending XMR or relying on zXMR in an application.