During a routed swap, custody depends on who controls the intermediate asset’s keys. Sending from your own wallet and receiving into another self-controlled wallet does not settle who holds the funds between those transfers; the key question is whether a provider can redirect or withhold the value after your deposit.
For example, if you send XMR and expect Bitcoin, the service may receive your Monero, then pay BTC from its own inventory or arrange a separate conversion. The two transfers can be visible to you at their endpoints while the provider controls the Monero, Bitcoin, or both in between. For the broader workflow, see what an XMR bridge does; this article focuses on that custody interval.
What does “custody” mean during the swap?
Custody means practical control of the keys or transaction authorization needed to move the intermediate funds. It is not the same as whether the service calls the process non-custodial, whether it holds funds briefly, or whether you retain your own wallet keys.
In a typical provider-routed flow, you sign an outgoing transaction from your wallet to an address the provider controls. After the deposit meets its confirmation policy, the provider owes you the destination asset and sends it to your specified wallet. Until that payout is broadcast and confirmed, your claim is against the provider’s operational process and solvency; your own wallet cannot reverse the deposit.
Classify the design by where control sits at each stage:
- Direct wallet control: Your keys authorize every spend, and no intermediary can move the intermediate asset alone.
- Provider custody: A provider controls the deposit address or payout inventory and can authorize the relevant transfer.
- Protocol escrow: A contract or cryptographic swap protocol constrains settlement and refund paths, though software, timing, and chain assumptions still matter.
A Monero deposit has an important verification limit. Ring signatures, stealth addresses, and RingCT obscure the sender, recipient, and amount from public observers. Your Monero GUI Wallet can identify a payment to your wallet, but the public chain generally cannot show that a provider has ring-fenced your particular deposit or holds enough reserves for every outstanding payout.
When does the provider gain control, and when does it pay?
The provider gains unilateral control when it has the keys to spend the deposit; confirmation waiting changes settlement confidence, not ownership. Monero’s target block interval is about two minutes, but block arrival is probabilistic, so a quoted wait measured in blocks is not a guaranteed wall-clock duration.
For a Monero-to-Bitcoin example, suppose you send 2 XMR for a BTC payout. Your wallet can see whether its outgoing transaction is pending or confirmed, while the provider’s policy determines how many confirmations it waits before treating the deposit as usable. The provider may then send BTC from prefunded inventory; that payout can reach the destination Bitcoin address before it replenishes the inventory elsewhere. The intermediate exposure is therefore a credit exposure to the provider, even when no single on-chain transaction links your XMR directly to the BTC payout.
The handoff has two different failure windows. Before the provider accepts the deposit under its policy, a reorganization or a delayed transaction can leave the swap pending; after the provider has recognized it, a stalled payout, key compromise, or insolvency can leave you with a claim rather than spendable BTC. Bitcoin confirmations also reduce reorganization risk gradually, rather than making settlement mathematically final at a fixed count.
Timing has a Monero-specific wrinkle: received outputs normally remain locked for ten blocks before they can be spent, roughly twenty minutes at the target interval. A provider may use liquidity to pay sooner, but the incoming output’s unlock delay still affects its ability to reuse that exact XMR. The Monero technical specification and Monero’s payment guidance describe the block cadence and confirmation tracking; ask which confirmation event starts the payout clock.
How should you compare the custody exposure?
Compare the provider’s control and failure handling, not just the time its system estimates for a swap. Before choosing, find clear answers to these questions in the provider’s published terms and transaction design:
- Who controls the deposit key, and can one operator move funds without another signer or a protocol condition?
- Are customer deposits segregated or pooled, and what happens to pending swaps if the provider’s wallet or business fails?
- What exact event triggers payout: mempool observation, a set number of confirmations, or an internal risk decision?
- What is the recovery path if the payout transaction is delayed, a chain reorganizes, or the destination address is invalid?
These answers also explain part of the price. A provider may charge for liquidity, inventory risk, and operational handling in addition to network transaction costs; a longer confirmation threshold can reduce reorganization exposure while extending the time your value is unsettled. A low displayed spread does not compensate for unclear liability during that interval.
Would an atomic swap remove that risk?
A purpose-built atomic swap can reduce reliance on a provider’s promise by making each party’s claim depend on linked cryptographic conditions. In XMR–BTC designs, Bitcoin adaptor signatures and cross-group proofs connect events across Bitcoin’s secp256k1 and Monero’s Ed25519 cryptography; this differs from simply placing equivalent hash-timelock contracts on both chains.
That changes the trade-off rather than erasing risk. You take on protocol and client-software complexity, must keep the swap process online and synchronized with both chains, and may face timeout or recovery steps if a peer disappears or a transaction is reorganized. Monero’s Community Crowdfunding System documentation describes these components and operational failure cases, including connectivity, chain congestion, and manual recovery.
For a quick, wallet-to-wallet routed conversion, assess the provider as a temporary custodian and decide whether its disclosure, payout policy, and recovery terms justify that exposure. If minimizing intermediary control matters more than convenience or liquidity, compare a maintained atomic-swap implementation for the exact pair and direction you need. Before committing a meaningful amount, verify the custody answers and test the destination wallet with a small transfer.