Connect Fireblocks with GTR
Fireblocks is an enterprise-grade platform delivering a secure infrastructure for moving, storing, and issuing digital assets.
This documentation outlines how to integrate Fireblocks with GTR as your travel rule compliance system via the Fireblocks Travel Rule Supported Providers framework to ensure seamless transaction processing while meeting regulatory requirements.
Enable Fireblocks Integration with GTR
Step 1: Enable Travel Rule Link in Fireblocks
-
In Fireblocks dashboard, navigate to Compliance > Travel Rule Link.
-
Assign a Legal Entity for TR Link:
- Select Entity Purpose: TR Link
- Provide the vaults
- Set the discoverability mode to one of: discoverable, hidden, anonymous. (Recommended: select discoverable)
Step 2: Connect Fireblocks to GTR
-
Login to GTR Dashboard, navigate to Settings > Fireblocks
-
Click Edit
-
Paste your Fireblocks API Key (the Integration ID generated in the Fireblocks workspace) into this text field.
-
Turn on the Status toggle.
-
Click Submit.
Step 3: Generate API Key in GTR
-
Navigate to Travel Rule Info > Create API Key
-
Once you pass 2FA Verification, you will get the API Key to download.
Please be noted that GTR will automatically share this key with Fireblocks once you create it.
Step 4: Setup Public Key in GTR
-
Navigate to Settings > Public Key
-
Click Add Public Key > Production Environment Usage, and select the key algorithm as curve25519.
-
Please choose the Self-Custody Key and enter your public key.
Final Step: Go Live in GTR
When you complete the integration, you can register your VASP entity to GTR’s public VASP directory, allowing other GTR members to identify your VASP and send Travel Rule requests to you for compliance purposes.
-
Navigate to Settings > VASP Network Visibility
-
click Edit, select Visible as an API Member and Save
Important Reminder: Once you enable Visible as an API Member, your VASP will instantly appear on the GTR VASP Network list. Any GTR clients will be able to send Travel Rule requests to your server immediately, as if your VASP has the PII Receiving capability enabled by default. Ensure your server is fully stable and ready to process live traffic before activating this setting.
Disable the connection to Fireblocks
-
Login to GTR Dashboard, navigate to Settings > Fireblocks
-
Click Edit
-
Turn off the Status toggle
-
Click Submit
Important Reminder: Once you turn off the Status, the connection to Fireblocks will be disabled immediately. You will no longer be able to send or receive Travel Rule requests through Fireblocks, and the Go Live Settings (Visibility) will also be turned off at the same time.
Learn More: PII Format Specification
GTR is using IVMS101 to exchange PII data. It is a standard format for the exchange of personal identification information (PII) between parties involved in the Travel Rule process. It is designed to ensure that the PII is accurately transmitted between VASPs.
To learn how to fill in the data in IVMS101 format to exchange PII with GTR clients, please refer to this link: IVMS101 Guidelines.
Learn More: PII Encryption / Decryption
Transmitting plain-text PII is prohibited in GTR. For Fireblocks VASPs connected to GTR, all PII data must be encrypted before being sent to GTR and have to be decrypted once received from GTR.
Curve25519 is the algorithm for the PII encryption and decryption, and the Public / Private Key Pair format is ED25519.
So, you need to convert the ED25519 key to Curve25519 format to run encryption / decryption.
For a quicker encryption & decryption process, you can also leverage this open source tool provided by GTR.