Cowrie Research

trisa-primary-sources-2026-04-27

3 min read

TRISA primary-source snapshot

Last reviewed: 2026-04-27 UTC

Project status snapshot

What the official materials say

1) Homepage

  • URL: https://travelrule.io/
  • Key takeaways:
    • The homepage frames TRISA as decentralized cryptocurrency Travel Rule compliance and presents the system as open, peer-to-peer, secure, privacy-preserving, and available now
    • The site highlights three architectural pillars: the certificate-authority model for VASP identity, a global VASP directory, and a translation layer for interoperability across different Travel Rule approaches
    • The homepage also foregrounds Envoy as a self-hosted open-source solution to accelerate adoption, which is useful because it shows the project ships operator-facing software rather than only policy documents

2) Whitepaper

  • URL: https://travelrule.io/trisa-whitepaper/
  • Key takeaways:
    • The whitepaper states that TRISA was initiated in 2019 in response to FATF and FinCEN Travel Rule requirements for cryptocurrency transactions between VASPs
    • It says the goal is to enable compliance without modifying core blockchain protocols, increasing transaction costs, or changing peer-to-peer transaction flows
    • The whitepaper describes a certificate-authority model, VASP identity certificates, a global directory, secure message formats, and a transfer protocol with asynchronous replies and interoperability considerations
    • The whitepaper is especially valuable because it makes clear that TRISA is intended as a reusable overlay compliance network, not a single vendor product

3) Developer docs

  • URL: https://trisa.dev/
  • Key takeaways:
    • The docs describe TRISA as a gRPC API that uses protocol buffers to support language-agnostic, high-performance peer-to-peer services between VASPs
    • The docs point directly to the open-source reference implementation, protobuf definitions, and Go package documentation
    • The docs also highlight Envoy as an open-source node, which makes the architecture feel concrete and deployable rather than theoretical

4) GitHub organization

  • URL: https://github.com/trisacrypto
  • Key takeaways:
    • The public org shows separate repositories for the core protocol, Envoy node, global directory service, testnet/integration libraries, certificate-delivery service, and related utilities
    • This repo inventory is an important source signal because it demonstrates real operational scope beyond a single standards document
    • The organization page also reinforces that TRISA is open source and still maintained, with several repos updated in 2026

5) Core protocol repo

  • URL: https://github.com/trisacrypto/trisa
  • Key takeaways:
    • The repo README says it contains a gRPC implementation of the TRISA protocol, as described by the whitepaper, using protocol buffers and Go
    • It explains that the proto folder includes IVMS message definitions and TRISA service definitions for key exchange and secure-envelope transfer
    • The README also points to the companion directory repository for the Global Directory Service, confirming that discovery and identity are first-class parts of the stack

Whitepaper / technical-doc status

  • An official TRISA whitepaper exists as a web document and is a core primary source.
  • The best current source surface is the combination of the homepage, whitepaper, developer docs, and public GitHub repositories.

Research notes

  • Best current category for the library: Travel Rule compliance infrastructure / VASP identity-and-directory network / secure inter-VASP messaging protocol.
  • The key insight is that TRISA should be understood as a compliance overlay network with identity, directory, transport, and interoperability layers rather than as a policy alliance or simple messaging spec.
  • Envoy and the directory implementation are especially important because they show the protocol is backed by operator-facing software and deployment paths.

Graph View