Anonymous Bitcoin Mixer

Untraceable BTC mixing. No logs. No accounts. No KYC.

pool · ≈ 41.148 BTC

How Bitcoin mixing works

  1. Paste your Bitcoin receiving address — we generate a unique BTC deposit address.
  2. Send any amount of Bitcoin (≥ 0.001 BTC) to the deposit address.
  3. After 3 confirmations we tumble your coins and send mixed BTC back to you.
Mixer fee — set yours 0.7%
0.5% 2.5%

Receiving Bitcoin address

Bitcoin Mixer — technical FAQ

Because the Bitcoin ledger is permanent and public. Anyone with one of your addresses — an exchange, an employer, an ex-partner, a counterparty, a chain-analytics vendor — can read your full balance and trace every payment you have ever made or received. A Bitcoin mixer breaks that link by returning BTC from a disjoint UTXO set: the receiving wallet has no on-chain ancestry with the deposit wallet, so analytics tools cannot walk the graph back. People mix coins received in payroll, OTC trades, donations, freelance invoices, and exchange withdrawals — anywhere financial privacy is the goal, not just paranoia.

No. Mixing your own legitimately-acquired BTC to recover financial privacy is lawful in the US, UK, EU, Canada and most other jurisdictions — the same way paying with cash to keep a transaction off your bank statement is lawful. Money laundering is the unlawful predicate (theft, fraud, ransomware, sanctions evasion), and it is illegal whether or not a mixer is used. We screen deposits against active criminal-investigation flags and refuse the order if a coin is implicated. If your BTC came from a clean source, mixing it is a privacy choice, not a crime.

Round-trip is 10–30 minutes from the moment your deposit clears 3 network confirmations. Wall-clock time depends mostly on mempool fee pressure and how quickly miners pick up your deposit in a block. The order page shows live state — confirmation count, mix-completion ETA, and the eventual payout TXID — and both transactions are independently auditable on mempool.space or any other Bitcoin block explorer.

You pick the percentage. Anywhere from 0.5% to 2.5% of the deposit, set with the slider before the deposit address is issued. The choice is locked into the order — we cannot raise it later — and it includes the on-chain network fee, so the percentage you set is the all-in cost of the mix. Minimum order: 0.001 BTC. No upper cap; large orders are split across multiple pools. Why a range instead of a flat rate? A flat fee is a chain-analysis fingerprint; a user-chosen percentage is much harder to match against the payout.

Not from on-chain data alone. The payout is constructed from a disjoint UTXO set, so common-input-ownership and change-output heuristics terminate at the mixer boundary — chain-analysis tools cannot walk back from the receiving address to the original wallet. The protection is broken only by off-chain leaks you create yourself: redepositing mixed BTC into a KYC exchange (which then ties the new wallet to your KYC identity), reusing the receiving address for clearnet payments (donations, social-media tip jars, ad networks), or co-spending pre-mix and post-mix outputs in a single transaction. The mixer secures the chain. The user must keep their wallet hygiene.

No accounts, no email, no password, no IP storage, no analytics scripts on the order page. The deposit→payout association is the single piece of state we have to hold during an active order in order to deliver your funds; it is destroyed when the Letter of Guarantee is generated. The Order ID stays — it resolves to nothing. The data is not encrypted-at-rest, not pseudonymized, not archived: it is removed from the database. A subpoena delivered after the Letter is generated returns an empty file. The simplest way for any service to be unable to leak data is to never collect it.

Every standard Bitcoin script type is accepted on input and output. P2PKH (Legacy, 1…), P2SH (3…), Bech32 SegWit (bc1q…), Taproot (bc1p…). The mixer routes the payout to whatever script type matches the receiving address you paste — you do not need to convert anything before depositing. Hardware wallets, mobile wallets, multisig coordinators and node-backed wallets all work; the mixer only sees a UTXO, never the wallet behind it.

Walk through three checks in order. (1) The deposit address on your order page must match the address in your wallet history exactly — Bitcoin transactions are irreversible, a single typo means the BTC is gone. (2) The deposit must be at least 0.001 BTC; below the floor and the mixer will not process it. (3) Your transaction must show up at the deposit address on mempool.space. If all three hold, the deposit is en-route and only needs 1–3 confirmations; otherwise contact support with your Order ID and the broadcast TXID.

About this Bitcoin Mixer

Threat model — what a Bitcoin mixer actually solves

Bitcoin gives you pseudonymity, not privacy. Every output that has ever been spent is publicly indexed; every input ever signed leaks ownership through standard graph heuristics. Two adversaries are worth planning against. (1) Commercial chain-analysis vendors that sell wallet-cluster data to exchanges, regulators and litigation firms. (2) Anyone with read access to the blockchain who already knows one of your addresses — an employer, a counterparty, a stalker, a tax inspector. A Bitcoin mixer targets exactly this attack surface: it produces an output UTXO whose history cannot be walked back to your input UTXO using on-chain data alone.

Three privacy techniques, side by side

  • Custodial mixer — what this service is. The deposit address belongs to a wallet with no transactional connection to you; the payout is signed from a disjoint UTXO set in a separate liquidity pool. Anonymity set: the entire pool. Cost: custody during the mix, mitigated by the signed Letter of Guarantee.
  • CoinJoin (Wasabi, Samourai, JoinMarket) — a non-custodial collaborative Bitcoin transaction signed by several participants with equal-value outputs. Anonymity set: the round size, typically small. Cost: CoinJoin-tagged outputs are widely flagged on KYC venue deposits, and the workflow requires a specific wallet client.
  • Generating a new wallet, no mix — the most common self-deanonymization. The first transaction that spends a new-wallet UTXO together with any other input collapses both wallets back into a single cluster. A fresh address resets nothing on its own.

Choose by threat: a mixer is the fastest path to immediate unlinkability if a custodial step is acceptable; CoinJoin is preferable when you must keep custody and can tolerate venue tagging; a new wallet is mandatory in either case but solves nothing on its own.

Order lifecycle (technical)

  • generate — you submit a receiving Bitcoin address; a one-time deposit address is derived from a wallet that has no on-chain history with you.
  • deposit — broadcast any amount ≥ 0.001 BTC. We see one inbound UTXO; nothing about your identity is collected on either side.
  • confirm — three Bitcoin network confirmations (~30 minutes on average) before the mix begins.
  • payout — the service constructs a Bitcoin transaction sourced from a disjoint input set. Output amount and broadcast time are randomized within the configured fee window.
  • erase — when the Letter of Guarantee is generated, the deposit→payout association is removed from storage. The Order ID survives; it resolves to nothing.

Operational hygiene for the user

  • Receiving address. Generate it in a wallet that has never received funds from a KYC source. The wallet, not just the address, is the unit of privacy.
  • Defeat amount fingerprints. Round numbers (0.1, 0.5, 1.0 BTC) and amounts that exactly match a recent exchange withdrawal are trivially correlated by analytics filters. Add an arbitrary fractional component.
  • Do not redeposit mixed coins to a KYC venue. Most exchanges flag mixer-origin UTXOs and may freeze the deposit pending review.
  • Split large balances. Several smaller orders spaced over hours or days enlarge the effective anonymity set more than one bulk mix.
  • Wallet partitioning. Pre-mix and post-mix wallets must live in separate keychains, ideally on separate devices. Never co-spend a pre-mix output and a post-mix output in the same transaction — that single signature collapses the entire mix.
  • Archive the Letter. The signed document is your only post-purge proof an order existed and was issued by us.