ZeroFi bridges native Monero (XMR) into zXMR, a wrapped ERC-20 token. Check the destination first: the displayed Sepolia route gives you testnet zXMR, not an Ethereum mainnet asset. To bridge XMR with ZeroFi, open ZeroFi , connect your EVM wallet, send XMR to the generated address, and await minting.
Key points
-
You send real XMR and receive zXMR on the destination network shown in the bridge.
-
Sepolia zXMR is useful for testing compatible apps; it cannot be spent in Ethereum mainnet DeFi.
-
Keep enough XMR for the deposit and enough destination-chain ETH for later transactions.
zXMR Represents XMR Held by the Bridge
ZeroFi gives you a token that represents an XMR claim, rather than moving Monero itself onto an EVM chain. Monero and Ethereum use different transaction systems, so a DeFi app cannot accept native XMR as an ERC-20 token. The bridge receives XMR on Monero and issues zXMR to your EVM address; redemption reverses that process.
The project describes a network of nodes that holds the deposited XMR in collective multisignature wallets and authorizes minting and payouts. That design matters because the zXMR balance in your wallet depends on both the token contract and the bridge’s ability to release the backing XMR. A displayed one-to-one backing ratio describes the intended relationship between tokens and reserves, not a guarantee that every withdrawal will be immediate or free.
Look at the network name as carefully as the token name. The bridge interface currently shows Sepolia, Ethereum’s test network, with chain ID 11155111. A zXMR balance there will not appear in an Ethereum mainnet app, even if both networks use the same wallet address. ZFI, the project’s separate token, is not the XMR representation you receive from a deposit.
The Deposit Has a Monero Leg and a Sepolia Leg
The ZeroFi XMR bridge first assigns you a Monero deposit address tied to your chosen EVM recipient. After you send XMR, its nodes observe the Monero transaction, wait for the required confirmations and arrange for zXMR to be minted on Sepolia. You can then see and transfer the ERC-20 token in a wallet set to that network.
For an illustrative run, suppose you want to send 0.05 XMR to a wallet you use for a Sepolia app. Set that wallet to Sepolia, connect it, enter 0.05 XMR on the Deposit tab and review the recipient address before generating the Monero address. Send the XMR from your Monero wallet to that exact address, then keep the Monero transaction hash so you can follow the transfer.
The interface currently shows a minimum deposit of about 0.01 XMR and a requirement of 10 source-chain confirmations. Monero targets a block about every two minutes, so those confirmations alone often take roughly 20 minutes; detection, the displayed 10 sweep confirmations and minting can add time. Treat the bridge’s current amount and status display as authoritative for your transaction, since a quoted minimum or processing rule can change.
Once minting completes, check your balance on Sepolia. If your wallet does not display zXMR automatically, add it as a custom token using the token contract address shown in the bridge interface, and confirm that your wallet is on chain ID 11155111. A missing wallet icon or token listing is different from a missing on-chain balance.
Fees and Destination Network Decide Whether It Fits
Your cost is the Monero network fee for sending XMR, any bridge charge shown before you commit, and destination-chain gas when you later move or redeem zXMR. The amount you receive may therefore be below the XMR amount you sent; check the quoted output instead of assuming a deposit of 0.05 XMR will yield exactly 0.05 spendable zXMR. Sepolia ETH pays for Sepolia transactions and has no mainnet ETH value.
The deciding question is where your next app runs. If that app accepts this zXMR contract on Sepolia, the route can serve a test of its deposit, transfer or redemption flow. If your task requires a live Ethereum mainnet position, a Sepolia balance will not meet it. Also check that the app accepts this specific wrapped token: sharing the symbol zXMR does not make two token contracts interchangeable.
Bridging changes the privacy properties of your activity. Monero hides transaction details on its own chain, while ERC-20 balances and transfers on Sepolia are publicly visible. Review the destination network, recipient address and token contract together before sending XMR; those three details catch the mistakes that matter most here.
Redemption Burns zXMR Before XMR Is Paid Out
ZeroFi’s Withdraw route converts your zXMR claim back into native XMR. Choose Withdraw, connect the Sepolia wallet holding zXMR, enter the amount and provide a Monero address you control. Review the displayed payout and any fee, approve the token if prompted, then sign the withdrawal transaction with enough Sepolia ETH for gas.
The bridge must recognize the Sepolia-side withdrawal before its nodes send XMR from their Monero holdings. Its interface says payouts also wait for 10 confirmations on the source chain, so do not expect the Monero wallet to update as soon as you sign. Save the Sepolia transaction hash and check the bridge status before retrying; a second withdrawal request is a separate action.
If this is your first transfer, use an amount just above the displayed minimum and complete the return trip before committing more XMR. That one small round trip checks the wallet, token contract and payout address you will actually use.