Optional cookies require your permission.Privacy & cookies

How to explain a CoinJoin transaction in a funding file.

A CoinJoin transaction combines inputs from several participants. A reviewer examining one person’s wealth still needs the acquisition history, that person’s role, and the later use of their funds.

Adam Juchniewicz, CEO, Bitcoin Lawyer10 min read
Sources cited in this essay (4)
A black YubiKey security key with a brass contact and metal ring rests on a pale surface.
In this essay10 sections
  1. Identify what actually happened.
  2. Build the history on both sides of the privacy step.
  3. Follow one disputed history from acquisition to proposed payment.
  4. Give the real purpose, not a borrowed explanation.
  5. Resolve the accounting before debating the label.
  6. Distinguish a privacy indicator from a conclusion.
  7. Challenge the proposition that is actually disputed.
  8. Disclose proportionately through the right channel.
  9. Keep settlement suitability separate from the wider declaration.
  10. The Bitcoin Lawyer take

Identify what actually happened.

“I used a mixer” can describe very different activity. A collaborative Bitcoin transaction may combine participants’ inputs without giving an intermediary custody. Another service may receive assets and later return different assets or transfer value onward. A funding explanation should identify the actual arrangement, dates, and records rather than rely on a broad label.

This distinction matters both technically and legally. FinCEN’s 2019 US guidance distinguishes the provision of anonymizing services from merely providing software, with regulatory treatment depending on the conduct involved. It is not a worldwide declaration that every privacy transaction is prohibited, or that every non-custodial arrangement is legally unobjectionable in every circumstance.

Start with what you can substantiate: the service or software used, whether another party received control, and which funds entered the activity. Do not attach a legal conclusion simply because a tool describes itself as private, decentralized, or non-custodial.

Build the history on both sides of the privacy step.

The strongest account begins before the activity that caught the reviewer’s attention. How did the applicant acquire the Bitcoin? What paid for the purchase? What account or wallet held it beforehand? A later withdrawal record cannot answer all three questions by itself.

Then explain the privacy step using the records that actually survive. Preserve transaction references, contemporaneous wallet records, and any service correspondence. Finally, explain how the resulting holdings relate to the assets proposed for the contribution. Do not assume that a reviewer can infer the entire sequence from an output visible today.

A fictional employee who bought Bitcoin from salary, later participated in a collaborative transaction and held the resulting outputs for years has several distinct propositions to support. Salary records concern the original purchasing power; acquisition records concern the purchase; wallet records concern the subsequent movements. Combining them into one narrative helps. Calling the final balance “savings” does not substitute for them.

Follow one disputed history from acquisition to proposed payment.

Consider a fictional architect, Lena, who bought Bitcoin from employment savings in 2016, used a collaborative privacy transaction in 2020, and now proposes to fund a citizenship application. A screening report describes the current wallet as having mixer exposure. She has the purchase confirmation, the bank payment to the exchange and a wallet export, but no longer has the laptop used in 2020. Her response should address those particular facts, rather than offer a general defense of every privacy service.

The purchase records establish an exchange acquisition in her name. Her employment and bank records explain the money used for it. A withdrawal record connects the exchange to an address in her wallet records. None of those documents, alone, identifies the later output she controlled after the collaborative transaction. That connection needs its own supporting material, with any reconstruction clearly identified as reconstruction.

Suppose the surviving records show 2 BTC before the activity, total fees of 0.002 BTC, a later spend of 0.4 BTC, and a remaining balance of 1.598 BTC. These invented figures reconcile arithmetically. They do not prove the ownership connections or the lawful origin of the first 2 BTC. The calculation should sit beside the records establishing those propositions, not substitute for them. If the actual history contains additional transactions, include them instead of forcing it into this simplified example.

Her statement can say that she used the tool after a customer connected a public receiving address with her professional identity, if that is what actually happened. It should identify the supporting correspondence where available. If she cannot remember the exact reason, she should say so. An invented rationale creates a second problem without solving the missing wallet evidence.

The resulting packet may support much of the history while leaving one association uncertain. Lena should ask whether the reviewer needs further ownership evidence, a technical analysis, or a different settlement source. She should not describe an unresolved association as independently verified merely because the rest of the narrative is convincing.

Give the real purpose, not a borrowed explanation.

Privacy can have ordinary personal and commercial motivations. The applicant should describe the actual reason in their own circumstances rather than select an acceptable-sounding reason from a template. A public professional’s concern about exposing a wallet balance is not the same as a business protecting customer information, and neither should be asserted without a factual basis.

Purpose is only one part of the response. It does not prove the source of the funds or override restrictions applicable to a counterparty or service. A truthful explanation can therefore be relevant without being sufficient. The recipient may still need more evidence or may decide that the history falls outside its acceptance policy.

Keep the language measured. An applicant need not apologize for valuing financial privacy, but an ideological argument about Bitcoin does little to establish a particular acquisition. Explain why the activity occurred and what the accompanying documents demonstrate.

Resolve the accounting before debating the label.

The quantities may change across a long history for legitimate reasons, including network fees, spending, and wallet consolidation. A presentation that ignores those changes can create an avoidable discrepancy. Work in native units first and identify the relevant transactions before introducing changing fiat valuations.

Be especially careful with change outputs. A payment can spend an earlier output and return part of the value to a wallet controlled by the payer. That is not a fresh purchase. Likewise, moving funds between wallets does not create additional wealth. Treating every receipt as income can materially overstate an applicant’s history.

The evidence may not permit perfect reconstruction. Identify a gap precisely: an unavailable purchase confirmation, an uncertain association between records, or a missing service export. Do not fill it with invented dates or a diagram that makes uncertainty disappear. An incomplete but accurately bounded account allows the reviewer to decide what further evidence would be useful.

Distinguish a privacy indicator from a conclusion.

FATF includes anonymity-enhancing activity among virtual asset risk indicators. Its accompanying explanation warns against interpreting an isolated indicator as proof of criminal conduct. That gives the issue its proper scale: a reason to investigate context, not a universal finding against every user of a privacy technique.

The same caution applies in the other direction. “No crime was intended” does not answer an actual ownership dispute, a sanctions concern or unexplained funding. A direct relationship with a service also differs from remote exposure identified by an analytics method. Ask which relationship the reviewer is examining before preparing a response.

Avoid treating two different institutions’ decisions as contradictory simply because one accepts the account and another requests more evidence. They may be considering different transactions, obligations, or policies. Obtain the relevant reason where it can properly be given, and address that reason rather than promising that a prior acceptance settles the issue.

Challenge the proposition that is actually disputed.

A disagreement about a screening result can concern several different propositions. The transaction may be correctly identified but the service attributed to it may be wrong. The service may be correctly identified but the report may describe indirect exposure as direct use. Alternatively, the attribution may be accurate and the disagreement may concern the recipient’s policy. Each problem calls for a different response.

In Lena’s case, a useful clarification would identify the transaction, report date, and disputed finding, then attach the records that address it. A request that merely says the score is unfair gives the reviewer little to investigate. A request that explains why an input belongs to another participant is more concrete, provided the evidence supports that statement. Unknown third parties should remain unknown rather than receive guessed identities.

Keep the original report and any amended version. Record which finding changed and which remained. If the provider corrects an attribution, that correction should accompany later submissions where the original finding is material. A corrected technical report is useful evidence, but it does not compel a government or bank to accept the funds under its separate policy.

A private forensic report should also state its limits. What data was available? Which wallet associations came from the applicant? Which conclusions depended on a provider’s attribution? A diagram can look authoritative while combining public facts with untested assumptions. The reader needs to see those differences to judge what the report actually establishes.

Disclose proportionately through the right channel.

Provide the information needed to understand the material history, using the recipient’s agreed secure process. The explanation should identify which wallets and periods are relevant and why. A raw export of unrelated financial activity can overwhelm the review and expose other people’s information without answering the question.

Never supply recovery words or private keys as evidence. Nor should an applicant make extra transfers to obscure a disputed path, split payments to avoid scrutiny or describe an intermediary as the economic source of wealth. Those actions change the visible route without repairing the underlying explanation.

If a record is disputed, preserve the original and the basis for correction. If the issue is legal rather than merely evidential, obtain advice appropriate to the relevant jurisdiction. The aim is to make an accurate disclosure that can be evaluated, not to engineer a story that will pass every possible reviewer.

Agree who receives the explanation and who answers follow-up questions. A bank, an authorized agent, and a government reviewer may legitimately need different exhibits, but the factual account should remain consistent. Date each version and preserve the accompanying request. If a later discovery changes the explanation, identify the correction explicitly instead of allowing incompatible versions to circulate. Protecting irrelevant private information and correcting a material omission are compatible tasks when the disclosure is carefully scoped.

Keep settlement suitability separate from the wider declaration.

An applicant may own several independently documented assets. If one proposed source cannot be accepted, another source may be operationally suitable. That choice does not rewrite the applicant’s wider wealth history or change the questions on an application form. A form asking about all relevant assets or past activity still needs a truthful answer, even when a different bank balance funds the immediate obligation.

For Lena, a genuine salary-funded cash reserve might therefore be considered separately from her Bitcoin holdings. The file should explain whose money it is, how it accumulated and why it is being used. It should not present a friend’s transfer as her own earnings or describe a recent intermediary as the original source. The review remains about the real economic events.

The same distinction applies after an institution accepts a payment. Its receipt confirms the event and its decision at that time. It is not a transferable certificate that every other institution must accept the complete history. Preserve the approved explanation and evidence because later questions may concern a different obligation, period, or legal framework.

The whole picture

The Bitcoin Lawyer take

Describe the actual privacy transaction and its purpose. Reconcile the owner’s position on both sides, identify any remaining gap, and request a correction if the screening result attributes someone else’s activity to the applicant.

A screening label should lead to a precise question. Establish whether the issue is attribution, ownership, economic origin, applicable law, or the recipient’s acceptance policy. Correct the relevant error with evidence and obtain the right advice for any unresolved legal question. Moving the coins again cannot repair the historical facts.

Cite this essay

Adam Juchniewicz, CEO, Bitcoin Lawyer. “How to explain a CoinJoin transaction in a funding file.” https://www.bitcoinlawyer.com/journal/privacy-history-and-funding-disclosure