El Salvador will accept your Bitcoin. What it will not accept is a holding it cannot explain. The most common reason a Freedom Passport application stalls is not the size of the contribution, which is fixed at $1,000,000, and it is not the settlement asset, which is BTC or USDT moving direct to a government-controlled address. It is the gap in the story between the coins and where they came from. The Bitcoin Office and the Dirección General de Migración y Extranjería screen the file for source of funds, and the question they ask is procedural, not philosophical: can you show the trail, end to end, in a form a compliance officer can verify without a follow-up.
So before you wire a deposit, before the advisory engagement begins, before a single sat moves, the work is the same. Reconstruct the provenance. Find the gaps. Decide whether the file is clean, fixable, or one that cannot be filed. This is the part that rewards lived experience, because the failure modes are particular to how Bitcoiners actually hold, and the reviewer is reading for exactly the gaps a self-assembled file tends to leave.
Provenance is the real gate.
The AML and CTF screening runs over roughly two to three weeks, and it has three parts. International criminal-database checks. Sanctions screening. Source-of-funds verification. The first two are pass-or-fail and out of your hands. The third is the one you can prepare for, and the one that decides most files. It is not a check on whether Bitcoin is real wealth. It is a check on whether the chain’s story is coherent and documented, coin by coin, back to a legitimate origin.
Read the standard precisely, because the difference matters. What is required is a documented, legitimate profile, not a spotless one. A long, ordinary history of exchange buys, a few self-custody moves, and a narrative that holds together passes cleanly. A short history with one large unexplained inflow does not, however pristine the coins look on a block explorer. The provenance reaches all the way back: not to the first on-chain buy, but to the bank wire, the salary, the business income, or the asset sale that funded it.
What a complete file carries.
Every Bitcoin-funded file is built from the same evidence types. You will not have all of them. You need the ones that document how your specific coins came to be yours. Here is the accepted evidence, named plainly.
Self-custody is accepted on its own merits. The Bitcoin Office and DGME do not require that your coins sit with a regulated custodian; they require a coherent audit trail from source to address. A signed message proves you control each address without exposing a private key or seed phrase to anything but your own hardware. The keys are never requested, and never required.
What flags a file.
Some on-chain shapes make a compliance officer pause. None of them is an automatic disqualifier on its own, with a single exception, but each must be explained with a coherent narrative, and some cannot be explained at all. Mixers and tumblers, the CoinJoin sweep that deliberately obfuscates the history, need disclosure upfront and a post-mix trail a reviewer can follow. A privacy-coin conversion, a swap through Monero or shielded Zcash, takes the trail dark across the conversion; the converted portion stands only if the pre-swap source is independently documentable. An unexplained jump, a large output arriving from an address with no documented origin, is often solvable by documenting the prior address as a pre-existing wallet of yours or naming the counterparty behind the transfer. Coins with no provenance narrative at all leave nothing for the reviewer to verify, and nothing anyone can file on your behalf.
The one shape that cannot be narrated away is a sanctioned entity. If any address in your history transacted with a sanctioned party, the file fails enhanced screening regardless of intent. That is the exception. Everything else is a conversation, had early, in the right order. The honest answer is that some of these are tractable and some are not, and the value of the work is telling you which is which before you commit.
A complicated history is not a verdict. An unread one is the only real risk.
We read the chain before the government does.
This is the part that separates a Bitcoin-native file from a traditional Citizenship by Investment one, where the agent wanted a wire transfer and treated Bitcoin as a red flag. We pre-audit the on-chain provenance before submission. You bring an address list and the records you hold. We trace each UTXO backward to its origin, name every gap before the reviewer can, and tell you plainly whether the file is clean, fixable, or one we will not lodge.
If your provenance is complicated, we tell you before you spend $50,000, not after. The advisory fee is a flat 5%, and we will not lodge a thin source-of-wealth narrative because the timeline pressure is yours and not ours. The pre-audit happens before any fee moves and before a single sat leaves your wallet. That is the whole point of the order of operations: the documentation is easier to assemble before a deadline than during one, and a gap found at the address-inventory stage is a question we can answer together, while a gap the Bitcoin Office finds during enhanced review is weeks lost and, sometimes, a file that does not clear. . . . Low time preference does not mean no action. It means building the file the reviewer is going to read, before you need it read.
The program rules are public. The fee math is on the pricing page. The reserves are auditable in real time at bitcoin.gob.sv. The one part of a Freedom Passport file that genuinely rewards a Bitcoin-native advisor is this one, because the screen is reading for the gaps a self-assembled file tends to leave, and the coins, however legitimately earned, do not speak for themselves. A US person should note that home-country obligations always apply; FATCA does not pause because a second passport issues. None of that changes the provenance work. It only changes what you do after.
Adam Juchniewicz, CEO, 21 CBI
June 2026