The most common reason a Bitcoin citizenship file stalls is not the size of the holding. It is the gap in the story. The Financial Intelligence Unit, the government body that conducts due diligence on Vanuatu applications, has no opinion on whether Bitcoin is real wealth. The question it asks is procedural: can you show the audit trail from the original acquisition to the address you hold today, with documentation at every transition, in a form a compliance officer can verify without a follow-up request. Most files have one or two gaps. The work is finding them before the FIU does.
So rather than describe the process in the abstract, walk a representative file. The client is composited and the figures are illustrative, but the shape is real. The wallet history spans four acquisition events across seven years, which is typical of someone who has held through more than one cycle. Each event documents differently.
Stage one: the 2014 purchase.
The oldest coins are the hardest, because they predate the clean record-keeping the industry takes for granted now. In 2014 the client bought from an exchange that no longer sends usable statements, and moved the coins to a wallet whose address still appears in the current history. There is no tidy CSV for this.
The reconstruction has three parts. First, the on-chain record: the 2014 acquisition transaction and the path from that early address forward, which is permanent and public and can be traced. Second, any surviving fiat evidence: the bank statement showing the wire or card payment that funded the original buy, even a single line, anchors the purchase to a real-world account. Third, a signed affidavit attesting to the acquisition where documentary evidence has aged out. The FIU accepts this combination for genuinely old holdings. The standard tightens for later coins, where better records should exist and their absence is itself a question.
Stage two: the 2017 exchange consolidation.
In 2017 the client consolidated several smaller holdings onto a regulated exchange, then withdrew to self-custody. This is the stage that trips up almost every file, and it is worth being precise about why.
An exchange withdrawal is documented in two halves. The first half is the exchange record: the CSV showing the purchase or deposit, the fiat source, the date, and the withdrawal address. The second half is a signed message from that withdrawal address, proving the client controls the wallet the coins went to. The single most common gap in a Bitcoin file is one that shows the exchange side or the self-custody side, but never both, tied together. The exchange CSV proves the purchase happened. The signed message proves the destination is yours. Without both halves, the on-chain story has a missing chapter, and the FIU routes the file for enhanced review, which adds weeks.
The exchange record proves the purchase happened. The signed message proves the wallet is yours. The file needs both halves, stitched.
Stage three: the 2018 mining payouts.
For a stretch in 2018 the client ran mining hardware and received pool payouts. Mining income documents differently from purchased coins, because there was no counterparty and no purchase. The file is built from the mining-pool statements showing the payout history to addresses the client controls, plus evidence that the operation physically existed: hardware invoices and electricity bills that corroborate the hash rate the payouts imply. A solo miner without a pool documents the equivalent through the coinbase outputs at controlled addresses and the network-share math. The principle is the same as everywhere else in the file: the claim has to tie to evidence a third party can check.
Stage four: the 2021 Lightning channel.
The most recent event is the smallest and the cleanest. In 2021 the client opened a Lightning channel, which on-chain is simply a funding transaction from a known wallet to a multisignature address. Because the funding source is an address already documented earlier in the file, the channel open inherits its provenance. This is the part of the reconstruction that takes an afternoon rather than a week, precisely because the earlier stages did the hard work. Recent, well-recorded activity carries its own paper trail; the effort always concentrates on the oldest and the messiest coins.
What the FIU does not need.
It is worth stating what is not in any of this, because the fear of over-disclosure keeps people from starting. The FIU does not need your private keys, and it does not request them. It does not need your seed phrase, your full balance history across every wallet you have ever touched, or a real-time feed of your holdings. It needs cryptographic proof that the specific addresses in the file are yours, which a signed message provides without exposing anything that controls the coins. A good advisor structures the disclosure to answer the question that was asked and not a word more. Privacy and compliance are not opposites here; the file is built to satisfy the screen with the minimum sufficient evidence.
The order of operations.
The reconstruction runs oldest to newest, because the early coins set the foundation that everything downstream inherits. We trace each unspent output backward to its origin, flag every gap before the FIU sees the file, and resolve the gaps with the client first. Sometimes that means re-contacting a 2017 exchange for a historical confirmation. Sometimes it means a signed affidavit for a 2014 buy that no longer has a statement. Occasionally it means telling a client that a particular tranche cannot be documented to the standard the file needs, and deciding together how to handle it. None of this is exotic to an advisor who has done it. All of it is exotic to a traditional Citizenship by Investment agent who wanted a wire transfer and treated Bitcoin as a red flag.
That is the whole case for working with a Bitcoin-native advisor on this specific step. The program rules are public. The fee math is on the pricing page. The one part of a Vanuatu file that genuinely rewards lived experience is the source-of-funds reconstruction, because the failure modes are particular to how Bitcoiners actually hold, and the FIU is reading for exactly the gaps a self-assembled file tends to leave.
If your history looks anything like the four stages above, the reconstruction is tractable. The point of starting early is that the documentation is easier to assemble before a deadline than during one. Low time preference does not mean no action. It means building the file the FIU is going to read, before you need it read.
Adam Juchniewicz, CEO, 21 CBI
Buenos Aires · May 2026