Reconstruct a position before totaling the transfers.
A decentralized finance (DeFi) export may list deposits, receipt tokens, collateral, repayments, and swaps as separate lines. Start by reconstructing one position. Identify what the investor contributed, what was borrowed, and what remained owed on the date shown. Then follow any proceeds to the payment the reviewer is being asked to assess.
Identify the initial capital and its owner. Then describe what happened to it: an exchange of assets, liquidity provision, lending, borrowing, reward accrual, or a transfer between controlled wallets. If a company or jointly owned arrangement supplied the capital, the applicant’s ability to sign a transaction does not make the entire position personal property.
The July 2026 DeFi report from the Financial Action Task Force (FATF) emphasizes a functional and risk-based approach, including analysis of who exercises control. It is regulatory guidance, not an approval checklist for a citizenship applicant. Its useful lesson here is to look at the actual activity and authority behind an arrangement rather than relying on a decentralized label.
Separate the asset flow from the wealth explanation.
The transaction history shows where the units moved. The wealth history explains how the investor became entitled to them. A person reviewing a house purchase, a bank deposit, or a citizenship contribution needs those two accounts to meet at the amount now proposed for payment.
For each material interaction, retain the network, transaction identifier, date, assets in and out, relevant contract, and purpose. Explain internal transfers so they are not counted as fresh income. Identify a receipt token or claim separately from the underlying asset where both appear in an interface. Reconcile the opening position, external additions, returns, disposals, fees, and closing position.
A hypothetical liquidity position illustrates the issue. Tokens deposited into a pool and the resulting position token are records of one arrangement. Adding both displayed values as separate unencumbered wealth could double-count the same exposure. The file should explain what the position represents, how its value was calculated, and what must happen to realize it.
Keep debt and restrictions visible.
Borrowing against an asset can produce a spendable balance without creating the same amount of net wealth. Record the liability, collateral, repayment terms, and relevant restrictions. If borrowed proceeds are proposed for an application or contribution, establish whether that funding arrangement is permitted before treating the balance as available.
A dashboard’s gross position can also conceal pooled ownership, locked assets, or claims held for someone else. Identify the legal and economic owner of each material position. Where the arrangement is disputed or its legal character is uncertain, obtain the necessary advice rather than resolving it through a spreadsheet label.
Timing matters. An asset shown at a valuation date may no longer be available after repayment, liquidation, withdrawal, or a transfer. State the date of the position and distinguish historic wealth from funds presently intended for settlement. A reviewer should not have to infer whether the same collateral supports several different proposed uses.
Explain bridges and wallet control without exposing keys.
For a bridge movement, connect the source-network event to the destination-network receipt, and explain the mechanism used. Preserve both transaction identifiers and any provider record. Similar amounts close in time are useful leads, but do not claim they prove a particular linkage unless the record supports it. Fees, wrapped assets, and intermediate steps should remain visible.
Present control is a narrower proposition than historic beneficial ownership. Bitcoin Core’s message-verification method checks a message, signature, and address; it does not establish how the assets were acquired. Signing methods also differ by wallet and address type. Agree a compatible and proportionate demonstration with the reviewer before making any operational change.
A multisignature or contract wallet needs an explanation of signers, thresholds, and relevant permissions. A person authorized to initiate a proposal may not be able to execute it alone. Preserve the applicable configuration and period. Never supply recovery words, private keys, or an unrestricted wallet backup as a source-of-funds exhibit.
Make valuation reproducible and keep tax work distinct.
A fiat total needs a method. Record the source, date, time convention, currency, and treatment of fees. Where a token is thinly traded or a position is difficult to realize, describe the limitation rather than presenting a screen price as guaranteed sale proceeds. Use a consistent approach instead of choosing favorable prices for different lines.
A valuation prepared for an application is not automatically a tax computation. The relevant tax professional may need acquisition dates, basis, disposals, and income character that the onboarding narrative does not resolve. Keep their conclusions and assumptions distinguishable from the transaction schedule. Do not infer tax treatment from the protocol’s label for an event.
If software changes how it classifies an interaction, preserve the earlier output and explain the revision. A manually corrected record should identify the original transaction, the correction and its basis. The value of the report lies in making the reasoning reviewable, not in hiding the work needed to interpret imperfect data.
Build for a reader who does not use the protocol.
Lead with the owner, initial economic source, main activities, resulting position, and proposed funding route. Add a glossary only for terms needed to understand those facts. Group repetitive interactions into intelligible periods while preserving access to the underlying transactions. A reviewer should be able to test a material line without learning an entire interface.
Include a candid account of missing evidence. A closed frontend, unavailable counterparty, or uncertain contract attribution should have a retrieval history and a stated effect on the conclusion. Do not invent a transaction description because software cannot decode it. A qualified technical review may be useful, but its assumptions should remain visible.
The file is ready for substantive review when the reader can distinguish contribution from return, ownership from control, assets from liabilities, and observation from inference. That standard does not guarantee acceptance by a bank or authority. It creates an honest basis for deciding what can be submitted and what still needs work.
A worked example: reconcile the position before the proceeds.
Consider a fictional applicant who supplies assets to a lending protocol, receives a token representing the position, borrows against collateral, and later repays part of the debt. An export shows a deposit, a token receipt, a loan receipt, rewards, and several transfers. Adding all incoming entries as earnings would confuse contributed capital, a claim against that capital, debt, and any actual return.
Begin with an opening balance and the source of the capital. Identify the deposit and the position it created. Then record the liability associated with borrowing, the assets received, repayments, fees, and any changes to collateral. The object is a reconciliation someone can follow without knowing the interface. If the arrangement’s economic or legal character is unclear, preserve that issue for the appropriate professional.
Now identify the assets intended for the contribution. Are they the borrowed proceeds, assets withdrawn after repayment, or returns realized separately? Each answer changes the explanation and potentially the recipient’s requirements. A dashboard total cannot decide whether funds are available without restriction, and a position token should not be counted again beside the assets it represents.
This example assumes no particular return or tax treatment. It illustrates classification. A technically accurate export can still be economically misleading when its rows are assigned the wrong meaning. Have the material events reviewed against the contracts, transaction evidence, and applicable records before the numbers enter a wealth statement or an application declaration.
Describe authority as it existed at the time.
A multisignature wallet can change signers or thresholds. A contract wallet can use modules, delegated permissions, or a governance process. Describe the relevant configuration for the period under review, not only the configuration visible today. If a business controlled the position, include the records establishing who could authorize activity and whose assets the signers were managing.
A fictional founder who holds one of three signing keys may be able to propose a transfer without being able to execute it alone. That is different from sole control. If the founder later becomes the only signer, present control does not rewrite the earlier arrangement. The chronology should identify the change and its basis so the reviewer can distinguish continuity of ownership from changes in technical authority.
Where evidence of control is requested, agree the scope and method before operating the wallet. A signing demonstration should not expose secrets or authorize an unintended transaction. A transaction proposed as proof can have fees, disclosure consequences, and a real destination. Use only a method understood by the parties and appropriate to the wallet, rather than copying instructions meant for another network or address type.
The accompanying legal records remain necessary. A technically valid signature does not prove that the signer is the beneficial owner, that funds are unencumbered, or that an earlier acquisition was lawful. The strongest file connects technical observations to the agreement or organizational record that gives them economic meaning.
Preserve enough detail to revise an interpretation.
Protocol interfaces and data parsers change. A transaction that one tool labels as income may be recognized later as an internal movement or redemption. Preserve the raw identifier and source data alongside the interpretation. That allows a later reviewer to understand why the classification changed without treating a revised spreadsheet as an unexplained alteration of history.
Use a stable event reference across the narrative, schedule, and exhibits. Record the network and asset identifier where ticker symbols could be ambiguous. For a bridge, retain the evidence linking the source event to the destination receipt. Where that link is inferred from timing and amounts rather than directly supported, state the inference and its limits. Similar numbers alone should not carry the whole conclusion.
A small number of material examples can explain a repeated activity, but the underlying schedule should still reconcile the period. Define which interactions have been grouped and why. Do not hide a different activity inside a category chosen for convenience. A reward, a repayment, and an unsolicited token receipt can require different treatment even when each appears as an incoming line.
This is useful beyond citizenship. The same reliable event history can help an accountant assess reporting, a bank understand conversion proceeds, or a business explain treasury activity. Each recipient may reach a different conclusion under its own rules. Good data makes those conclusions reviewable without pretending that one software export has settled every legal, accounting, and tax question.
The whole picture
The Bitcoin Lawyer take
Give the reviewer the assets and the outstanding debt as of the same date. A wallet export becomes a wealth statement only after the owner explains which positions are theirs, what is pledged, and what must be repaid.
If the reviewer can see a deposit but cannot identify its corresponding loan, pause the calculation there. An accurate statement that one position is unresolved is more defensible than a total that silently counts borrowed capital as wealth.


