Why does a compliant stablecoin transfer still require guessing my counterparty's protocol?
Opportunity
FATF Recommendation 16 requires VASPs to exchange originator and beneficiary data before a qualifying stablecoin transfer settles, but three incompatible protocols carry this data in practice: TRISA, TRP, and OpenVASP. Each nominally uses the IVMS101 data standard but with different trust models, inconsistent treatment of optional fields, and distinct message validation rules. A VASP initiating a cross-border USDC payment must first discover which protocol its counterparty supports, yet there is no universal discovery registry or real-time protocol negotiation layer running at scale. The FATF June 2025 Targeted Update found that serious VASPs now have to support more than one protocol because counterparties do not all speak the same one, and the FSB has flagged VASP discovery fragmentation as a key remaining infrastructure gap.
Why it matters
A universal VASP discovery layer with real-time protocol negotiation would turn Travel Rule compliance from a bespoke multi-protocol integration project into a commodity any payment corridor can consume.
How I score the opportunity
The Opportunity Score is my own read, not a measurement: how much it hurts, how often it bites, and how little exists to solve it today. Higher means I think it is more worth building.
How much pain it causes when it shows up.
How often people actually run into it.
How little good tooling exists for it today.
More problems worth solving
Why can't I prove I am solvent without showing my balance?
BlockchainWhy is moving money between chains still scarier than the early internet?
BlockchainWhy does compliance still mean a PDF and a prayer?
BlockchainWhy is self-custody still a choice between losing your keys and trusting a company?
BlockchainWhy does tokenizing a real asset still need ten middlemen?
BlockchainWhy can't a stablecoin pay someone with no internet?