trisacrypto · bbengfort · Jan 5, 2026 · Dec 31, 2025
diff --git a/LICENSE b/LICENSE
@@ -1,6 +1,6 @@
 The MIT License
 
-Copyright (c) 2021 TRISA https://trisa.io
+Copyright (c) 2021 TRISA https://travelrule.io
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal

diff --git a/README.md b/README.md
@@ -4,7 +4,7 @@
 [![Go Reference](https://pkg.go.dev/badge/github.com/trisacrypto/trisa/pkg.svg)](https://pkg.go.dev/github.com/trisacrypto/trisa/pkg)
 [![Go Report Card](https://goreportcard.com/badge/github.com/trisacrypto/trisa)](https://goreportcard.com/report/github.com/trisacrypto/trisa)
 
-Please visit the [TRISA website](https://trisa.io) for more information and the [TRISA documentation](https://testnet.directory) for developer docs and integration.
+Please visit the [TRISA website](https://travelrule.io) for more information and the [TRISA documentation](https://testnet.directory) for developer docs and integration.
 
 # Contributing to TRISA
 
@@ -14,7 +14,7 @@ If you're a developer whose organization is using (or planning to adopt) the TRI
 
 ## Navigating the Repository
 
-This repository contains a gRPC implementation of the TRISA protocol as described by the [white paper](https://trisa.io/trisa-whitepaper/), which leverages [protocol buffers](https://grpc.io/) and Golang.
+This repository contains a gRPC implementation of the TRISA protocol as described by the [white paper](https://travelrule.io/trisa-whitepaper/), which leverages [protocol buffers](https://grpc.io/) and Golang.
 
 The `proto` folder contains the core RPC definitions, including:
  - the interVASP Messaging Standard (IVMS) message definitions, which serve as the basis for how two VASP peers should mutually describe entities involved in cryptographic transfers, including names, locations, and government identifiers. This is the spec that will allow originators to identify themselves to beneficiaries and to request information from those beneficiaries to meet the legal requirements of their regulators.

diff --git a/docs/content/_index.de.md b/docs/content/_index.de.md
@@ -10,9 +10,8 @@ weight: 0
 
 [![Go Report Card](https://goreportcard.com/badge/github.com/trisacrypto/trisa)](https://goreportcard.com/report/github.com/trisacrypto/trisa)
 
-Das Ziel der Travel Rule Information Sharing Architecture (TRISA) ist es, die Einhaltung der FATF- und FinCEN-Reiseregeln für Kryptowährungs-Transaktionsidentitätsinformationen zu ermöglichen, ohne die Kernprotokolle der Blockchain zu verändern und ohne erhöhte Transaktionskosten zu verursachen oder die Peer-to-Peer-Transaktionsflüsse virtueller Währungen zu verändern. Das TRISA-Protokoll und die Spezifikation werden von der [TRISA Working Group](https://trisa.io) definiert; um mehr über die Spezifikation zu erfahren, [lesen Sie bitte die aktuelle Version des TRISA-Whitepapers](https://trisa.io/trisa-whitepaper/).
+Das Ziel der Travel Rule Information Sharing Architecture (TRISA) ist es, die Einhaltung der FATF- und FinCEN-Reiseregeln für Kryptowährungs-Transaktionsidentitätsinformationen zu ermöglichen, ohne die Kernprotokolle der Blockchain zu verändern und ohne erhöhte Transaktionskosten zu verursachen oder die Peer-to-Peer-Transaktionsflüsse virtueller Währungen zu verändern. Das TRISA-Protokoll und die Spezifikation werden von der [TRISA Working Group](https://travelrule.io) definiert; um mehr über die Spezifikation zu erfahren, [lesen Sie bitte die aktuelle Version des TRISA-Whitepapers](https://travelrule.io/trisa-whitepaper/).
 
 Diese Website enthält die Entwicklerdokumentation für das TRISA-Protokoll und die Referenzimplementierung, die unter [github.com/trisacrypto/trisa](https://github.com/trisacrypto/trisa) zu finden ist. Das TRISA-Protokoll ist als [gRPC-API](https://grpc.io/) definiert, um sprachunabhängige, hochleistungsfähige Peer-to-Peer-Dienste zwischen Anbietern virtueller Asset Services (VASPs) zu ermöglichen, die Lösungen zur Einhaltung der Travel Rule implementieren müssen. Sowohl die API als auch das Nachrichtenaustauschformat werden über [protocol buffers](https://developers.google.com/protocol-buffers) definiert, die im [`protos` directory](https://github.com/trisacrypto/trisa/tree/main/proto) des Repository zu finden sind. Darüber hinaus wurde eine Referenzimplementierung in der [Go Programmiersprache](https://golang.org/) im [`pkg` directory](https://github.com/trisacrypto/trisa/tree/main/proto) des Repositorys zur Verfügung gestellt. In Zukunft werden weitere Implementierungen als Bibliothekscode für bestimmte Sprachen im [`lib` directory](https://github.com/trisacrypto/trisa/tree/main/lib) des Repositorys zur Verfügung gestellt.
 
 Die Version v1 von TRISA befindet sich in aktiver Entwicklung, weitere Dokumentation folgt in Kürze!
-
diff --git a/docs/content/_index.en.md b/docs/content/_index.en.md
@@ -24,7 +24,7 @@ The goal of the Travel Rule Information Sharing Architecture (TRISA) is to enabl
 compliance with the FATF and FinCEN Travel Rules for cryptocurrency transaction
 identity information without modifying core blockchain protocols, and without
 incurring increased transaction costs or modifying virtual currency peer-to-peer
-transaction flows. The TRISA protocol and specification is defined by the [TRISA Working Group](https://trisa.io); to learn more about the specification, [please read the current version of the TRISA whitepaper](https://trisa.io/trisa-whitepaper/).
+transaction flows. The TRISA protocol and specification is defined by the [TRISA Working Group](https://travelrule.io); to learn more about the specification, [please read the current version of the TRISA whitepaper](https://travelrule.io/trisa-whitepaper/).
 
 This site contains the developer documentation for the TRISA protocol and reference implementation which can be found at [github.com/trisacrypto/trisa](https://github.com/trisacrypto/trisa). The TRISA protocol is defined as a [gRPC API](https://grpc.io/) to facilitate language-agnostic, high-performance, peer-to-peer services between Virtual Asset Service Providers (VASPs) that must implement Travel Rule compliance solutions. Both the API and message interchange format are defined via [protocol buffers](https://developers.google.com/protocol-buffers), which can be found in the [`protos` directory](https://github.com/trisacrypto/trisa/tree/main/proto) of the repository. In addition, a reference implementation in the [Go programming language](https://golang.org/) has been made available in the [`pkg` directory](https://github.com/trisacrypto/trisa/tree/main/proto) of the repository. In the future, other implementations will be made available as library code for specific languages, found in the [`lib` directory](https://github.com/trisacrypto/trisa/tree/main/lib) of the repository.
 

diff --git a/docs/content/_index.fr.md b/docs/content/_index.fr.md
@@ -10,7 +10,7 @@ weight: 0
 
 [![Go Report Card](https://goreportcard.com/badge/github.com/trisacrypto/trisa)](https://goreportcard.com/report/github.com/trisacrypto/trisa)
 
-L'objectif de l'architecture de partage d'informations sur les règles de voyage (TRISA) est de permettre la mise en conformité avec les règles de voyage du GAFI et du FinCEN pour les informations d'identité des transactions en crypto-monnaies sans modifier les protocoles de base de la blockchain, et sans encourir de coûts de transaction accrus ni modifier les flux de transaction P2P en monnaie virtuelle. Le protocole et la spécification TRISA sont définis par le [groupe de travail TRISA](https://trisa.io) ; pour en savoir plus sur la spécification, [veuillez lire la version actuelle du livre blanc TRISA](https://trisa.io/trisa-whitepaper/).
+L'objectif de l'architecture de partage d'informations sur les règles de voyage (TRISA) est de permettre la mise en conformité avec les règles de voyage du GAFI et du FinCEN pour les informations d'identité des transactions en crypto-monnaies sans modifier les protocoles de base de la blockchain, et sans encourir de coûts de transaction accrus ni modifier les flux de transaction P2P en monnaie virtuelle. Le protocole et la spécification TRISA sont définis par le [groupe de travail TRISA](https://travelrule.io) ; pour en savoir plus sur la spécification, [veuillez lire la version actuelle du livre blanc TRISA](https://travelrule.io/trisa-whitepaper/).
 
 Ce site contient la documentation pour développeurs du protocole TRISA et la mise en œuvre de référence qui se trouve sur [github.com/trisacrypto/trisa](https://github.com/trisacrypto/trisa). Le protocole TRISA est défini comme une [API gRPC](https://grpc.io/) conçue pour faciliter le service pair à pair, performants et indépendants du langage entre fournisseurs de services et d'actifs virtuels (VASP) qui doivent mettre en œuvre des solutions de conformité aux règles de voyage. L'API et le format d'échange de messages sont définis via les [tampons de protocole](https://developers.google.com/protocol-buffers), qui se trouvent dans le [répertoire `protos`](https://github.com/trisacrypto/trisa/tree/main/proto) du référentiel. De plus, une implémentation de référence dans le [langage de programmation Go](https://golang.org/) a été mise à disposition dans le [répertoire `pkg`](https://github.com/trisacrypto/trisa/tree/main/proto) du référentiel. Dans le futur, d'autres implémentations seront disponibles sous forme de code de bibliothèque pour des langages spécifiques, dans le [répertoire `lib`](https://github.com/trisacrypto/trisa/tree/main/lib) du référentiel.
 

diff --git a/docs/content/_index.ja.md b/docs/content/_index.ja.md
@@ -11,10 +11,8 @@ weight: 0
 [![Go Report Card](https://goreportcard.com/badge/github.com/trisacrypto/trisa)](https://goreportcard.com/report/github.com/trisacrypto/trisa)
 
 
-トラベルルール情報共有アーキテクチャ（TRISA）の目標は、コアブロックチェーンプロトコルを変更したり、トランザクションコストを増加させたり、仮想通貨のピアツーピアトランザクションを変更したりすることなく、暗号通貨トランザクションID情報のFATFおよびFinCENトラベルルールへの準拠を可能にすることです流れ。TRISAプロトコルと仕様は、[TRISAワーキンググループ](https://trisa.io) によって定義されています。 仕様の詳細については、[現在のバージョンのTRISAホワイトペーパーをお読みください](https://trisa.io/trisa-whitepaper/)。
+トラベルルール情報共有アーキテクチャ（TRISA）の目標は、コアブロックチェーンプロトコルを変更したり、トランザクションコストを増加させたり、仮想通貨のピアツーピアトランザクションを変更したりすることなく、暗号通貨トランザクションID情報のFATFおよびFinCENトラベルルールへの準拠を可能にすることです流れ。TRISAプロトコルと仕様は、[TRISAワーキンググループ](https://travelrule.io) によって定義されています。 仕様の詳細については、[現在のバージョンのTRISAホワイトペーパーをお読みください](https://travelrule.io/trisa-whitepaper/)。
 
 このサイトには、[github.com/trisacrypto/trisa](https://github.com/trisacrypto/trisa) にあるTRISAプロトコルとリファレンス実装の開発者向けドキュメントが含まれています。 TRISAプロトコルは[gRPC API](https://grpc.io/) として定義されており、トラベルルールを実装する必要のある仮想資産サービスプロバイダー（VASP）間で、言語に依存しない高性能のピアツーピアサービスを促進しますコンプライアンスソリューション。 APIとメッセージ交換の形式はどちらも、[`protos`ディレクトリ](https://github.com/trisacrypto/trisa/tree/main/proto) にある[protocol buffers](https://developers.google.com/protocol-buffers) を介して定義されます。リポジトリの 。さらに、[Goプログラミング言語](https://golang.org/) のリファレンス実装が [`pkg`ディレクトリ](https://github.com/trisacrypto/trisa/tree/main/proto) で利用できるようになりました。 リポジトリの。将来的には、リポジトリの[`lib`ディレクトリ](https://github.com/trisacrypto/trisa/tree/main/lib) にある特定の言語のライブラリコードとして他の実装が利用できるようになる予定です。
 
 TRISA v1リリースは活発に開発されており、さらに多くのドキュメントが間もなく公開されます。
-
-
diff --git a/docs/content/_index.zh.md b/docs/content/_index.zh.md
@@ -10,7 +10,7 @@ weight: 0
 
 [![Go Report Card](https://goreportcard.com/badge/github.com/trisacrypto/trisa)](https://goreportcard.com/report/github.com/trisacrypto/trisa)
 
-Travel Rule Information Sharing Architecture (TRISA)的目标是在不修改核心区块链协议、不增加交易成本或修改虚拟货币点对点交易流的情况下，使加密货币交易身份信息符合FATF和FinCEN数据转移规则。TRISA协议和规范由[TRISA工作组](https://trisa.io)定义；欲了解更多有关规范的信息，[请阅读TRISA白皮书的当前版本](https://trisa.io/trisa-whitepaper/)。
+Travel Rule Information Sharing Architecture (TRISA)的目标是在不修改核心区块链协议、不增加交易成本或修改虚拟货币点对点交易流的情况下，使加密货币交易身份信息符合FATF和FinCEN数据转移规则。TRISA协议和规范由[TRISA工作组](https://travelrule.io)定义；欲了解更多有关规范的信息，[请阅读TRISA白皮书的当前版本](https://travelrule.io/trisa-whitepaper/)。
 
 本网站包含TRISA协议的开发人员文档和参考实现，可以在[github.com/trisacrypto/trisa](https://github.com/trisacrypto/trisa)查看。TRISA协议被定义为一个[gRPC API](https://grpc.io/)，用于促进那些必须遵守数据转移规则解决方案的虚拟资产服务提供商(VASP)之间的语言无关、高效、点对点的服务。API和消息交换格式都是通过[Protocol Buffers](https://developers.google.com/protocol-buffers)定义的，可以在存储库的[`protos`目录](https://github.com/trisacrypto/trisa/tree/main/proto)中找到。此外，在存储库的[`pkg`目录](https://github.com/trisacrypto/trisa/tree/main/proto)中提供了[Go编程语言](https://golang.org/)中的参考实现。在未来，其他实现将作为特定语言的库代码提供，可查阅存储库的[`lib`目录](https://github.com/trisacrypto/trisa/tree/main/lib)。
 

diff --git a/docs/content/api/_index.en.md b/docs/content/api/_index.en.md
@@ -10,7 +10,7 @@ This section of the documentation describes the TRISA Protocol and API.
 
 ###  Navigating the Open Source TRISA Code
 
-The [`trisa`](https://github.com/trisacrypto/trisa) repository contains a gRPC implementation of the TRISA protocol as described by the [white paper](https://trisa.io/trisa-whitepaper/), which leverages [protocol buffers](https://grpc.io/) and Golang.
+The [`trisa`](https://github.com/trisacrypto/trisa) repository contains a gRPC implementation of the TRISA protocol as described by the [white paper](https://travelrule.io/trisa-whitepaper/), which leverages [protocol buffers](https://grpc.io/) and Golang.
 
 The `proto` folder contains the core RPC definitions, including:
  - the interVASP Messaging Standard (IVMS) message definitions, which serve as the basis for how two VASP peers should mutually describe entities involved in cryptographic transfers, including names, locations, and government identifiers. This is the spec that will allow originators to identify themselves to beneficiaries and to request information from those beneficiaries to meet the legal requirements of their regulators.
@@ -26,6 +26,3 @@ The `pkg` folder contains the reference implementation code, including compiled
 [^1]: Note that these compiled files are compiled for Golang; but this is certainly not the only option. Those interested in building implementation code in a different language should look to the `lib` folder, which currently contains placeholder folders but is intended to showcase such other implementations (including compiled protocol buffer code for these other languages).
 
 Another integral part of the TRISA protocol is the [Global Directory Service]({{% ref "/gds" %}}), which serves as a look-up tool for TRISA members to identify peers with which they wish to exchange information. For RPC definitions and implementation code related to the Global Directory Service, visit the companion [directory repository](https://github.com/trisacrypto/directory).
-
-
-
diff --git a/docs/content/envoy/_index.en.md b/docs/content/envoy/_index.en.md
@@ -6,7 +6,7 @@ description: "Using the TRISA Envoy self-hosted node"
 weight: 12
 ---
 
-Built to help compliance teams handle travel rule exchanges efficiently and economically, Envoy is an open source, secure, peer-to-peer messaging platform. Designed by TRISA engineers and compliance experts, Envoy offers a mechanism for Travel Rule compliance by providing [IVMS101](https://www.intervasp.org/) data exchanges using the [TRISA](https://trisa.io) and [TRP](https://www.openvasp.org/) protocols.
+Built to help compliance teams handle travel rule exchanges efficiently and economically, Envoy is an open source, secure, peer-to-peer messaging platform. Designed by TRISA engineers and compliance experts, Envoy offers a mechanism for Travel Rule compliance by providing [IVMS101](https://www.intervasp.org/) data exchanges using the [TRISA](https://travelrule.io) and [TRP](https://www.openvasp.org/) protocols.
 
 #### Key Benefits
 
@@ -65,4 +65,4 @@ Public key management is required for effective use of Envoy. Envoy can store ke
 
 We strongly recommend that the internal UI and API is restricted to specific IP addresses or accessed from within a VPN. This will prevent brute force attacks on your Envoy node.
 
-Passwords and API Key secrets are stored on the Envoy disk as [Argon2](https://github.com/P-H-C/phc-winner-argon2) hashes that cannot be reversed. Argon2 is a password-hashing function that includes a time and memory cost to balance defense against cracking attacks. Even using Argon2, it is still recommended that passwords are routinely changed and that strong passwords are generated. API keys should also be revoked if not in use, or recycled on a routine basis.
+Passwords and API Key secrets are stored on the Envoy disk as [Argon2](https://github.com/P-H-C/phc-winner-argon2) hashes that cannot be reversed. Argon2 is a password-hashing function that includes a time and memory cost to balance defense against cracking attacks. Even using Argon2, it is still recommended that passwords are routinely changed and that strong passwords are generated. API keys should also be revoked if not in use, or recycled on a routine basis.