Skip to content
Crypto Infrastructure

Atomic Swaps BTC to XMR: The State of Cross-Chain Conversion in Early 2026

Customer payments arrive in Bitcoin; we prefer accounting in Monero for privacy-aligned operations. Atomic swaps replace the centralized exchange dependency. The current state of BTC↔XMR atomic swap tooling, what works, what does not, and our production experience.

Most customer cryptocurrency payments to ASH arrive in Bitcoin. Our internal accounting and reserves favor Monero for the privacy alignment with our brand positioning. For two years we handled the conversion through centralized exchanges with KYC requirements that contradicted our positioning. The friction was operational drag we accepted as cost of doing business in cryptocurrency.

Atomic swaps emerged from cryptographic research starting around 2017 and reached usable production tooling around 2022-2023. The technology allows direct BTC ↔ XMR conversion without trusted third parties. The tooling has matured enough that we have been using it for production conversion since mid-2024.

This post is the current state of BTC↔XMR atomic swaps in early 2026, what works, what does not, and our operational experience using them at meaningful volume.

What atomic swaps actually are

The cryptographic primitive: two parties on different blockchains exchange tokens in a way where either both transfers complete or neither does. The “atomic” property guarantees the exchange completes fully or rolls back fully.

The mechanism for BTC↔XMR specifically:

Party A holds Bitcoin and wants Monero. Party B holds Monero and wants Bitcoin.

Party A locks Bitcoin in a contract with specific cryptographic conditions. Party B observes the Bitcoin lock and locks Monero with corresponding conditions. The conditions are constructed such that:

If party B reveals a secret to claim the Bitcoin, the same secret is exposed in the transaction. Party A can use the revealed secret to claim the Monero.

If neither party completes the exchange within a time window, both can recover their original locked tokens.

The cryptographic construction ensures no party can defraud the other. The exchange completes atomically or recovers atomically.

The specific construction for BTC↔XMR involves elliptic curve operations because Bitcoin and Monero use different signature schemes. The construction was developed in academic research starting around 2017 (Joël Gugger’s COMIT work) and refined into production tools through 2020-2023.

Why this matters operationally

For privacy-aligned operators, atomic swaps remove specific operational dependencies.

No centralized exchange dependency

Centralized exchanges typically require KYC verification. For operators whose customers value privacy, processing through KYC-required exchanges contradicts the value proposition.

Atomic swaps complete the conversion without involving any exchange. The two parties directly exchange. No third party knows the transaction occurred.

No counterparty trust

Traditional OTC (over-the-counter) trading requires trusting the counterparty. Atomic swaps remove this trust requirement through cryptographic guarantees.

Reduced surveillance footprint

Centralized exchanges produce records that exist on their servers, subject to regulatory requirements, subpoenas, data breaches. Atomic swaps leave only blockchain records that reveal less context.

Operational simplicity at scale

Once tooling is set up, atomic swaps are operationally simple. Set the desired conversion, the tooling executes, the conversion completes. Compared to exchange operations (account verification, deposit, trade execution, withdrawal), the atomic swap workflow is much shorter.

The current tooling

Several specific tools enable production BTC↔XMR atomic swaps as of early 2026.

COMIT-network: foundational implementation

The COMIT network produced the original production implementation. The protocol specification is well-documented. Multiple implementations build on COMIT’s work.

The reference implementation is in Rust. Setup requires running both Bitcoin and Monero nodes and the COMIT protocol implementation. The setup is bounded but non-trivial.

Farcaster: refined implementation

Farcaster is a refined implementation building on COMIT’s protocol with improved usability and reliability. The project continues active development.

Farcaster includes both swap participation (Alice/Bob roles) and a market-making component for liquidity providers.

Swap providers

Several services operate as swap counterparties. Customers can initiate swaps against these providers’ liquidity rather than finding individual counterparties.

The providers we have used:

  • UnstoppableSwap (most reliable in our experience)
  • SerAi (newer but stable)
  • Several smaller providers with varying reliability

Each provider has slightly different liquidity, pricing, and operational reliability. Production use typically involves multiple providers for redundancy.

CLI tooling

Command-line tools for swap execution are functional but require some technical sophistication. The tools handle the cryptographic primitives, wallet integration, and protocol coordination.

For our production use, we built thin wrappers around the CLI tools to integrate with our internal workflows.

GUI applications

Some GUI applications wrap the swap protocol for non-technical users. Adoption is limited but growing. For operational use cases like ours, CLI integration is preferable.

Our production setup

We have been running atomic swaps in production since mid-2024. The setup has evolved with experience.

Infrastructure

A dedicated server runs:

  • Bitcoin full node (currently Bitcoin Core 25.x)
  • Monero full node (currently Monero v0.18.x)
  • UnstoppableSwap CLI for swap operations
  • Custom Python wrapper integrating with our internal workflows

The server is dedicated to crypto operations to isolate the workload from other infrastructure. The resource requirements are modest: 16GB RAM, 8 CPU cores, 2TB SSD storage for the blockchain data.

Wallet management

Bitcoin wallet uses descriptor-based watch-only configuration with hardware signing for security. The wallet receives customer payments and serves as the source for swaps.

Monero wallet uses standard CLI wallet with hot wallet for swap destination and cold wallet for long-term storage. Monero received from swaps moves to cold wallet periodically.

Swap execution workflow

The operational workflow:

  1. Customer payment arrives in Bitcoin wallet. Webhook notifies our internal system.

  2. After Bitcoin confirmations (3+ for typical amounts, 6+ for larger amounts), the funds are available for swap.

  3. Swap request submitted to UnstoppableSwap (or alternate provider) with the desired BTC amount.

  4. The provider responds with offered exchange rate and swap parameters. We accept if the rate is acceptable.

  5. The atomic swap protocol executes. The Bitcoin is locked, the Monero is locked, the secrets are exchanged, both sides complete.

  6. The received Monero appears in our hot wallet. After confirmations, it moves to operational accounting.

  7. Periodic transfers from hot wallet to cold wallet preserve long-term holdings.

The workflow is automated for routine amounts. Larger amounts get manual review before execution.

Pricing analysis

Atomic swap rates typically include a spread compared to exchange spot prices. The spread is the swap provider’s compensation for capital lockup and risk.

Spreads we observe:

  • Small amounts (under 0.1 BTC): 1.0-2.5% spread
  • Medium amounts (0.1-1 BTC): 0.5-1.5% spread
  • Larger amounts (1-5 BTC): 0.3-0.8% spread
  • Very large amounts (5+ BTC): require pre-arrangement, custom pricing

For comparison, centralized exchanges typically charge 0.1-0.3% trading fees plus 1-2% in implicit spread on the bid-ask. The atomic swap cost is moderately higher than centralized exchange cost but eliminates the KYC, custodial risk, and surveillance footprint.

Throughput

Atomic swap throughput is bounded by blockchain confirmation times. Bitcoin confirmations average 10 minutes per block. Monero confirmations average 2 minutes per block. The full swap protocol typically takes 30-90 minutes from initiation to completion.

For our volume (typically 5-15 conversions per week), the throughput is adequate. Higher-frequency operations would face throughput constraints from the underlying blockchain confirmation requirements.

What works well

Several aspects of our production atomic swap setup work well.

Reliability

The swap completion rate in 2024-2025 production use has been 96-98%. The 2-4% non-completion has been almost entirely due to provider-side issues (provider availability, provider’s own liquidity issues) rather than protocol-level failures.

The non-completion cases recover safely: the timeout mechanism returns funds to their original owners. No funds have been lost during our production use.

Privacy posture

The privacy benefits operate as expected. The swaps leave only blockchain records that do not reveal counterparty identity or transaction context. The Monero side is naturally private; the Bitcoin side reveals only that an exchange occurred without revealing what was exchanged for.

Cost economics

The 0.5-1.5% spread is reasonable for the privacy and operational benefits provided. Compared to the alternative (CEX with KYC + withdrawal fees + surveillance footprint), the cost is favorable.

Operational simplicity

Once the infrastructure is set up, the operational workflow is straightforward. The CLI tooling is mature enough that routine operations require minimal attention.

What does not work as well

Several aspects produce friction or limitations.

Initial setup complexity

The full node requirements (Bitcoin node + Monero node + swap tooling + wallet management) require infrastructure that not everyone can or wants to maintain. The setup is bounded but exceeds what casual users would tolerate.

For operators serious about privacy-aligned operations, the setup is justified. For casual users wanting occasional swaps, the setup overhead is high relative to swap value.

Provider concentration

Despite multiple swap providers existing, UnstoppableSwap accounts for the majority of available liquidity. Provider concentration creates dependency risk. If UnstoppableSwap had operational issues, our swap operations would be significantly affected.

We have tested several other providers but their liquidity is more limited. Production use heavily relies on the dominant provider.

Liquidity for large amounts

Swaps for large amounts (10+ BTC) often cannot complete with single providers. The liquidity at this scale is limited. Either the swap must be split across multiple smaller swaps or pre-arrangement with specific providers is required.

This affects operators handling larger amounts. Our operations are typically below this threshold but the limitation is real for high-volume use cases.

Protocol updates

The atomic swap protocol continues evolving. New cryptographic refinements, security improvements, and feature additions produce protocol updates. The updates require periodic tooling updates on our side.

The maintenance burden is bounded but real. Operators considering atomic swaps should plan for ongoing tooling maintenance.

Limited counterparty discovery

Finding swap counterparties beyond the established providers is operationally difficult. Peer-to-peer counterparty discovery infrastructure exists but is limited. Most production swap activity flows through the established providers.

For operators seeking maximum decentralization, the limited counterparty discovery is a friction point. For operators willing to use established providers, the issue is less significant.

What we have learned

The production experience over the past 18+ months produced specific learnings.

Provider relationships matter

Even though atomic swaps are trustless in the cryptographic sense, the operational reliability depends on provider relationships. Providers we have built relationships with provide better experience than anonymous providers.

The relationship building involves consistent usage, communication during issues, and reasonable conduct during edge cases. Good relationships produce better operational outcomes.

Confirmation requirements scale with amount

For small amounts, faster confirmations are acceptable. For larger amounts, more confirmations protect against blockchain reorganizations.

We use:

  • Under 0.1 BTC: 1-2 confirmations
  • 0.1-1 BTC: 3 confirmations
  • 1-5 BTC: 6 confirmations
  • 5+ BTC: 10+ confirmations and manual review

The confirmation requirements add operational time but reduce risk.

Diversification across providers

Single provider dependency is a real risk. Maintaining capability with multiple providers produces operational resilience even if one provider has issues.

Our setup can swap through 3 different providers. Most volume goes through the dominant provider but we maintain capability with alternatives.

Documentation matters

The atomic swap workflow involves many steps. Documentation of our specific procedures has proven valuable for consistent execution and for training new team members.

The documentation includes operational procedures, troubleshooting steps, and escalation paths for unusual situations.

Monitoring is operational necessity

Active monitoring of swap operations catches issues early. The monitoring includes:

  • Swap initiation success rate
  • Completion times relative to expected
  • Pricing relative to spot prices
  • Provider availability
  • Wallet balance management

The monitoring infrastructure is bounded but important for sustainable operations.

What we considered but did not adopt

Several alternative approaches received consideration but did not match our operational needs.

Decentralized exchanges (DEX)

DEXes like THORChain offer cross-chain swaps without atomic swap protocols. The technology is interesting but the privacy model differs from atomic swaps. DEX swaps are more visible in their blockchain footprint.

For our privacy-aligned positioning, atomic swaps fit better than DEX swaps.

Lightning Network for Bitcoin handling

Lightning Network could reduce Bitcoin on-chain costs. We considered Lightning integration but the operational complexity exceeded the benefit for our current volume.

Higher-volume operations might benefit from Lightning integration. Our scale does not justify the complexity yet.

Self-custody multi-signature for swaps

Multi-signature wallets add operational security but slow individual swap execution. The trade-off favors single-signature operations for routine swaps with multi-signature reserved for large amounts.

We use single-signature for the bulk of operations with hardware-signing for added protection.

Custom liquidity provision

We considered offering swap liquidity as a service to customers. The operational complexity and capital requirements exceeded our current capacity for this expansion. The infrastructure focus remained on internal operations rather than external liquidity provision.

The regulatory considerations

Atomic swaps exist in a complex regulatory environment.

Jurisdiction variability

Different jurisdictions treat cryptocurrency exchange differently. Some jurisdictions consider atomic swap participation as exchange activity requiring registration; others do not. Our operations comply with Panamanian regulatory requirements applicable to our specific situation.

For operators in other jurisdictions, the regulatory analysis must reflect local requirements. The cryptographic technology is the same; the legal handling varies.

KYC requirements

Atomic swaps inherently do not collect KYC information from counterparties. For jurisdictions requiring KYC for cryptocurrency activities, this creates compliance considerations.

The compliance approach depends on whether the operator is acting as exchange (which typically requires KYC) or as customer using a swap service (which typically does not require self-imposed KYC).

Reporting requirements

Some jurisdictions require reporting of cryptocurrency activities above certain thresholds. The reporting requirements apply regardless of the conversion method used.

For our operations, reporting compliance is maintained through standard accounting practices applicable to cryptocurrency businesses.

Sanctions compliance

Cryptocurrency activities must comply with applicable sanctions regulations. Atomic swaps with sanctioned entities would violate sanctions even if the cryptographic protocol allows them.

The compliance approach: known providers operate within their own sanctions compliance frameworks. The transitive compliance covers most operational scenarios.

What we expect for 2026

Looking forward at atomic swap evolution:

Tooling maturation will continue. Current tooling is functional but rough at edges. 2026 should produce more polished implementations.

Provider expansion likely. Additional swap providers will enter the market as the technology matures. Competition should improve pricing and reliability.

Volume growth. Adoption increases as more operators discover the operational and privacy benefits.

Possible protocol refinements. The underlying cryptographic protocols may receive updates based on production experience and security research.

Integration with other privacy tools. Atomic swaps are one element of a broader privacy-aligned operations toolkit. Integration with other tools (CoinJoin for Bitcoin, monitoring privacy improvements) may produce complementary benefits.

Regulatory developments. Jurisdictions may produce specific guidance on atomic swap activities. The current regulatory ambiguity may resolve in various directions over time.

For our operations, the trajectory is continued use with periodic tooling updates. The current approach works; we expect to refine rather than replace.

What we recommend for similar operators

For privacy-aligned operators considering atomic swaps:

Plan for the infrastructure investment. Full node operation, wallet management, swap tooling all require infrastructure. The cost is bounded but not zero.

Start with smaller volumes during initial production rollout. Build operational experience with low-stakes swaps before handling significant amounts.

Maintain relationships with multiple providers. Single provider dependency produces risk that diversification addresses.

Document procedures comprehensively. The workflows involve many steps. Documentation prevents operational drift and supports team scaling.

Monitor continuously. The infrastructure to monitor swap operations is bounded but valuable for sustainable operations.

Plan for ongoing maintenance. Atomic swap tooling continues evolving. Plan for periodic updates rather than one-time setup.

Understand the regulatory environment for your specific jurisdiction. The technical capability does not exempt from regulatory compliance. Maintain practices that satisfy applicable requirements.

The honest assessment

Atomic swaps work in production for BTC↔XMR conversion. The privacy and operational benefits are real. The cost premium versus centralized exchanges is reasonable for operators who value the privacy alignment.

The technology has matured to the point where production use is feasible without specialized cryptographic expertise. The remaining friction is operational rather than fundamental.

For operators whose business model aligns with cryptocurrency privacy values, atomic swaps are operationally meaningful. For operators without strong privacy alignment, centralized exchanges with KYC may be the more pragmatic choice.

Our operations have benefited from atomic swap adoption. The privacy posture aligns with brand positioning. The operational workflow is sustainable. The financial cost is acceptable.

For other privacy-aligned operators reading this: the technology is ready for production use. The setup investment is bounded. The ongoing operations are sustainable. The strategic alignment with privacy-focused business positioning is real.

We expect to continue using atomic swaps for cryptocurrency conversion through 2026 and beyond. The tooling will continue maturing. The provider ecosystem will continue growing. The cumulative privacy and operational benefits will continue accumulating for operators who invested in the capability.

The decision to adopt is bounded analysis. The setup work is bounded engineering. The operational practice is bounded discipline. For privacy-aligned operators, the cumulative case favors adoption.

Operating email infrastructure at scale?

We run anonymous server hosting for email operators across seven jurisdictions. Crypto-paid, no-KYC, PowerMTA-tuned. Look at the catalog or talk to us.