Educational guidance. No deposits, transfers, or privacy guarantees.
Decision framework
Compare crypto mixer claims by evidence, not adjectives
Use seven evidence checks to examine custody, retention, total cost, timing, network fit, failure handling, and claim quality before relying on an operator statement.
Method
Each criterion pairs a decision question with stronger evidence and a weak signal. Churn Money has not evaluated individual providers.
Comparison frameworkSeven checks that survive a polished landing page
Cost answer
How much does crypto mixing cost?
There is no universal mixer fee. Compare the amount sent with the amount expected at the destination after service fees, network fees, spread or slippage, minimum effects, payout costs, and any refund or failure deductions.
Service fee: the route's stated charge, including any tier or minimum rule.
Network cost: the ledger fee and any extra output or address cost.
Difference at payout: spread, slippage, delay, refund, and failed-route deductions.
There is no universal duration. Define when the clock starts and ends, then account for confirmations, queues, selected delay, liquidity, payout policy, split outputs, timeouts, and partial failure.
Start: an address generated, a transaction broadcast, or a confirmation accepted.
Middle: queue, selected delay, liquidity, screening, and network congestion.
End: a payout broadcast is not the same as a destination confirmation.
It is a claim about data collection and retention, not proof that no data exists. Verify the fields collected, their purposes, session and support records, processors, retention windows, deletion behavior, and legal exceptions for the current service. Churn Money has not verified an operator's logging practices.
Check the asset, token contract, network, address format, memo or tag, confirmation rule, minimum, limit, and wrong-network response as one combination. A ticker or logo is not a compatibility table.
Match the contract identifier to the current source.
Confirm the destination format and any memo or tag.
Read the failure and recovery boundary before relying on a route.
Churn Money has not verified support for a particular asset, contract, or network.
Neutral alternatives
Compare control flow, not rankings
A custodial route, CoinJoin-style coordination, smart-contract or protocol route, DEX or bridge, and pausing a transfer each create a different evidence burden. None is a universal recommendation.
Custodial: inspect who can move funds and how recovery is decided.
Coordinated: inspect participant, coordinator, and transaction construction assumptions.
Protocol / bridge: inspect code, keys, contracts, counterparties, and added records.
Pause: preserve control while an unresolved claim remains unresolved.
No provider, route, ranking, review, or fee result has been tested by Churn Money.
Decision questions, evidence to seek, and signals that do not prove a claim.
Criterion
Decision question
Evidence to seek
Not proof
01Custody
Who can move or hold the funds at every step, and what happens if processing stops?
Evidence to seek
A specific control-flow description, contract or wallet path, defined failure states, and a refund policy that names costs and conditions.
Not proof
A generic “non-custodial” badge with no explanation of keys, contracts, coordinators, or emergency controls.
02Retention
Which data is collected, why is it needed, how long is it retained, and which exceptions apply?
Evidence to seek
A dated policy that names fields, purposes, retention windows, deletion behavior, processors, and legal exceptions.
Not proof
“No logs” in a hero banner, especially when the interface still uses analytics, support tickets, or session identifiers.
03Total cost
What is the worst plausible difference between the amount sent and the amount received?
Evidence to seek
Service and network fees, spreads, minimums, timing assumptions, refund deductions, and a reproducible example.
Not proof
One attractive percentage without network cost, slippage, minimum, or failure-case disclosure.
04Timing
How long could the route take, and when does the stated clock start?
Evidence to seek
A current range with its start point, confirmation assumptions, selected delay, liquidity or payout rules, status states, and timeout behavior.
Not proof
Fast or instant without network, queue, delay, payout, and failure assumptions.
05Network fit
Is the exact asset, contract, network, and destination format supported for this route?
Evidence to seek
Current documentation with contract identifiers, address rules, confirmation policy, minimums, and a visible wrong-network warning.
Not proof
A token logo or ticker used as proof that every network version is interchangeable.
06Failure path
How can a user identify a stalled route, preserve evidence, and request recovery without exposing more data?
Evidence to seek
Defined status states, bounded support channels, signed receipts or identifiers, escalation timing, and explicit refund conditions.
Not proof
A support icon, anonymous chat handle, or promise that every transfer is automatic.
07Claim quality
Can the central privacy, speed, and security claims be tested or checked against an independent source?
Evidence to seek
A narrow claim, method, date, source, limitations, and evidence that applies to the current implementation.
Not proof
Absolute language such as “untraceable,” “100% anonymous,” or “guaranteed safe.”
01
Decision question
Custody
Who can move or hold the funds at every step, and what happens if processing stops?
Evidence to seek
A specific control-flow description, contract or wallet path, defined failure states, and a refund policy that names costs and conditions.
Not proof
A generic “non-custodial” badge with no explanation of keys, contracts, coordinators, or emergency controls.
02
Decision question
Retention
Which data is collected, why is it needed, how long is it retained, and which exceptions apply?
Evidence to seek
A dated policy that names fields, purposes, retention windows, deletion behavior, processors, and legal exceptions.
Not proof
“No logs” in a hero banner, especially when the interface still uses analytics, support tickets, or session identifiers.
03
Decision question
Total cost
What is the worst plausible difference between the amount sent and the amount received?
Evidence to seek
Service and network fees, spreads, minimums, timing assumptions, refund deductions, and a reproducible example.
Not proof
One attractive percentage without network cost, slippage, minimum, or failure-case disclosure.
04
Decision question
Timing
How long could the route take, and when does the stated clock start?
Evidence to seek
A current range with its start point, confirmation assumptions, selected delay, liquidity or payout rules, status states, and timeout behavior.
Not proof
Fast or instant without network, queue, delay, payout, and failure assumptions.
05
Decision question
Network fit
Is the exact asset, contract, network, and destination format supported for this route?
Evidence to seek
Current documentation with contract identifiers, address rules, confirmation policy, minimums, and a visible wrong-network warning.
Not proof
A token logo or ticker used as proof that every network version is interchangeable.
06
Decision question
Failure path
How can a user identify a stalled route, preserve evidence, and request recovery without exposing more data?
Evidence to seek
Defined status states, bounded support channels, signed receipts or identifiers, escalation timing, and explicit refund conditions.
Not proof
A support icon, anonymous chat handle, or promise that every transfer is automatic.
07
Decision question
Claim quality
Can the central privacy, speed, and security claims be tested or checked against an independent source?
Evidence to seek
A narrow claim, method, date, source, limitations, and evidence that applies to the current implementation.
Not proof
Absolute language such as “untraceable,” “100% anonymous,” or “guaranteed safe.”
A split payout can add output times, network costs, address-allocation questions, and partial-failure states; it does not prove a privacy outcome. Mechanism and privacy boundaries use the reviewed guide sources. These seven criteria are decision prompts; current operator behavior remains untested and unverified, and no comparison score is offered. Read the methodology.
Check the terms before you commit.
Continue to our partner and confirm the fees, network, and recovery terms before sending funds.
