What Is a Pending ZeroFi Bridge and How Does It Resolve?

Your transfer is pending because a required chain event has not finished. Check the XMR transaction first, then the bridge record, before deciding whether to wait or seek help. For the full walkthrough, see how ZeroFi turns XMR into zXMR; this guide focuses on diagnosing a transfer that seems stuck.

• Ten source-chain confirmations are required, so a visible XMR transaction may still be waiting.
• A bridge record can show activity the Monero wallet cannot, including a later sweep.
• Do not send a second deposit until you know what happened to the first.

What does “pending” mean at each stage?

“Pending” can describe different steps, and the step determines what to check. First, look up your XMR transaction in your wallet and in the ZeroFi Bridge Explorer using its transaction hash. The explorer can also search by bridge address.

If the transaction is absent from Monero or has no confirmations, the bridge may not yet have a confirmed deposit to process. The current bridge page specifies ten source-chain confirmations; Monero blocks arrive roughly every two minutes, so ten blocks can take around twenty minutes, with timing varying. If your wallet says “pending,” confirm that it has broadcast the transaction and is synced before assuming the bridge is at fault.

Once the XMR deposit reaches the required depth, the bridge still has work to do. The displayed sweep-confirmation requirement is also ten: a sweep is the bridge’s movement of deposited XMR into its processing flow. Only after the relevant bridge steps complete should you expect the wrapped asset to appear on the destination chain.

How can you tell whether to wait or act?

Follow the transaction by its source hash, and compare its state with the two confirmation thresholds. If the source transaction has fewer than ten confirmations, wait and check again. If it has ten or more, but the explorer still shows no bridge progress, save the hash, amount, deposit address, and approximate send time; those details let support investigate the specific transfer.

For example, suppose you sent 0.05 XMR and your wallet shows four confirmations. Before, the wallet may show the outgoing amount while no zXMR is visible. That does not by itself mean the transfer failed: four is short of the displayed ten-confirmation threshold. After the threshold, check the explorer again for bridge activity, then check the destination wallet and network once the bridge processing finishes.

A completed mint can be easy to miss if your wallet is on the wrong network or does not display zXMR automatically. The live bridge interface currently identifies Sepolia, an Ethereum test network, as its destination and shows chain ID 11155111. Make sure your wallet is viewing that network and the zXMR ERC-20 token; a balance on Sepolia is testnet activity, not spendable mainnet XMR.

What should you do if the transfer failed?

A failed label needs investigation before you retry. Check whether the original XMR transaction was actually confirmed and whether the explorer records a corresponding bridge event. If the source transaction confirmed, keep its hash and do not repeat the deposit: a second send creates a separate transfer and will not repair the first one.

If the XMR transaction never confirmed or your wallet marks it failed, check the wallet’s transaction state and balance before trying again. If the source payment confirmed but the bridge record does not progress, contact the project through its official support channel with the transaction details. Never share a seed phrase or private key, and verify any recovery instructions independently.

Before acting, ask yourself: have I verified the original transaction’s confirmation count and bridge status, or am I about to send again because the destination balance is still missing?