Whirlpool is a named wallet feature and CoinJoin context; the Samourai case adds a separate DOJ procedural record. The page must distinguish technical documentation, agency allegations, charges, and any later court outcome.
What remains visible
Whirlpool belongs to Bitcoin privacy context, not USDT token-transfer context. That difference should be explicit.
What it does not prove
A legal-source page does not prove that every wallet, CoinJoin tool, or USDT mixer claim is equivalent.
Evaluation checklist
- Define Whirlpool as context.
- Link CoinJoin comparison.
- Cite official source.
- Avoid current-status speculation.
Technical-versus-legal context ledger
Never use a criminal-case source as the sole technical specification or a wallet document as proof of legal status.
Document the feature
Use first-party technical material to describe Whirlpool or CoinJoin terminology.
Document the action
Record DOJ date, named parties, charges or allegations, and exact procedural language.
Reconcile boundaries
State which technical facts are independent of the legal claims and which later record would update status.
Filled evidence record
Technical-versus-legal context ledger snapshot: 2026-08-05. The worked record for samourai whirlpool labels every synthetic or non-attributed specimen directly in the table.
| Evidence item | Worked record | Interpretation boundary |
|---|---|---|
| Technical layer | Wallet or protocol documentation describes transaction construction and intended feature scope. | Documentation does not prove every deployment, use, or outcome. |
| DOJ layer | DOJ published charges concerning Samourai Wallet founders on 2024-04-24. | Charges and allegations are not final findings; later court records control later status. |
| Category limit | The named record can inform review of custody, coordination, claims, and evidence language. | It cannot define every CoinJoin wallet or USDT mixer claim. |
Pass or hold criteria
For samourai whirlpool, a missing decisive input remains unknown and blocks the affected conclusion; the technical-versus-legal context ledger never converts it to a silent pass or zero.
| Dimension | Pass condition | Hold or fail condition |
|---|---|---|
| Source role | Technical and legal sources used for their own jobs | One source answers both |
| Procedure | Charge, allegation, and outcome distinct | Accusation stated as conviction |
| Transfer | Case-specific limit explicit | Every CoinJoin context generalized |
Next evidence layer
CoinJoin vs Mixer
CoinJoin vs Mixer adds category comparison context to samourai whirlpool. Define CoinJoin separately. A CoinJoin comparison does not validate any USDT mixer claim. It only clarifies vocabulary and mechanism differences.
Privacy Wallets vs Mixers
Privacy Wallets vs Mixers adds category comparison context to samourai whirlpool. Separate wallet controls from service claims. Using privacy-wallet terminology does not prove a USDT mixer claim. It only helps classify the type of privacy idea being discussed.
Bitcoin Mixer vs USDT Mixer
Bitcoin Mixer vs USDT Mixer adds category comparison context to samourai whirlpool. Explain UTXO vs token-account context. A comparison does not make one category safer or more private. It only explains why the evidence, vocabulary, and risk signals differ.
USDT Mixer Risk Signals
USDT Mixer Risk Signals adds core guide context to samourai whirlpool. Check the scope and supporting evidence. Keep the conclusion within the available evidence.
Source notes
The sources below clarify samourai whirlpool terminology and the evidence limits described above. They do not verify private service operations or guarantee an outcome.
Related questions
What if the first-party technical site is unavailable?
Use an archived or repository source with a capture date and mark deployment behavior unverified.
What if later court documents conflict with a press release summary?
Prefer the later primary court record for procedural status and retain the press release as the earlier announcement.