# Privacy & Anonymity
Publisher: Bitcoin Library (KK siiiiiixth) — https://bitcoin.ne.jp

## Privacy & Anonymity

URL: https://bitcoin.ne.jp/en/learn/privacy
URL role: Self-canonical for this English representation
Japanese counterpart URL: https://bitcoin.ne.jp/learn/privacy
Slug: privacy
Language: en
First published: 2025-12-01
Last updated: 2026-11-03
Last verified: 2026-10-09
Description: Pseudonymity, chain analysis, and CoinJoin — the reality of Bitcoin privacy and how to protect it.

Bitcoin is pseudonymous, not anonymous. This article explains how chain-analysis techniques such as the common-input-ownership heuristic can trace transactions, and what privacy-enhancing technologies such as CoinJoin, Taproot, and Silent Payments offer in response. It also covers the growing regulatory pressure on privacy tools since 2024, including the prison sentences handed to Samourai Wallet's two operators in November 2025 and the conviction of Tornado Cash developer Roman Storm.

Reuse terms: https://bitcoin.ne.jp/licenses#content-reuse
Third-party sources retain their own rights. Cite the canonical HTML URL or its section fragment.
Sources below are article-level references; they do not establish support for every sentence. Check the original source and its date before quoting time-sensitive claims.
This is educational material, not investment or legal advice. Dates describe the editorial text; this representation excludes browser tools and live market/network values.

This page is for informational purposes only and does not constitute investment advice, a recommendation to buy or sell crypto-assets or financial products, or legal advice. It has not been reviewed by a qualified expert. For the latest regulatory, tax, and market information, please consult primary sources.

### A 30-second entry

Bitcoin’s ledger has no name field. Yet in a place where every footprint is visible, a numbered mask does not guarantee anonymity.

Mental model: Imagine walking through a glass hallway in a numbered mask: the number is not your name, but the paths you take can still narrow down who you are.
Where the analogy stops: Much of chain analysis is heuristic, so an inference is not always certainty. Privacy techniques do not guarantee anonymity either, and they carry operational, counterparty, and legal risk.
Reading journey: [Pseudonymity and leaks](https://bitcoin.ne.jp/en/learn/privacy#pseudonymity) → [Clues used in chain analysis](https://bitcoin.ne.jp/en/learn/privacy#chain-analysis) → [Defenses and trade-offs](https://bitcoin.ne.jp/en/learn/privacy#privacy-techniques)
What you will understand: For each payment you will ask not what you hoped to hide, but what an observer can still see.

### Pseudonymous, not anonymous

Section URL: https://bitcoin.ne.jp/en/learn/privacy#pseudonymity

Bitcoin is often mistaken for anonymous, but it is pseudonymous: it uses addresses rather than real names. On-chain transactions are recorded in a public ledger. Once an address is linked to a person, transactions involving that address can be analyzed in connection with that identity.

Bitcoin addresses are like usernames on the internet. No name is written on them, but all activity under the same address is linked together.

Exchange identity checks or publication of a payment address can link an address to a real name. Earlier records and later transactions then provide leads for analysis, but links to other addresses and the identity of their owners are not always certain.

### Chain analysis techniques

Section URL: https://bitcoin.ne.jp/en/learn/privacy#chain-analysis

[Figure: privacy-traces — Bitcoin’s ledger is public. Address reuse, common inputs, change, amounts and timing can be combined with exchange or other outside data to infer links between clusters and people, but inference must not be confused with certainty.]

Common-Input-Ownership Heuristic: When a transaction has multiple inputs, they're assumed to belong to the same entity. This is the most fundamental and powerful chain analysis technique.

Change Address Detection: When you send Bitcoin, the leftover returns as "change." Identifying this change address reveals wallet ownership. Amount patterns, address format differences, and wallet software fingerprints all serve as clues.

Amount & Timing Correlation: Searching the blockchain for specific amounts or timestamps narrows down transaction parties.

Combining these techniques ("data fusion") turns individually trivial information leaks into severe privacy breaches.

The parties actually doing this are blockchain analytics firms such as Chainalysis, TRM Labs, and Elliptic. Their customers are crypto asset exchange providers, financial institutions, and law enforcement, who use the output to screen deposits and withdrawals (classifying what kind of entity an address belongs to) and to trace funds in investigations. It is not that nobody is watching: an industry exists whose business is tracing, and its product is consulted as a matter of routine.

There is institutional reinforcement too. In Japan, the travel rule under the amended Act on Prevention of Transfer of Criminal Proceeds (Article 10-5) took effect on June 1, 2023, obliging crypto asset exchange providers to notify the receiving provider of the sender's name, residential address (or a customer identification number) and blockchain address, and the recipient's name and blockchain address, when crypto is transferred. Even where only public keys and addresses are visible on-chain, identity information circulates alongside it between providers. The wider regime is covered in "Regulation — Japan & the World."

### The danger of address reuse

Section URL: https://bitcoin.ne.jp/en/learn/privacy#address-reuse

Address reuse is one of the biggest threats to privacy. Using the same address repeatedly links all associated transactions to a single entity.

"Forced address reuse attacks" also exist: attackers deliberately send small amounts to already-used addresses, hoping wallet software will spend them alongside other coins, exposing additional addresses through the common-input-ownership heuristic.

The solution is simple: use a new address for every transaction. Modern wallet software (HD Wallets, BIP-32) does this automatically.

### Privacy-enhancing technologies

Section URL: https://bitcoin.ne.jp/en/learn/privacy#privacy-techniques

CoinJoin: Combines multiple users' transactions into one, breaking the common-input-ownership heuristic. Implemented in JoinMarket and others. The effect is not unconditional, however: if the anonymity set mixing at the same time is small, narrowing down is easy, and the very shape of equal-value outputs is itself detectable as a CoinJoin. Spending several of the mixed outputs together afterwards re-engages the common-input-ownership heuristic and undoes the benefit.

PayJoin (P2EP): both sender and receiver contribute inputs to one transaction. This breaks the assumption that all inputs belong to one owner and makes ownership inference harder. It does not guarantee protection from analysis using other information.

Lightning Network: Off-chain transactions minimize the on-chain footprint, and onion routing means an intermediate node knows only its immediate predecessor and successor. That is not the same as nobody being able to tell. In today's HTLCs the same payment hash is used along the whole route, so an observer controlling several relaying nodes can correlate them as one payment (replacing HTLCs with PTLCs is the proposed fix, not deployed as of August 2026). On top of that, the public channel graph and small trial payments (probing) can be used to infer balances and endpoints, and with custodial wallets the provider holds the entire history.

Tor: configuring Bitcoin node traffic to use Tor can keep the node's IP address from being exposed directly to those peers. It does not prevent identification through other network connections or transaction information.

### Privacy best practices

Section URL: https://bitcoin.ne.jp/en/learn/privacy#privacy-best-practices

Run a full node: Verifying and broadcasting transactions through your own node prevents third-party servers from learning your balance and transaction patterns.

New address per transaction: Use HD Wallets (BIP-32/44) and generate a fresh address for every receipt.

Coin control: Manually select UTXOs in your wallet to prevent mixing coins from different sources.

Understand what KYC does: At exchange providers in Japan and most other jurisdictions, identity verification is a statutory obligation, not something a user can opt out of. What matters is that an address you withdraw to is linked to your real name in that provider's records. Moving the funds to another address afterwards does not erase the link, because the move itself is recorded on-chain. How much of this matters depends on the threat model described below.

Privacy begins with defining "who you're hiding from." Define your threat model and implement appropriate countermeasures.

### Taproot and the evolution of privacy

Section URL: https://bitcoin.ne.jp/en/learn/privacy#taproot-privacy

Taproot (BIP-340/341/342), activated in 2021, significantly improved Bitcoin's privacy.

Schnorr signatures allow several keys to be combined into one (key aggregation), so under the right conditions a multisig spend becomes indistinguishable from an ordinary one. The scope is limited, though. MuSig2 (BIP-327), the aggregation scheme in practical use, covers n-of-n arrangements where every participant signs. A threshold such as 3-of-5 (k-of-n) can be built through Taproot's script path (using CHECKSIGADD and the like), and in that case the condition becomes visible on-chain when it is spent. FROST produces a single threshold signature and was published in June 2024 as the IRTF Informational document RFC 9591. It is not an IETF Internet Standard, and even the RFC's secp256k1 suite is not directly compatible with Bitcoin's BIP-340 signatures. The BIP-445 proposal (PR #2070) for BIP-340-compatible signing and key tweaking remains a Draft and has not been merged into the official BIP repository as of October 20, 2026. Publication of a specification and support in a particular wallet or service need to be checked separately.

MAST (Merklized Alternative Script Trees) ensures that unused script branches aren't revealed on the blockchain. Even complex smart contracts only expose the executed path.

These changes can reduce the spending conditions revealed on-chain. The benefit depends on the spending path, wallet implementation, address reuse, and other factors. Using Taproot does not make every user's transactions anonymous.

### Regulatory pressure on privacy wallets (2024–2026)

Section URL: https://bitcoin.ne.jp/en/learn/privacy#privacy-pressure-2024

April 2024: U.S. DOJ indicted two operators of Samourai Wallet for conspiracy to operate an unlicensed money transmitting business and conspiracy to commit money laundering. The operation of their CoinJoin mixing service "Whirlpool" was central to the charges.

The two defendants pleaded guilty to conspiracy to operate an unlicensed money transmitting business on July 30, 2025. In November 2025, CEO Keonne Rodriguez was sentenced to five years and CTO William Lonergan Hill to four years in prison. Each received a $250,000 fine and three years of supervised release. DOJ reported a $237.83 million forfeiture order and payment of $6,367,139.69, representing the fees earned. These are the district-court sentences reported by the U.S. Attorney's Office for the Southern District of New York and IRS-CI, not a statement that all later proceedings have ended.

For Wasabi Wallet (operated by zkSNACKs), the withdrawal from the U.S. market in April 2024 mattered less than what came the following month: zkSNACKs shut down its CoinJoin coordination service entirely, effective June 1, 2024. Users of Trezor Suite and BTCPay Server, which connected to that coordinator, lost the feature at the same moment (the wallet itself continues as an ordinary Bitcoin wallet).

August 2023: Tornado Cash (Ethereum mixer) developer Roman Storm was indicted and arrested, bringing the legal risk of developing privacy tooling itself into sharp focus. A 2025 jury found him guilty of conspiracy to run an unlicensed money-transmitting business while deadlocking on the money-laundering and sanctions counts. In an order dated August 25, 2026, the court postponed the retrial to April 26, 2027, in light of the defense's pending Rule 29 motion for acquittal and request for a continuance. On September 10, the court denied a motion to dismiss the remaining counts under the Speedy Trial Act; this was not a ruling on the Rule 29 motion for acquittal. Prosecutors submitted supplemental authority on venue on October 5, and in an October 9 letter, the defense argued that the cited decision did not support the prosecution's venue arguments. In a letter dated October 16, prosecutor Thane Rehn requested removal as counsel because he was leaving the U.S. Attorney's Office for other employment. Document 308 includes the court's endorsement dated the same day, granting the request and directing the clerk to remove him from the docket. This order concerns counsel's removal, not the Rule 29 motion for acquittal or sentencing.

This account uses copies of filings preserved by RECAP and the docket listing. The cited docket listing and archived copies correspond to archive identifier 604938. The ECF header on the August 25 order reads Document 300, but the September 10 order cites that adjournment order as Dkt. 299. The copy marked Document 299 is a separate order dated August 4. The citation-number discrepancy remains unresolved, and we do not treat it as a confirmed clerical error. These are not originals obtained directly from the court. The docket listing checked on October 21 dated Document 308 to October 19, while the ECF header and endorsement in the RECAP copy now obtained from Internet Archive are dated October 16. The reason for that date difference and the completeness of subsequent court records in the free archives remain unverified.

These events set a stark precedent: open-source developers of privacy tools may face criminal liability.

The result is that far fewer non-custodial CoinJoin coordinators are available in 2026, and migration to Bitcoin-native privacy features (Taproot, MuSig2, Silent Payments, and so on) is accelerating. A second, non-technical friction has appeared alongside it: UTXOs that passed through a CoinJoin are screened on deposit by exchanges relying on analytics-firm classifications, and there are reports of users being asked for further explanation or having deposits held or refused. This does not make using privacy technology illegal, but the practical cost belongs in the decision.

### Silent Payments & next-generation privacy (BIP-352)

Section URL: https://bitcoin.ne.jp/en/learn/privacy#silent-payments

Silent Payments (BIP-352) is a new protocol that fundamentally solves the address-reuse problem for the receiver.

The receiver publishes a Silent Payment Address beginning sp1q.... The sender derives a destination Taproot output using that address and information about its transaction inputs. The receiver can detect the output by scanning, but the sender that created it also knows the destination.

An outside observer cannot link on-chain outputs directly from the published Silent Payment Address alone. The protocol does not hide information already known to the sender or off-chain metadata, and does not defeat every form of chain analysis.

How far implementation has come differs sharply by wallet. As of October 2026, Bitcoin Core merged the BIP-352 primitives (#35301) into its development branch in September 2026, but wallet sending and receiving remain at the pull-request stage (#35302 and #32966), and no released version ships it. Sparrow Wallet added sending in v2.3.0 (October 2025) and receiving in v2.5.0 (May 2026). Cake Wallet supports both sending and receiving. Summaries along the lines of "Core supports it" do not match the current state, so check each wallet's status individually before relying on it.

In practice, it substantially improves privacy wherever the same payee receives repeated transfers: donations and e-commerce payments are the obvious examples.

Silent Payments requires no change to the Bitcoin protocol and works at the application layer, so adoption can proceed gradually.

### Primary Sources

- U.S. District Court - Endorsed letter granting counsel removal (dated October 16, 2026; Document 308; RECAP copy on Internet Archive): https://archive.org/download/gov.uscourts.nysd.604938/gov.uscourts.nysd.604938.308.0.pdf
- Internet Archive - RECAP file inventory for the Storm case (archive 604938): https://archive.org/metadata/gov.uscourts.nysd.604938
- Bitcoin.org - Protect your privacy: https://bitcoin.org/en/protect-your-privacy
- BIP 78 - A Simple Payjoin Proposal: https://github.com/bitcoin/bips/blob/ada341963ab3916e74c98e6de4ba48babc024a75/bip-0078.mediawiki
- Bitcoin Core v32.1 - Tor Support: https://github.com/bitcoin/bitcoin/blob/v32.1/doc/tor.md
- Bitcoin Wiki — Privacy: https://en.bitcoin.it/wiki/Privacy
- BIP-0341 (Taproot): https://github.com/bitcoin/bips/blob/master/bip-0341.mediawiki
- BIP-0327 (MuSig2 — Schnorr key aggregation): https://github.com/bitcoin/bips/blob/master/bip-0327.mediawiki
- BIP-0352 (Silent Payments): https://github.com/bitcoin/bips/blob/master/bip-0352.mediawiki
- U.S. DOJ — Samourai Wallet Founders Charged: https://www.justice.gov/usao-sdny/pr/founders-and-ceo-cryptocurrency-mixing-service-arrested-and-charged-money-laundering
- U.S. DOJ — Samourai Wallet Founders Sentenced (November 2025): https://www.justice.gov/usao-sdny/pr/founders-samourai-wallet-cryptocurrency-mixing-service-sentenced-five-and-four-years
- U.S. DOJ — Roman Storm Conviction Announcement: https://www.justice.gov/usao-sdny/pr/founder-tornado-cash-crypto-mixing-service-convicted-knowingly-transmitting-criminal
- zkSNACKs — Discontinuing the CoinJoin Coordination Service (effective June 1, 2024): https://blog.wasabiwallet.io/zksnacks-is-discontinuing-its-coinjoin-coordination-service-1st-of-june/
- Japan FSA — Amendments implementing the crypto travel rule (in force June 1, 2023): https://www.fsa.go.jp/news/r4/sonota/20230526-2/20230526-2.html
- U.S. District Court - RECAP copy of retrial adjournment order (August 25, 2026; ECF header: Document 300): https://storage.courtlistener.com/recap/gov.uscourts.nysd.604938/gov.uscourts.nysd.604938.300.0.pdf
- U.S. Attorney - RECAP copy of supplemental authority on venue (October 5, 2026; ECF header: Document 305): https://storage.courtlistener.com/recap/gov.uscourts.nysd.604938/gov.uscourts.nysd.604938.305.0.pdf
- RFC 9591 - FROST (IRTF Informational, June 2024): https://www.rfc-editor.org/rfc/rfc9591.html
- BIP-340 - Bitcoin Schnorr signature format: https://github.com/bitcoin/bips/blob/130b8e0fa7f30fa45532f080b87b8db27a79e46e/bip-0340.mediawiki
- BIP-445 proposal - FROST draft for BIP340 (October 12, 2026 version): https://github.com/siv2r/bips/blob/363f69340b6731368db4a514147c7dec8eb5fd99/bip-0445.md
- Bitcoin BIPs PR #2070 - FROST draft proposal status: https://github.com/bitcoin/bips/pull/2070
- U.S. District Court - RECAP copy of Speedy Trial Act order (September 10, 2026; Document 303): https://storage.courtlistener.com/recap/gov.uscourts.nysd.604938/gov.uscourts.nysd.604938.303.0_1.pdf
- RECAP docket - entries through October 19 (corresponding to archive 604938): https://www.courtlistener.com/docket/67720764/united-states-v-storm/
- U.S. District Court - RECAP copy of letter with August 4, 2026 order (Document 299): https://storage.courtlistener.com/recap/gov.uscourts.nysd.604938/gov.uscourts.nysd.604938.299.0.pdf
- RECAP docket - August 25 order filing entry (entry 300; archive 604938): https://www.courtlistener.com/docket/67720764/united-states-v-storm/?order_by=desc#entry-300
- RECAP docket - October 5 prosecution letter filing entry (entry 305; archive 604938): https://www.courtlistener.com/docket/67720764/united-states-v-storm/?order_by=desc#entry-305
- Defense - RECAP copy of venue response (October 9, 2026; Document 306): https://storage.courtlistener.com/recap/gov.uscourts.nysd.604938/gov.uscourts.nysd.604938.306.0.pdf
- U.S. Attorney - RECAP copy of counsel-removal request (October 16, 2026; Document 307): https://storage.courtlistener.com/recap/gov.uscourts.nysd.604938/gov.uscourts.nysd.604938.307.0.pdf

### Revision history

- 2026-11-03: Corrected privacy conditions for address analysis, PayJoin, Tor and Taproot, and the Samourai sentencing account. Obtained Document 308 in the Storm case and recorded the order granting the prosecutor's removal as counsel.
- 2026-10-21: Added the September 10 Storm order and the October 9 letter filing record, distinguishing them from a Rule 29 ruling or sentencing. Identified the unresolved case-ID and citation-number discrepancies between RECAP copies and the docket listing, distinguishing these from direct court originals. Verified the October 9 defense response and October 16 prosecution counsel-removal request from additional free copies. Corrected the docket-to-archive mapping and retained the limits on the October 19 filing text and citation discrepancy.
- 2026-10-20: Checked developments in the Storm case against the court order and prosecution filing. Distinguished what senders, receivers, and outside observers can learn from Silent Payments. Distinguished the published FROST RFC from the scope of the Bitcoin-specific draft.
- 2026-10-09: Added that the Tornado Cash retrial was postponed to April 26, 2027. Corrected the Travel Rule notification items (recipient: name and address only); updated Bitcoin Core's BIP-352 status (#35301 merged) and corrected Cake Wallet's support.
- 2026-08-18: Added a bilingual diagram showing how public transaction traces, clustering heuristics, and outside data produce probabilistic rather than certain identity links.
- 2026-08-16: Brought the Samourai case up to the July 2025 guilty pleas and November 2025 sentences, added the June 1, 2024 end of zkSNACKs CoinJoin coordination, limited Schnorr key aggregation to n-of-n and distinguished k-of-n thresholds, made the Lightning privacy claim conditional, added the chain-analysis industry and Japan's travel rule, replaced the "minimize KYC" advice with a factual account, and stated Silent Payments implementation stages and the Storm docket as of August 2026
