Bitcoin Source-of-Funds for the Freedom Passport: How Self-Custodied Stacks Get Documented for The Bitcoin Office

Source-of-funds documentation for the Freedom Passport is structurally different from source-of-funds documentation for every other Citizenship by Investment (CBI) on the 21 CBI slate. The reason is mechanical. The $1,000,000 contribution settles in BTC or USDT, on-chain, into a sovereign-controlled receiving address. The applicant’s wallet history is the primary evidence; the question is what supporting documentation The Bitcoin Office and the Dirección General de Migración y Extranjería (DGME) expect alongside it.

El Salvador’s Freedom Passport is the only CBI program in the world where the government contribution is paid in Bitcoin (or USDT) directly to a state-controlled wallet. That structure is the program’s headline differentiator. It is also the structure that makes source-of-funds documentation more demanding, not less, than at a Caribbean CBI where the contribution clears through fiat banking. The Bitcoin Office of El Salvador handles applications for the Freedom Passport. The General Directorate of Migration and Foreigners conducts sanctions and adverse-screening checks. Both agencies require a complete, verifiable trail from acquisition to current self-custody, and "I bought some Bitcoin in 2017" is not a documentation package.

This is what they actually need.

The Standard

Source of funds (SoF) for the Freedom Passport runs to a higher precision than most Caribbean CBI files because the contribution itself is on-chain. The Bitcoin Office is not asking whether your Bitcoin came from a legitimate source; it is asking, for each unit of Bitcoin in the qualifying contribution, where on the blockchain it originated and how it landed in your custody.

The framework draws from El Salvador’s Financial Intelligence Unit (Unidad de Investigación Financiera, UIF) standards adapted for Bitcoin-native files. Three standards apply.

01 / Origin verification. Every input UTXO must trace back to an identifiable acquisition event: an exchange purchase, a mining payout, a payment for services rendered, or another documented source. "Inherited from a hardware wallet" is not an origin event; the Bitcoin had to enter the wallet from somewhere.

02 / Continuity. The chain of custody from acquisition to current address must be reconstructable. Gaps where the Bitcoin moves through unidentified intermediaries (mixers, privacy-coin conversions, opaque OTC desks) require explicit explanation and additional documentation.

03 / Counterparty identifiability. Where the Bitcoin transacted with another wallet, the counterparty’s role and identity are part of the file. Peer-to-peer trades require records identifying the counterparty.

The standard is not designed to fail Bitcoin-native applicants; it is designed to fail bad actors. A clean self-custodied stack with exchange-purchase origins and a coherent audit trail clears the standard. A stack assembled over a decade with no records, opaque wallet transitions, and no persistent metadata fails it.

What The Bitcoin Office Accepts

The accepted documentation set, in order of strength.

01 / Regulated exchange purchase records with KYC. The cleanest origin path. Account statements from a regulated exchange (Coinbase, Kraken, Gemini, River, Strike, NYDIG, regulated European venues, etc.), with KYC-verified identity, dated trade confirmations, and on-chain withdrawal records to the applicant’s controlled address. The Bitcoin Office accepts this category readily.

02 / Mining records. Documentation of the mining operation that produced the Bitcoin: hardware purchase receipts, electricity bills, hosting agreements, pool payout records. For institutional-scale mining, the corporate vehicle’s records (Wyoming LLC, Salvadoran SA, etc.) substitute for natural-person records. Mining-derived Bitcoin is fully acceptable and routinely files clean.

03 / Bitcoin-denominated income. Invoice records, contractor agreements, employer statements, and on-chain receipt records for Bitcoin received as payment for goods or services. Common for Bitcoin-economy founders, Lightning-payable consultants, and Bitcoin-paid contributors to open-source projects. The standard requires records establishing the underlying service performed and the counterparty’s role.

04 / Custody attestations. Where a Bitcoin holding has been in self-custody for years and the original acquisition records are partial, a chain-analysis report from a recognized blockchain-forensics firm (Chainalysis, Elliptic, TRM Labs, CipherTrace) can establish current address provenance and historical custody continuity. Used as a supplement to first-tier records, not a substitute.

05 / Tax filing records. Capital-gains schedules, Report of Foreign Bank and Financial Accounts (FBAR) or Foreign Account Tax Compliance Act (FATCA) filings (for U.S. persons), or the equivalent jurisdictional reporting that establishes the holding has been disclosed and reported. Particularly useful for older stacks where original exchange records are incomplete.

The Bitcoin Office is the single point of intake for all five document categories. 21 CBI prepares the package in the format the Bitcoin Office expects, including a chain-of-custody narrative, supporting documents in chronological order, and English-Spanish dual presentation where translation matters.

Where The File Gets Hard

Three patterns commonly create problems, and each requires advance planning.

01 / Pre-2017 acquisitions on now-defunct exchanges. Bitcoiners who bought through Mt. Gox, BTC-e, or other shuttered platforms have legitimate origin events with no operating-exchange records to retrieve. The mitigation is a combination of contemporaneous bank-transfer records (showing fiat moving to the exchange), email confirmations from the exchange, and a chain-analysis report establishing on-chain receipt at addresses the applicant controls.

02 / Mixer or privacy-tool history. Bitcoin that has transited through a mixing service, a CoinJoin coordinator, or another privacy-tool implementation cannot be filed without explicit narrative. Mixers do not categorically fail the file, but they require an explanation of the privacy purpose, documentation that the funds were not laundered through the mixer, and forensic analysis confirming the pre- and post-mixer balances reconcile.

03 / OTC trades without counterparty records. Peer-to-peer trades, in-person OTC, and unidentified-counterparty transactions require post-hoc identification. The mitigation is to identify the counterparty (typically a known OTC desk) and obtain their records, or to demonstrate the trade through bank-transfer records that anchor the fiat side.

In each case, the failure mode is not the trigger; it is the absence of a coherent narrative. The Bitcoin Office does not require pristine. It requires explained.

The 21 CBI Pre-audit Workflow

We do not file source-of-funds documentation that we have not pre-audited. Filing a thin SoF package and hoping the Bitcoin Office does not push back is malpractice; the right move is to assemble the file in the format the Bitcoin Office expects, identify gaps before they reach the diligence team, and close those gaps before the contribution is made.

Our pre-audit runs four steps.

01 / Stack inventory. A walk through every UTXO that is in scope for the qualifying contribution. We map each input to an origin event and mark the documentation category that applies.

02 / Gap identification. Where origin documentation is incomplete, we identify what additional records are needed: bank statements, exchange archive requests, chain-analysis reports, custody attestations.

03 / Narrative drafting. A chain-of-custody narrative in the format the Bitcoin Office reviews, in dual English-Spanish presentation where the underlying records are in another language.

04 / Pre-submission review. A final read against the Bitcoin Office’s expected file shape before the application is submitted. Where flags surface, we close them before filing.

The pre-audit is included in the 21 CBI advisory engagement. We do not charge separately for it; it is part of how we close out a Freedom Passport file in 6 to 8 weeks rather than 8 to 12.

The Principle

Bitcoin source of funds is the part where most Bitcoiners get stuck on every CBI program. On the Freedom Passport specifically, the on-chain payment structure makes the SoF standard more demanding, not less, because the qualifying contribution itself moves on-chain. The Bitcoin Office is not asking whether your Bitcoin is clean. It is asking whether the documentation you bring tells a coherent story from acquisition to current custody.

A Bitcoiner with a clean exchange-and-self-custody trail clears the standard. A Bitcoiner with mining-operation records clears the standard. A Bitcoin-economy founder paid in sats clears the standard. The standard fails when the file fails to explain itself, not when the underlying acquisition was anything other than legitimate.

If your stack is straightforward, the documentation package writes itself. If your stack is complicated, plan for the work; do not start the file until the SoF package is ready. The Bitcoin Office does not look kindly on rushed filings, and the contribution does not move until the file clears.

Programs change. The programs available today may not exist next year. Every CBI threshold increase in history has been upward. Low time preference does not mean no action. It means making the right move at the right time.

If you want a pre-audit of your stack against the Freedom Passport SoF standard before you commit to the file, book a confidential advisory session. Encrypted, no obligation, no payment required to start the conversation.

Adam Juchniewicz, CEO Retired US Air Force veteran. Bitcoiner since 2020. Licensed agent of The Bitcoin Office of El Salvador.