Begin with the acquisition, not today’s balance.
An early holder can show a substantial balance and still struggle with a straightforward question: how did you acquire these coins? The wallet answers where assets can be spent from now. A bank, citizenship reviewer, or tax professional may need to understand the earnings, purchase, mining activity, or transfer that put them there. Those are different propositions, and one screenshot rarely establishes both.
Start by naming the claim. “I bought Bitcoin in 2014 using employment savings” needs evidence of employment, available savings, the purchase, and the connection to the later holding. “I mined it” needs a different history. A mixed holding needs several explanations. Do not force ten years of activity into the story of its oldest transaction merely because that transaction is easiest to find.
The work becomes manageable when the claim is narrow enough to test. Pick an acquisition period and identify what is known, what can be recovered, and what depends on memory. A specific gap can be investigated. A general assertion that everything happened long ago gives a reviewer little to work with.
Preserve what remains before trying to explain it.
Old email accounts, exchange exports, bank statements, invoices, and device backups can contain parts of the same history. Work on copies and retain the originals in their original form. A screenshot can help explain a record, but it should not silently replace a downloadable statement or original message. Keep a note of where each item came from, when it was recovered and any transformation made for readability.
A useful technical principle is to preserve evidence integrity before analysis. NIST’s forensic guidance provides a framework for collecting, examining, analyzing, and reporting digital data. It is technical guidance, not a promise that a particular bank, court, or citizenship authority will accept a reconstructed file.
Do not create a new custody problem to solve a paperwork problem. A reviewer should not receive a seed phrase, private key or unrestricted wallet export. An extended public key can also expose more of a wallet’s history than a single transaction. Agree on the minimum evidence required and a suitable delivery channel before disclosing it.
Build three histories and reconcile their differences.
The first history follows the money used to acquire Bitcoin: salary, business receipts, an asset sale, or another source. The second follows the platform or counterparty: deposits, trades, withdrawals, and account identifiers. The third follows the chain: transaction IDs, relevant outputs, and later movements. They will not always use the same date, time zone, currency, or unit.
A bank debit on Monday and an exchange credit on Tuesday are not necessarily contradictory. Nor should they be treated as the same event without explanation. Record the currency, exchange conversion, fees, and settlement interval. If the platform statement reports a gross withdrawal and the wallet received a smaller net amount, account for the difference rather than altering one number to make the spreadsheet match.
Illustrative example: a holder finds a bank debit, an exchange confirmation, and a later withdrawal, but the exchange account is closed. The documents may support the purchase and withdrawal even if a complete trading ledger is unavailable. The file should say exactly that. It should not turn three surviving records into a claim that every intervening trade has been independently verified.
A fictional cash purchase shows the difference between context and proof.
Imagine that Daniel says he bought Bitcoin for cash at a local meeting in 2013. He has an old forum message arranging the meeting, a cash withdrawal around the same date and a wallet transaction received that evening. He cannot locate the seller. These records may corroborate parts of the account, but none alone identifies the seller or establishes the complete terms of the purchase.
Daniel should preserve the message in its original format if available, the complete bank statement and the transaction reference. A new screenshot showing only the amount and date can remove information needed to assess authenticity and context. If the forum used a pseudonym, he should explain what connects that account to him, rather than assume the name is self-evident.
An archived page showing that the meeting took place provides context. It does not prove Daniel attended, exchanged that amount of cash, or received the particular coins in return. A historic price chart can indicate whether his recollection is plausible, but a plausible price is not a receipt. The narrative should keep those distinctions visible.
If a contemporaneous email describes the deal and matches the amount received, the account becomes stronger. It still needs to say what remains uncertain. A later statement from Daniel can explain his recollection and the unsuccessful attempt to locate the seller. It cannot retrospectively become the seller’s confirmation or guarantee that a reviewer will accept the funding source.
Preservation proves consistency of a file, not truth of its contents.
A cryptographic hash can help show that a preserved digital file has not changed between two points in the reconstruction. It does not establish that the original file was authentic, complete, or accurate when first collected. A fabricated statement can also have a stable hash. Keep the integrity check separate from the assessment of the record’s source and meaning.
The same distinction applies to metadata. A file creation date can reflect a download or conversion rather than the underlying transaction. An email export may preserve useful headers, but their interpretation depends on the source and format. Avoid treating every visible date as independent corroboration of an acquisition date.
Use a simple record of transformations. If a spreadsheet is converted to PDF, retain both. If a document is translated, keep the original language and identify the translation. If several pages are combined for reading, preserve the separate source files and their order. These steps let a reviewer retrace the work without assuming the presentation is the only surviving evidence.
The purpose is proportionate preservation, not claiming to have conducted a certified forensic investigation. If disputed authenticity or specialist recovery becomes material, define that question for a competent specialist. Ask what can be recovered safely, what the analysis can establish, and what risks the procedure creates for devices or signing material.
A transaction graph needs an ownership explanation.
A transaction can establish that an earlier output was spent. It does not, by itself, establish who beneficially owned it, why the transfer occurred, or whether it was a sale. Exchange batching, change outputs, shared arrangements, and collaborative transactions complicate a simple address-to-person story. Distinguish a directly documented connection from an analytical inference.
Label wallets according to the evidence available. “Withdrawal to the address recorded in the account export” is a more precise statement than “all addresses in this cluster belong to the applicant.” If a report uses clustering or another heuristic, identify that method and its limits. Do not describe an attribution as certain solely because a software tool colored several addresses alike.
A proposed ownership demonstration also deserves review. Signing an unfamiliar message or moving assets on demand can create security and privacy consequences. Establish who is requesting the demonstration, which proposition it is intended to establish, and whether a narrower record will do. Evidence collection should not require handing control of the asset to a stranger.
Put the missing records in the file.
A reconstruction should have a visible gap register. Identify the missing period, the record sought, the recovery attempt, and the effect of the missing information. An unanswered support request, a defunct platform, and a destroyed device are different situations. A contemporaneous third-party record can carry a different evidentiary weight from a statement prepared years later.
A personal explanation can connect exhibits, describe a transaction’s purpose, and disclose uncertainty. It does not turn recollection into a bank statement. Likewise, notarizing a signature does not independently establish that every factual assertion in the signed account is correct. Keep the statement and the supporting records distinguishable.
This discipline helps decide whether the next step is further recovery, an independent analysis, a narrower funding proposal, or waiting. It also prevents a weak claim from spreading into later bank, citizenship and tax submissions. Once different versions of the same history circulate, correcting the record becomes harder than describing its limits at the outset.
Prepare for the actual decision being made.
Source of wealth explains how an overall financial position arose. Source of funds follows the assets intended for a particular payment. A citizenship contribution, a company capital payment, and a bank deposit may draw on the same holding while requiring different explanations. Ask which decision the recipient is assessing before sending an entire lifetime archive.
The tax record is related but separate. A provenance narrative may explain lawful acquisition without resolving every cost-basis or disposal question. Keep the CPA’s calculations, assumptions, and missing inputs identifiable. Do not assume acceptance by one institution binds another or that a completed source-of-funds review establishes the tax treatment.
The practical deliverable is a readable chronology, an exhibit index and a candid statement of limitations. An independent reader should be able to follow the selected funds from their economic origin to the proposed payment without guessing which attachment proves which claim.
Test competing explanations instead of selecting the most convenient one.
Daniel’s received transaction might be a purchase, a payment for work, a gift, or an internal transfer from a wallet he had forgotten. The most favorable description is not necessarily the correct one. Compare the surviving records with each plausible explanation and identify which facts support or contradict it.
An email referring to a completed freelance project would change the inquiry. The work agreement, customer, invoice, and accounting history could be more relevant than the nearby cash withdrawal. A reconstruction should be willing to revise the initial explanation when the records point elsewhere. Otherwise the process becomes an exercise in defending a memory rather than establishing a history.
A second person can test the account without access to signing secrets. Give that reader the chronology and exhibits, then ask which connections require an assumption. Where they cannot determine who owned an account, whether a payment was received or why a transfer occurred, improve the evidence or narrow the claim. More pages will not necessarily answer the missing question.
Finally, distinguish an unresolved question from an adverse conclusion. Missing evidence does not by itself establish wrongdoing. It can nevertheless prevent a particular institution from accepting the asset for a particular purpose. That practical limit should influence timing and funding choices before fees or contractual commitments depend on approval.
The whole picture
The Bitcoin Lawyer take
Write down the claim in everyday terms. Where did the purchasing power come from, who made the purchase and how did those coins reach the wallet you hold today?
Test a plausible alternative against the same evidence. Acknowledging that two explanations remain possible is more useful to a reviewer than assigning the coins a date you cannot support.


