Blockchain

Why does a compliant stablecoin transfer still require guessing my counterparty's protocol?

Oportunidad

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.

Por qué importa

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.

Cómo evalúo la oportunidad

La Puntuación de Oportunidad es mi propia lectura, no una medición: cuánto duele, con qué frecuencia aparece y qué tan poco existe para resolverlo hoy. Un valor más alto significa que creo que vale más la pena construirlo.

Gravedad7/10

Cuánto dolor causa cuando aparece.

Frecuencia8/10

Con qué frecuencia la gente se topa con ello.

Espacio en blanco7/10

Qué tan pocas herramientas buenas existen para ello hoy.