Fireblocks

If your assets are held in Fireblocks, Notabene can be your Travel Rule provider through TR Link, the Fireblocks interface for Travel Rule providers. You connect the two once, and from then on your transactions run in Fireblocks while Notabene applies the policies you set in the Notabene dashboard.

Before you start

• A Notabene account, activated as described in Create your account.
• TR Link on your Fireblocks workspace, which Fireblocks Support turns on, and an API user for that workspace.
• The Fireblocks region your workspace is hosted in: US, EU, EU2 or Sandbox. A testnet workspace on Fireblocks production is in a production region, usually US.
• Ask Notabene to turn on Fireblocks for your account, and say which region your workspace is in. (placeholder)

To test, connect a Fireblocks test workspace to your Notabene sandbox account, then repeat the setup in production.

1. Create an API credential

Fireblocks calls Notabene with an API credential of your Notabene account. Create one in the dashboard as described in Authentication, and keep its client ID and secret for the next step. If you replace the credential later, give Fireblocks the new one.

2. Connect Notabene in Fireblocks

With your workspace’s API user, add Notabene as your Travel Rule provider through Fireblocks’ TR Link API. Then give Fireblocks your API credential, with the client ID as the API key and the client secret as the secret. Fireblocks answers with a customer integration ID, which you need in step 3, and can test the connection for you. Fireblocks’ TR Link API reference lists the calls.

Which provider to choose for a test workspace connected to your sandbox account is still to be confirmed. (placeholder) Then, in the Fireblocks Console, choose Notabene as your Travel Rule provider and set your screening policy.

3. Link your workspace in the dashboard

In the Notabene dashboard, open Settings › Wallet Providers › Fireblocks. Enter the customer integration ID, choose the Region your workspace is hosted in, turn Enabled on and save.

Notabene sends its status updates to Fireblocks in that region, so with the wrong region they never arrive. A change can take up to 15 minutes to apply.

Check the connection

Send a withdrawal from your workspace to an address outside it, since transfers between your own vaults are not screened. The transfer appears under Transactions in the Notabene dashboard, where you approve or reject it, and Fireblocks then shows the matching status.

Transfers

Each withdrawal’s Travel Rule message reaches Notabene as a transfer, and Notabene runs the policies you set in the dashboard, as described in Policies. They approve the transfer for you, or leave it to your team, who approve or reject it under Transactions.

Your Fireblocks screening policy decides which transactions go to Notabene, and your post-screening policy decides what Fireblocks does at each status. Once the message is ACCEPTED, Fireblocks may send the transaction, and it reports the transaction hash to Notabene when the funds move.

When a counterparty institution sends you a Travel Rule message, Notabene passes it on to Fireblocks as well.

Statuses

Notabene tells Fireblocks when a message is created and at every status change.

Your customer’s data

A message carries your customer’s data as an IVMS-101 document, encrypted to Notabene’s key for your account, which Fireblocks’ TR Link API gives you.

Encrypt it as a compact JWE with alg set to ECDH-ES and enc to A256GCM, with no signature, and copy the key’s kid into the JWE header. Notabene’s key is a P-256 elliptic-curve key, so data encrypted with RSA is refused.