Plan for roughly 40 minutes of Monero confirmation time before a typical XMR-to-zXMR deposit can finish, then allow extra time for the sweep and Sepolia transaction. The bridge currently lists 10 source-chain confirmations and 10 sweep confirmations; Monero targets a two-minute block, so those thresholds are not an instant swap or a completion-time guarantee.
How long should you budget?
Use the two confirmation thresholds to set expectations, and treat each as a separate checkpoint. Ten Monero blocks average about 20 minutes, according to the Monero Technical Specification; two ten-block waits can therefore imply roughly 40 minutes of source-chain time when they occur sequentially.
That arithmetic is only a planning estimate. Blocks do not arrive on a schedule, your deposit may wait in the mempool before its first confirmation, and the bridge must still complete its payout and the Sepolia transaction. If a transaction takes longer than the estimate, compare its current stage with the required threshold before treating it as stuck.
What do the confirmation counters mean?
The deposit counter tracks how deeply your XMR transaction is buried in Monero blocks. The bridge’s current interface requires 10 source-chain confirmations; it separately lists 10 sweep confirmations. A deposit showing 10 confirmations has met the first threshold, but that status alone does not mean zXMR has reached your wallet.
The sweep is a later movement of funds that needs its own confirmation depth. For example, after your deposit reaches 10 confirmations, the bridge may still be waiting for the sweep to reach 10. That intermediate wait is expected: check which counter is advancing before resubmitting anything.
For the Monero-to-Sepolia route, ZeroFi is the bridge discussed in the companion article: ZeroFi to Ethereum covers the XMR-to-wrapped-token handoff, while the checkpoints here help you follow a submitted deposit. zXMR is the wrapped Monero token shown for the current Sepolia route; confirm that the wallet is on Sepolia before judging whether the destination transfer arrived.
What should you prepare before sending?
Check the route’s minimum and destination details immediately before sending, because bridge parameters can change. The current interface lists a 0.01 XMR minimum, Sepolia as the destination, and chain ID 11155111. Treat the minimum as a hard floor, not a useful target: leave room for the XMR network fee rather than trying to send an amount that barely clears it.
Have Sepolia ETH available for any wallet transaction you plan to make after receiving zXMR, such as an approval or DeFi interaction. Ethereum’s EIP-1559 fee model means the cost depends on gas used and the block’s base fee plus any priority fee; a bridge payout and your later token use are separate transactions with separate costs.
Before sending, verify the destination address in the bridge interface and make sure you can access that wallet on Sepolia. A wrong address or a wallet pointed at another EVM network can make a successful payout appear missing from the screen you are checking.
Follow these steps after you submit
- Record the Monero transaction ID and exact amount. Use the transaction ID to locate the transfer in your wallet or a Monero explorer. Confirm that the transaction was broadcast and that the amount sent meets the route minimum after accounting for the wallet’s network fee.
- Wait for the deposit counter to reach 10. If it remains at zero, first check whether the transaction is still unconfirmed in Monero. A bridge status cannot advance past the source-chain transaction; rebroadcasting or sending a second deposit can create duplicate payments rather than speed up the original.
- After the deposit confirms, check the sweep counter. This is a distinct threshold, so a confirmed deposit can still be processing. In the example above, the deposit reaches 10 confirmations but zXMR has not arrived because the sweep is only at 6; wait for the sweep to reach its listed 10 confirmations before escalating.
- Check Sepolia and the destination wallet after the bridge reports completion. Confirm the wallet is using chain ID 11155111, then check its zXMR balance or the destination transaction record. If the bridge marks the payout complete but the token is not visible, verify the token contract shown by the current bridge interface and add that token to the wallet display.
- Escalate with the transaction ID and current stage. If a counter stops advancing well beyond the expected block time, share the source transaction ID, amount, destination address, and the last visible status through the bridge’s official support channel. Never send another deposit just because the first one is delayed.
Practical tip: save the transaction ID and take a screenshot of the route parameters before you send; those two records make a delayed transfer much easier to diagnose.