Self-custodial wallet-to-wallet transfer. Travel Rule compliance is thin — honesty marker territory.
"A cash handoff — the sender decides to pay, but unlike a bank transfer, there's no institutional identity gate."
Self-custodial wallet on Base. No KYC gate — the wallet is permissionless. Identity is established only to the extent the wallet provider (MetaMask, Coinbase Wallet, Rainbow) collects it, which for self-custody is typically none. L4 Account and L5 Application lit, but the identity layer is hollow. **Honesty marker:** the D1 (Identity) domain is technically present but not meaningfully enforced.
"Handing someone cash — the transfer executes, no intermediary screens it, no Travel Rule data accompanies it."
USDC transfers via a single ERC-20 transaction on Base. If the USDC contract's blocklist includes either address, the transfer reverts — this is the only code-enforced compliance gate. No sanctions oracle fires unless the wallet app adds one at the UX layer. L2 Consensus and L3 Execution lit. **Honesty marker:** Stages 3-6 compress because there is no Discovery, no Negotiation, and Authorization is reduced to the USDC blocklist check.
"Receiving cash — the recipient has the funds, but no reporting happened, no Travel Rule data was exchanged, no record exists outside the blockchain itself."
USDC arrives at the recipient's self-custodial wallet. L4 Account and L5 Application lit. **Honesty marker:** D7 (Travel Rule) is listed because FATF Recommendation 16 requires it, but in practice no mechanism exists to transmit originator/beneficiary data in a permissionless self-custodial transfer. This is the structural compliance gap the industry has not solved. Recordkeeping (D11) relies entirely on on-chain transparency — no off-chain report is filed.
Resolved 3 steps across 1 chain(s). 0 threshold(s) triggered. Frameworks: Common Reporting Standard / FATCA.
Coverage notes: 5 disclosed gap(s).
Build FATF Rec 16 Travel Rule messages with TRUST, Notabene, Sygna, and OpenVASP protocol compatibility.
Simulate freeze, burn, and deny-list operations across ERC-20, Token-2022, TRC-20, and ERC-3643 — with bypass risk analysis.