If you want to try using XMR in an EVM app, first confirm the bridge is still operating on the networks you intend to use; then send only an amount you can afford to risk. As of 30 September 2026, ZeroFi’s interface lists Monero as the source and Ethereum Sepolia as the destination, with a 0.01 XMR minimum. That means the wrapped zXMR you receive is on a test network, not Ethereum mainnet.
This route can suit someone testing a Sepolia app or learning how a bridge works. It is not a way to put XMR into a live DeFi position: Sepolia assets are test-network tokens. The ZeroFi interface also lists 10 source-chain confirmations and 10 sweep confirmations, so allow time for the bridge’s processing stages.
Check the source and destination labels before you connect a wallet or send funds. The current interface identifies the destination as Sepolia and the wrapped asset as zXMR; if your screen instead shows a different network or token, stop and check the live service details.
The displayed minimum is 0.01 XMR, but sending exactly that amount leaves no room for a fee or other deduction if one applies. For example, if you plan to test a wallet’s zXMR balance display, you might enter 0.02 XMR and review the quoted output before sending; treat that as an example, not a guaranteed amount received. The interface’s current quote and fee information should decide the amount, since fees can change.
You need a Monero wallet with spendable XMR and an EVM wallet connected to Ethereum Sepolia. Check that the EVM wallet is set to chain ID 11155111, the Sepolia network, and that you control its recovery phrase; keep a little Sepolia ETH available for later transactions that use the received token.
On the bridge, select Deposit, connect the EVM wallet, and enter the XMR amount. Read the generated Monero deposit address carefully, then copy it into your Monero wallet. The destination EVM wallet is where the wrapped asset is minted, while the Monero address is where you send the underlying XMR.
Send the amount shown by the bridge to the generated address from your Monero wallet. Check the first and last characters of the address after pasting, confirm the amount and network in your wallet, and keep the transaction ID so you can look up the transfer.
The deposit does not mint zXMR the instant it appears in a wallet. Monero first needs to include the transaction in a block; the current interface requires 10 source-chain confirmations, then lists another 10 sweep confirmations. Bridge operators can only process the deposit after it meets the relevant confirmation requirements, so a pending balance may simply mean the transaction has not reached the required depth or sweep stage yet.
If the bridge does not recognize the deposit, do not send a second payment to the same address as a troubleshooting attempt. Search the transaction ID in the bridge’s explorer if available, and compare its status with the Monero wallet’s confirmation count. If it remains unresolved, use the service’s current support channel and provide the transaction ID, amount, and destination wallet address.
After processing, check the Sepolia wallet for zXMR and verify the token address against the bridge’s published details before adding it manually. ZeroFi currently lists a zXMR contract and bridge contract on its interface; matching those addresses helps avoid interacting with an unrelated token or contract.
Before depositing, consider how you would redeem the wrapped asset. A return transfer generally involves selecting Withdraw, specifying a Monero address you control, and burning the wrapped tokens so the bridge can release XMR; check the live withdrawal instructions, minimum, fee, and confirmation requirements at that time. Keep enough zXMR for any required withdrawal amount and enough Sepolia ETH for EVM transactions.
For occasional use, the practical sequence is simple: verify the live route, test with a modest amount above the minimum, and wait for both confirmation stages before treating the zXMR as available.