@daily_btc_lore | Daily Bitcoin History Threads

June 21, 2019 | 7 years ago today

FATF Extends the Travel Rule to BitcoinFATF Extends the Travel Rule to Bitcoin

On June 21, 2019, the Financial Action Task Force extended its Travel Rule to crypto exchanges. The biggest gap it left is exactly where Bitcoin's original promise still lives.

What Is FATF?What Is FATF?

The Financial Action Task Force is an intergovernmental body founded in 1989 to set global anti-money laundering standards. Its 39 member countries plus the EU aren't legally bound by its recommendations, but countries that ignore them risk being cut off from the global banking system. In practice, they comply. FATF is effectively the world's financial rulemaker by consensus.

The Travel Rule Predates Bitcoin by 13 YearsThe Travel Rule Predates Bitcoin by 13 Years

The Travel Rule dates to 1996, when FinCEN introduced it for US banks under the Bank Secrecy Act. The core idea is straightforward: when money moves between financial institutions, identifying details of both the sender and the recipient must travel with it. Banks have transmitted this data alongside wire transfers for nearly three decades through SWIFT, the interbank messaging network built in 1973.

On June 21, 2019, FATF extended that same requirement to Virtual Asset Service Providers: exchanges, custodial wallet providers, and other businesses handling crypto. For transfers above $1,000, these businesses now had to collect and transmit full sender and recipient information to the counterpart exchange on the other side of the transaction.

The Tension With Bitcoin's DesignThe Tension With Bitcoin's Design

The conflict with Bitcoin's architecture is direct. Satoshi built a system specifically for peer-to-peer electronic cash transactions without trusted third parties and without requiring identity disclosure. The Travel Rule does not apply to self-hosted wallets or direct on-chain transfers between individuals. It only reaches regulated exchanges.

That boundary matters. FATF can require exchanges to behave like banks. It cannot require individuals to do the same, at least not through this mechanism.

The Sunrise ProblemThe Sunrise Problem

That gap between compliant and non-compliant jurisdictions immediately created what the industry came to call the "sunrise problem." Countries implemented the rule at different times, meaning exchanges in compliant jurisdictions had to collect sender and recipient information they had nowhere to send. Counterpart exchanges in other countries had no systems to receive it. Complying unilaterally was largely pointless.

The technical challenge turned out to be significant in its own right. Banks transmit wire data through SWIFT, a network running since 1973 and wired into the global financial system. Crypto exchanges had nothing equivalent. An entire compliance industry had to be built from scratch: new messaging protocols, new counterparty verification systems, new data standards. Notabene, Sygna, TRP, and others emerged to fill the gap.

Five Years Later: 75% Non-CompliantFive Years Later: 75% Non-Compliant

Despite six years of effort since adoption, FATF's own July 2024 report found that 75% of jurisdictions were still only partially compliant or non-compliant. The gap between setting a global standard and implementing it across thousands of exchanges in more than 100 countries proved far larger than anticipated.

The EU Went FurthestThe EU Went Furthest

The EU moved most decisively. Its Transfer of Funds Regulation went live on December 30, 2024, requiring full Travel Rule compliance on every crypto transfer between exchanges, with no minimum threshold. Every transaction, every time, full KYC data on both sides. The EU also defined the rule broadly enough to cover stablecoins and most tokenized assets, not just Bitcoin.

What the Rule Can't ReachWhat the Rule Can't Reach

Self-hosted wallets remain outside the Travel Rule's reach. The rule applies to exchanges and custodial providers, not to individuals controlling their own private keys. A person sending Bitcoin directly from their own wallet to another person's wallet on-chain has no VASP in the middle to collect and transmit data.

That gap is not an oversight. It is the boundary where the financial system's ability to impose wire transfer logic onto Bitcoin runs out. Whether regulators eventually find a way to extend requirements to self-hosted wallets, or whether that proves impossible as a practical matter, is one of the more consequential open questions in Bitcoin policy.

For now, the original design holds at that boundary: two parties transacting directly, without a trusted third party in between.