TRUST

TRUST (Travel Rule Universal Solution Technology) is a Travel Rule compliance network operated by Coinbase. Member VASPs complete an onboarding review before joining. A shared bulletin board lets a sending VASP identify which VASP controls a destination address, before the two exchange encrypted Travel Rule data directly. In Fireblocks, TRUST covers one thing: proving that you control an address in your vault accounts. Fireblocks creates that proof by signing a TRUST-formatted message with the vault account’s key. Unlike Notabene, Sumsub, and GTR, there is no automated screening, and no Trigger (Screening Policy) or Outcome (Post-Screening Policy), for TRUST. It works alongside any Travel Rule provider on the same workspace. TRUST is free and needs no enablement. It is API-only, and available on Developer Sandbox, Testnet, and Mainnet workspaces. See Travel Rule Overview for how TRUST fits alongside the other providers.

How it works

Start address ownership in TRUST. TRUST’s address ownership flow gives you a trustUuid. You choose the message prefix yourself and use it consistently when signing.
Create the proof of address. Fireblocks creates a typed message signing transaction from the vault account.
Sign. The transaction is signed like any other typed message request in your workspace.
Retrieve the signature once the transaction completes.
Submit the signature to TRUST for verification.

Proof of address uses typed message signing rather than raw signing. Typed message signing shows exactly what is being signed, in a structured, readable form, which reduces the risk of approving something other than what you intended. See Typed Message Signing.

Step 1: Create the proof of address

Call POST /screening/travel_rule/providers/trust/proof_of_address. The request accepts an optional Idempotency-Key header, valid for 24 hours.

Field	Description
`vaultAccountId`	Required. The vault account whose address you are proving.
`asset`	Required. The asset of the address, for example `BTC` or `ETH`.
`prefix`	Required. A non-empty prefix you choose for the signed message.
`trustUuid`	Required. The UUID from TRUST’s address ownership flow.

const { data: proof } = await fireblocks.travelRule.createTrustProofOfAddress({
  trustProofOfAddressRequest: {
    vaultAccountId: "0",
    asset: "ETH",
    prefix: trustPrefix,
    trustUuid,
  },
});

Step 2: Retrieve the signature

Call GET /screening/travel_rule/providers/trust/proof_of_address/{transactionId} with the proof-of-address transaction ID:

const { data } = await fireblocks.travelRule.getTrustProofOfAddress({
  transactionId: proof.transactionId,
});

if (data.signature) {
  // submit data.signature to TRUST
}

Field	Description
`transactionId`	The Fireblocks transaction ID of the proof of address.
`status`	The transaction status, for example `PENDING_SIGNATURE`. `COMPLETED` means the signature is ready. See Statuses.
`signature`	The TRUST-compatible encoded signature. Empty until `status` is `COMPLETED`.

Step 3: Submit the signature to TRUST

Send signature to TRUST to complete address ownership verification. Follow TRUST’s own documentation for this step.

On the Help Center

For an overview of TRUST in Fireblocks, see TRUST.

Get Started

Transactions

API Co-Signers

Workspace & Security

Webhooks

Direct Custody Wallets

Manage Wallets

Embedded Wallets

Canton

Gas Management

Treasury & Trading

Smart Contracts & Tokenization

Assets & NFTs

Identity & Compliance

Compliance Screening

Compliance Tooling

Payments

Offchain Signing

Key Link

Integrations

How it works

Step 1: Create the proof of address

Step 2: Retrieve the signature

Step 3: Submit the signature to TRUST

On the Help Center

​How it works

​Step 1: Create the proof of address

​Step 2: Retrieve the signature

​Step 3: Submit the signature to TRUST

​On the Help Center

How it works

Step 1: Create the proof of address

Step 2: Retrieve the signature

Step 3: Submit the signature to TRUST

On the Help Center