FAQ

Can Fireblocks and The Vault run side by side?

Yes, and this is recommended. The adapter and Fireblocks are independent endpoints. Most customers keep Fireblocks in read-only mode for several weeks after the last tranche.

Do we have to rotate our published deposit addresses?

In most cases, yes. Rotation is manageable when done in tranches while the old addresses are still monitored. If a specific counterparty cannot update its addresses, discuss a managed key import for that one wallet with your account manager.

What happens to transactions in flight at cutover?

Let them complete on Fireblocks. The adapter only sees transactions created through it, so there is no overlap.

Do policies apply to transactions submitted through the adapter?

Yes. A transaction request received by the adapter becomes a governed transfer, evaluated against your policies and approved by your approvers in the same way as a transfer initiated from the console.

Which vault accounts can the adapter access?

Only those in the wallet groups assigned to the linked API identity. A key with no wallet groups can neither see wallets nor initiate transfers.

Can we rotate the API key without reconfiguring the adapter?

Yes. The adapter configuration is bound to the API identity, not to a specific key.

What happens if our webhook endpoint is unavailable?

Deliveries go through a persistent outbox with retries. The Recent deliveries table shows each attempt, its status and the last error.

Can we leave The Vault later?

The same rule applies in both directions. There is no one-click key export; leaving The Vault works as described in this section — a governed asset transfer to the destination system, with a managed key procedure where unavoidable. Your exit plan under DORA and MiCA can reference this section.