TRUST

TRUST (Travel Rule Universal Solution Technology) is a Travel Rule network. Before TRUST accepts Travel Rule data for an address, you prove that you control it; Fireblocks signs that proof with Typed Message Signing, which shows exactly what is being signed instead of an opaque payload. TRUST is free, available to every workspace, and works alongside any other Travel Rule provider. It is set up through the API only and has no screening policy.

What you can do through the API

Step	Task	Console	API
1	Set up the Fireblocks SDK in your system	No	No API call; install the TypeScript SDK
2	Get a UUID from TRUST (`CreateAddressOwnership`)	No	No Fireblocks API call; request it in TRUST
3	List the addresses of an asset wallet, to prove a derived `BTC` or `BTC_TEST` address	No	Get addresses (Paginated)
3	Create a proof of address	No	`POST /screening/travel_rule/providers/trust/proof_of_address`
4	Get the encoded signature to submit to TRUST	No	`GET /screening/travel_rule/providers/trust/proof_of_address/{transactionId}`
4	Submit the signature to TRUST	No	No Fireblocks API call; submit it in TRUST

Step 1: Set up the Fireblocks SDK

Install the Fireblocks SDK in your system; proofs are created and retrieved from your code. See TypeScript SDK.

Step 2: Get a UUID from TRUST

Request address ownership in TRUST (CreateAddressOwnership). TRUST returns a UUID that ties the proof to your request.

Step 3: Create the proof of address

Field	Type	Description
`vaultAccountId`	string	Required. The vault account that holds the address.
`asset`	string	Required. The Fireblocks asset ID whose address you are proving, for example `ETH`; see Supported blockchains.
`prefix`	string	Required. Your TRUST prefix, used when signing the message. 1–255 characters.
`trustUuid`	string (UUID)	Required. The UUID from Step 2.
`address`	string	Optional. Maximum 255 characters. A derived address of the vault account to prove: a deposit address other than the default one. UTXO-based assets only: `BTC` and `BTC_TEST`. It must exist in the vault account for this asset, exactly as listed. If you leave it out, Fireblocks proves the default address. See Prove a derived address.

Accepts an optional Idempotency-Key header, valid for 24 hours. The request returns 400 if you send address for an asset other than BTC or BTC_TEST, or if the address does not belong to the vault account for this asset.

const { data } = await fireblocks.travelRule.createTrustProofOfAddress({
  trustProofOfAddressRequest: {
    vaultAccountId: "0",
    asset: "ETH",
    prefix: "trust_verification",
    trustUuid: "550e8400-e29b-41d4-a716-446655440000",
  },
});
console.log(data.transactionId, data.status); // e.g. PENDING_SIGNATURE

The proof is a typed message signing transaction. It follows the standard transaction statuses and your workspace’s Policies for approval and signing.

Prove a derived address (UTXO-based assets)

By default, Fireblocks proves the default address of the asset wallet. For UTXO-based assets (BTC and BTC_TEST), an asset wallet can have several deposit addresses. To prove one of the others, a derived address, pass it as address.

List the addresses of the asset wallet with Get addresses (Paginated). Copy the address you want to prove, exactly as listed.
Create the proof with that address:

const { data } = await fireblocks.travelRule.createTrustProofOfAddress({
  trustProofOfAddressRequest: {
    vaultAccountId: "0",
    asset: "BTC",
    prefix: "trust_verification",
    trustUuid: "550e8400-e29b-41d4-a716-446655440000",
    address: "<address from your vault account>",
  },
});

Fireblocks signs the message prefix + address + trustUuid, with no separators, using the key of that address. Both the SegWit and the Legacy form of an address are accepted. You cannot choose your own derivation path: only addresses that already exist in the vault account can be proven.

Step 4: Retrieve the signature and submit it to TRUST

Poll the GET endpoint with the transactionId from Step 3 until the transaction is signed. It always returns 200 with transactionId and status; signature and publicKey are included only once the transaction is signed.

`status`	Response includes	What to do
`QUEUED`, `PENDING_AUTHORIZATION`, `PENDING_SIGNATURE`	`transactionId`, `status`	Keep polling.
`SIGNED`, `COMPLETED`	`transactionId`, `status`, `signature`, `publicKey`	Send the signature to TRUST.
`REJECTED`, `CANCELLED`, `FAILED`	`transactionId`, `status`	Create a new proof of address.

TRUST requires the publicKey for SUI, TON, and XTZ. For BTC and BTC_TEST, the signature is Base64 text of v, r, and s (65 bytes), where v is the recovery value plus 31. The proof is complete when TRUST responds VALID.

Error	Meaning
`400`	`transactionId` is not a valid UUID v4.
`404`	No transaction exists with this `transactionId`.
`503`	The transaction lookup is temporarily unavailable. Try again.
`500`	The status is `SIGNED` or `COMPLETED`, but no signed message exists.

Supported blockchains

Blockchains supported for TRUST proof of address

Chain	TRUST ID	Fireblocks asset ID
Bitcoin	`BITCOIN`	`BTC`
Ethereum	`ETHEREUM`	`ETH`
Solana	`SOLANA`	`SOL`
Tron	`TRON`	`TRX`
Stellar	`STELLAR`	`XLM`
Near	`NEAR`	`NEAR`
Cosmos	`COSMOS`	`ATOM_COS`
Algorand	`ALGORAND`	`ALGO`
Tezos	`TEZOS`	`XTZ`
TON	`TON`	`TON`
Ethereum Classic	`ETHEREUMCLASSIC`	`ETC`
Sui	`SUI`	`SUI`
Avalanche C-Chain	`AVALANCHE_C_CHAIN`	`AVAX`
Arbitrum	`ARBITRUM`	`ETH-AETH`
Base	`BASE`	`BASECHAIN_ETH`
BSC	`BSC`	`BNB_BSC`
Celo	`CELO`	`CELO`
Cronos	`CRONOS`	`CRONOS`
Hyperliquid (HyperEVM)	`HYPERLIQUID`	`HYPE_ETH`
Optimism	`OPTIMISM`	`ETH-OPT`
Polygon PoS	`POLYGON_POS`	`MATIC_POLYGON`
Sei	`SEI`	`SEI`

Testnet variants of these chains are also supported, for example ETH_TEST5 and BTC_TEST.

Limitations

Proof of address uses the default address of the vault account. For BTC and BTC_TEST, you can prove a derived address of the vault account with address. For other assets, other deposit addresses cannot be verified.
Only addresses that already exist in the vault account can be proven. You cannot set a custom derivation path.
TRUST has no screening policy; it covers proof of address only.
TRUST is an external network, not operated by Fireblocks.

On the Help Center

For how TRUST proof of address works, see TRUST.

Get Started

Transactions

API Co-Signers

Webhooks

Workspace & Security

Identity & Compliance

Manage Wallets

Smart Contracts & Tokenization

Treasury & Trading

Gas Management

Payments

Embedded Wallets

Offchain Signing

Direct Custody Wallets

Integrations

Assets & NFTs

Canton

Key Link

What you can do through the API

Step 1: Set up the Fireblocks SDK

Step 2: Get a UUID from TRUST

Step 3: Create the proof of address

Prove a derived address (UTXO-based assets)

Step 4: Retrieve the signature and submit it to TRUST

Supported blockchains

Limitations

On the Help Center

​What you can do through the API

​Step 1: Set up the Fireblocks SDK

​Step 2: Get a UUID from TRUST

​Step 3: Create the proof of address

​Prove a derived address (UTXO-based assets)

​Step 4: Retrieve the signature and submit it to TRUST

​Supported blockchains

​Limitations

​On the Help Center

What you can do through the API

Step 1: Set up the Fireblocks SDK

Step 2: Get a UUID from TRUST

Step 3: Create the proof of address

Prove a derived address (UTXO-based assets)

Step 4: Retrieve the signature and submit it to TRUST

Supported blockchains

Limitations

On the Help Center