v1.4.1

Hotfix: fix JSON unmarshal for null values.

What's Changed

• Fix Panic During Person Unmarshal by @bbengfort in #177

Full Changelog: v1.4.0...v1.4.1

v1.4.0

What's Changed

• Envoy Workflows Documentation by @bbengfort in #171
• Webhook Docs by @bbengfort in #172
• Update OpenAPI Docs by @bbengfort in #173
• Impropved Enum Parsing by @bbengfort in #174
• Rekeying and Disallow Fields by @bbengfort in #175
• Better IVMS101 Validation by @bbengfort in #176

Full Changelog: v1.3.0...v1.4.0

v1.3.0

What's Changed

• Update TRISA Dependencies by @bbengfort in #169

Full Changelog: v1.2.0...v1.3.0

v1.2.0

What's Changed

• Fix minor typos in the OpenVASP section of the TRISA documentation by @kshyun28 in #165
• Enumeration Helpers by @bbengfort in #166
• Update Documentation by @bbengfort in #167
• Envelope Trees and Bug Fixes by @bbengfort in #168

New Contributors

• @kshyun28 made their first contribution in #165

Full Changelog: v1.1.1...v1.2.0

v1.1.1

What's Changed

• Updates TRISA documentation with state workflows by @bbengfort in #164
• Allows .local domains to be used in Travel Addresses

Full Changelog: v1.1.0...v1.1.1

v1.1.0

This release is intended to make things simpler for developers to implement Travel Rule compliance solutions on top of TRISA. Many of these tools will be used in the Envoy project. The big updates include:

Transaction States - you can now add a workflow state to a SecureEnvelope to indicate to the counterparty what state the envelope is in. E.g. is the transaction started, pending, accepted, in need of repair, rejected, or completed? These states hint at the expected response from the counterparty and make it easier to identify what is going on when messages are mirrored or echoed.

Address Confirmation - an alpha version of address confirmation has been added (just the protocol buffer definitions). It includes three trial methods: simple, key/token, and on-chain. In the simple method, the counterparty simply reports if they have control or not. In key/token a token is encrypted with the public key of the crypto address and the counterparty must return the decrypted token using the private key. In on-chain, the counterparty must post a transaction to a supplied beneficiary address with a very small amount that serves as a nonce value; once the originating party sees the transaction on the chain they know that the counterparty has control of the address. This protocol definition does not service as an official position from TRISA about how to conduct address proof-of-control (as it has been removed from the white paper) but provides an opportunity for counterparty peers to conduct such confirmation in an automated way.

Other changes include easier rejection envelopes, HMAC validation, and better documentation.

What's Changed

• Envoy Documentation Update by @bbengfort in #160
• Easier Rejection Errors by @bbengfort in #161
• Expose HMAC validation to user by @bbengfort in #162
• Transaction States by @bbengfort in #163
• Address Confirmation Message Definitions

Full Changelog: v1.0.0...v1.1.0

v1.0.0

v1beta1

This release is the first tagged stable release of the TRISA protocol. TRISA has been in operation since May 2021 and many TRISA nodes have been developed and deployed to facilitate Travel Rule compliance. Little has changed in the base protocol, so with the release of the Envoy self-hosted node, we've marked this package as stable. This tag is officially considered the v1beta1 release along with any minor or patch versions associated with the release which will be backwards compatible.