Verified in Xuanxi catalog
On 2026-07-19, route code USDTTRC20 appeared with send and receive enabled. The Source: Public enabled-route catalog lets another reader reproduce that narrow finding.
Claim comparison
Mixer claims you can verify before handoff
A ranked list would imply measurements that do not exist. This page takes the claims providers repeat and shows which part can be observed, sourced, or disproved.
Common promises and the evidence behind them
A claim can still be useful when the result is unknown, as long as the page says what was checked and where the evidence ends.
| Provider claim | What can be observed | Current finding | Where to look |
|---|---|---|---|
| No logs“We keep no records and store nothing that identifies you.” | Absence of records is very hard to prove from the outside; you can only confirm there is no account or identity wall. | Claimed by provider | Check whether the interface asks for anything beyond a destination address. An email/account requirement contradicts the claim. |
| No KYC“No identity verification is required.” | Directly observable on the interface right now. | Partially verified | Open the interface and confirm no document upload or verification step appears before you transact. |
| Anonymous / untraceable“Your funds become untraceable.” | False as stated. Mixing reduces linkage and raises tracing cost; it does not make transfers untraceable. | Failed | Treat any 'untraceable' or 'anonymous' guarantee as a red flag, not a feature. |
| Low, fixed fee“Flat X% fee, nothing hidden.” | Only verifiable at request time; published figures are not stable across routes. | Not published | Read the quoted fee before committing and confirm it does not change at settlement. |
| Instant / fast“Near-instant payout.” | Depends on network finality and pool depth; time delay is often a privacy feature, not a defect. | Not published | Understand that a deliberate delay can improve privacy. Confirm timing expectations on the interface. |
| Exchange-safe output“Funds are accepted anywhere, no questions.” | An operator cannot promise this because exchanges run their own inbound screening. | Failed | Assume deposit scrutiny. No route can guarantee a third-party exchange will accept mixed funds. |
| No AML hold“We never hold funds for compliance.” | Confirmable only by the absence of surprise holds in the live terms. | Claimed by provider | Stop if an AML hold or release fee appears only after deposit. The terms have changed after payment. |
A verified field and a live-quote field are not the same claim
USDTTRC20 makes the boundary concrete. One fact is reproducible from a dated source; the other exists only when a visitor requests a quote.
Read from the current quote
The same catalog response contains no service fee, minimum amount, pool depth, delay, or settlement time. Those values should not inherit a verified label from the listing.
Sources that anchor the comparison
The catalog supports route availability; issuer documents support token controls; analytics references explain why a privacy claim needs a narrower reading.
Use the finding, not a rank
A missing fixed fee is not evidence of fraud. It means the value changes and must be read from the live quote. A no-logs promise is different: the interface cannot prove what a server retains.
Observable behavior deserves more weight than an anonymous score. Check the hostname, the route terms, and the network before sending.