Overview
Welcome to the Fireblocks glossary! We recommend familiarizing yourself with the following terms, as they are used throughout the platform and documentation.
A
Accounts page
The Accounts page is your default home page in the Fireblocks Console. It's where you can view and manage your workspace's vault accounts, connected exchange accounts, and fiat accounts, along with aggregate balances across all of them.
Admin role
An Admin has full signer permissions, can manage workspace settings and users, approve whitelisted addresses, and expand Fireblocks Network connections. Admins are also key approvers for actions that require an Admin Quorum. There are three Admin-level roles: Owner, Admin, and Non-signing Admin.
Admin Quorum
An Admin Quorum is a defined threshold of Admin-level users required to approve certain workspace actions, such as whitelisting a deposit address or adding a Fireblocks Network connection. For example, a workspace with six Admins might require a quorum of three to approve a given action. Your Owner must approve any changes to the Admin Quorum configuration. Learn more about Admin Quorums.
AML integrations
Fireblocks integrates with Chainalysis and Elliptic for automated anti-money laundering (AML) transaction screening. You can also manage AML compliance through the API using your own logic. Learn more about AML on Fireblocks.
Amount caps for approve transactions
A security feature that lets you set maximum values on transaction approvals for DeFi smart contracts. This addresses a known risk with ERC-20 token transfers, where pre-approving a contract can otherwise allow it to withdraw any amount from your connected wallet. Learn more about amount caps.
API Co-signer
The API Co-signer is a software component that holds an MPC key share and a Configuration Change Key, enabling automated transaction signing and approvals without manual intervention. It can be deployed in a cloud environment or on-premises, and supports a callback handler for custom approval logic. Learn more about the API Co-signer on our Developer Portal.
API idempotency
Idempotency allows you to safely retry API requests without the risk of processing them twice. Fireblocks supports idempotent requests through the API gateway, helping you avoid double-spending, replay attacks, and other transaction errors.
Approval groups
An approval group is a defined set of workspace users, with a threshold specifying how many must approve a given action. Unlike Admin Quorums, approval groups can include non-Admin roles. Setting up or changing an approval group requires approval from your Owner and Admin Quorum. Learn more about approval groups.
Asset wallet
An asset wallet holds a specific digital asset within a vault account. Each vault account can contain multiple asset wallets but only one per supported asset. Fireblocks automatically creates a base asset wallet when you add a token wallet that runs on that base network (for example, adding a USDC wallet automatically creates an ETH wallet if one doesn't already exist). Asset wallets can be base asset wallets (for native blockchain assets) or token asset wallets (for tokens built on top of a base network).
Assets page
The Assets page in the Console shows how a specific token or fiat currency is distributed across your vaults and connected accounts, along with the total value for each asset across all venues.
Audit log
The audit log is a record of workspace events, including logins, transactions, address whitelisting, user management changes, policy updates, and Fireblocks Network activity. Admins and Owners can access, filter, and export the audit log from the Console, and can configure push notifications for specific events through the Notification Center. Learn more about the audit log.
Automated Address Authentication
Automated Address Authentication (AAA) is a Fireblocks Network feature that automatically verifies deposit addresses between Network members, eliminating the need for manual whitelisting or test transfers when transacting with connected counterparties.
Automatic Address Rotation
Automatic Address Rotation is a Fireblocks Network feature that generates a new deposit address for every transfer between Network members on UTXO-based blockchains. This preserves transaction-level privacy by preventing multiple transfers from being linked to a single address.
Automated ERC-20 listing
Automated ERC-20 listing automatically adds support for unlisted ERC-20 tokens when you initiate a contract call for that token through a DeFi app. This is an opt-in feature.
B
Backup and recovery
Backing up your workspace keys is a mandatory step during onboarding and a requirement under your Fireblocks license agreement. It ensures you can recover access to your assets even if all key shares are lost. There are two approaches:
- Managed by your company: You manage your Workspace Keys Backup, Key Share Backup, or both internally.
- Managed by a third-party Disaster Recovery Service (DRS): You use a Fireblocks partner (CoinCover or Station70) to handle backup and recovery on your behalf.
You can test your recovery process in a dedicated backup simulation workspace, which is a non-production environment available on request. Learn more about backup and recovery.
Blockchain integrations
Fireblocks supports 150+ blockchains, spanning the leading Layer 1 and Layer 2 networks by market cap and DeFi total value locked (TVL). Integration depth varies by blockchain: some support basic custody and transfers for native assets, while others include deeper capabilities such as DeFi access, staking, and token support. View all supported blockchains.
C
Callback handler
A callback handler is a component of the API Co-signer that receives approval or rejection requests and returns a response based on your custom logic. It acts as an integration point between the Co-signer and your internal systems, enabling use cases such as policy verification, KYC checks, transaction validation, and velocity controls. Learn more about the callback handler on our Developer Portal.
Communal test co-signer
A shared Co-signer available in testnet environments for adding and testing new API users, without needing to configure a dedicated API Co-signer for each one. Not for use in production. Learn more about the API Co-signer on our Developer Portal.
Connected accounts
Connected accounts is a tab on the Accounts page in the Fireblocks Console. It displays the exchange accounts and subaccounts you have connected to your workspace, along with their balances. Connected accounts are distinct from vault accounts: they represent your existing accounts at third-party exchanges rather than wallets managed directly by Fireblocks.
Contract Call Decoding
Contract Call Decoding (also called contextualization) lets you view a human-readable summary of a smart contract interaction before it is confirmed on-chain. Fireblocks maintains a database of smart contracts and their Application Binary Interfaces (ABIs), which define how to interact with each contract. This lets Fireblocks decode and display the intent of a contract call during the approval process, giving approvers better visibility into what they're signing. Learn more about Contract Call Decoding.
D
DeFi (decentralized finance)
Decentralized finance (DeFi) refers to financial applications and protocols built on public blockchains that operate without centralized intermediaries. DeFi applications (such as decentralized exchanges, lending protocols, and liquidity pools) are governed by smart contracts rather than institutions. Fireblocks provides secure access to DeFi through the Console and API.
DeFi / Web3 gateways
Fireblocks provides three ways to connect to Web3 and DeFi applications: WalletConnect native integration, the Fireblocks Chrome Extension, and the Smart Contract (DeFi) API. Each method suits different workflows: Console-based access, browser-based dApp interaction, and programmatic access respectively.
Deposit Control and Confirmation Policy
The Deposit Control and Confirmation Policy lets you define how many on-chain confirmations are required before an incoming transaction is credited to your available balance. Once the threshold is met, the transaction clears and its outputs become spendable. This is particularly relevant for UTXO-based blockchains, where outputs must be confirmed before they can be used in subsequent transactions. Learn more about the Deposit Control and Confirmation Policy.
Digital assets
Digital assets are digital representations of value recorded on a blockchain, including cryptocurrencies, stablecoins, tokenized securities, and other blockchain-based instruments. They can be owned, transferred, and managed using cryptographic systems that verify ownership and transaction authenticity without relying on a central authority.
Disaster recovery
Disaster recovery (DR) is a mandatory part of Fireblocks onboarding and a requirement under your license agreement. It ensures you can recover access to your assets even if all key shares are lost or all signing devices become unavailable. There are two approaches:
- Managed by your company: You handle Workspace Keys Backup, Key Share Backup, or both internally.
- Managed by a Disaster Recovery Service (DRS): You use a Fireblocks DRS partner (CoinCover or Station70) to manage backup and recovery on your behalf.
You must complete your DR setup before using Fireblocks in production. Learn more about disaster recovery.
E
Embedded wallets
Embedded wallets are white-labeled wallet experiences you can build into your own consumer or retail applications using Fireblocks infrastructure. They allow you to offer your end users a seamless, branded wallet experience while Fireblocks handles the underlying security and key management. Learn more about Embedded Wallets.
Emergency workspace freeze
The emergency workspace freeze lets Owners and Admins immediately block all outbound activity in a workspace. Once frozen, incoming transfers are still received, but users cannot send transfers, whitelist addresses, add Fireblocks Network connections, or set up new exchange or fiat account connections. Use this feature if you suspect a security incident or unauthorized access. Learn more about the emergency workspace freeze.
Exchange accounts
Exchange accounts are connected accounts that appear under the Connected accounts tab in the Fireblocks Console. They represent your existing accounts at integrated third-party exchanges, linked to your workspace through exchange APIs. There are three types:
- Main accounts: Your primary account for each connected exchange. Only main accounts can deposit to or withdraw from your Fireblocks vault.
- Subaccounts: Additional accounts at some exchanges that let you segregate teams or strategies. Funds must be moved to the main account before withdrawing to your vault.
- Trading accounts: Spot, margin, futures, and options accounts available at select exchanges. Transfers are limited to their associated main account.
Learn more about exchange connectivity.
External unmanaged wallets
External unmanaged wallets are whitelisted addresses belonging to external counterparties: wallets outside your Fireblocks workspace that you don't control. Unlike internal unmanaged wallets, external unmanaged wallets do not display live balances and are not counted toward Fireblocks Address Package pricing. They can be accessed via the Console or API. Learn more about whitelisted addresses.
F
Fiat accounts
Fiat accounts let you connect crypto-friendly bank accounts to your Fireblocks workspace for fiat transfers and settlement. They appear under the Fiat tab on the Accounts page in the Console, separate from your vault accounts and connected exchange accounts. Learn more about fiat accounts.
Fireblocks Chrome Extension
The Fireblocks Chrome Extension lets you connect to Web3 applications (dApps) directly from your browser using your Fireblocks workspace. Web3 apps recognize the extension as a MetaMask-compatible wallet, but all signing and approvals are handled through Fireblocks' secure infrastructure. Learn more about the Fireblocks Chrome Extension.
Fireblocks Console
The Fireblocks Console is a web-based interface for managing your workspace. From the Console, you can view balances, manage vault accounts and asset wallets, initiate and monitor transactions, configure policies, manage users, and connect to exchanges, fiat providers, and the Fireblocks Network, all from one place.
The Console is intended for your team's internal operations, not for your end clients. If you're building a customer-facing product, use the Fireblocks API to integrate wallet infrastructure into your own application.
Fireblocks Gas Station
The Fireblocks Gas Station automates gas fee replenishment for EVM-based networks such as Ethereum. Rather than manually monitoring and topping up vault accounts to cover transaction fees, the Gas Station handles this automatically based on thresholds you configure. You can also set caps to prevent overfilling or transferring when gas prices are high. Learn more about the Fireblocks Gas Station.
Fireblocks Mobile app
The Fireblocks Mobile app is the companion to your workspace for transaction signing and approvals. Users with signing roles use it to sign transactions and connect to DeFi apps via WalletConnect. Admins and Owners use it to approve user and policy changes initiated in the Console or API. The app is available for Android and iOS. Learn more about the Fireblocks Mobile app.
Fireblocks MPC-BAM
MPC-BAM is a 2/2 signing protocol in the Fireblocks Fast MPC product family, designed for API Co-signer workflows that require high-throughput or low-latency transaction signing. It delivers signing speeds up to 10 times faster than MPC-CMP by reducing the cryptographic signing process to two rounds. MPC-BAM is an opt-in feature configured per API user and supports ECDSA SECP256K1 only; chains using EdDSA (such as Solana and Cardano) continue to use MPC-CMP. If MPC-BAM encounters any issues, the system automatically falls back to MPC-CMP with no manual intervention required. Mobile co-signers are not supported. Learn more about MPC-BAM.
Fireblocks MPC-CMP
Multi-Party Computation (MPC) is the cryptographic foundation of Fireblocks' wallet security. Rather than storing a single private key that could be stolen or lost, Fireblocks uses MPC to split cryptographic key shares across multiple devices and secure hardware environments, so no single party ever holds a complete key. MPC-CMP is the Fireblocks implementation of this protocol, developed by Fireblocks R&D and optimized for performance and scalability across all signing device types. Learn more about Fireblocks' security model.
Fireblocks Network
The Fireblocks Network is a settlement network connecting thousands of institutional counterparties, including exchanges, liquidity providers, banks, payment companies, and fintechs. Network connections eliminate the need to manually manage deposit addresses for recurring transfers, replacing them with Automated Address Authentication and Automatic Address Rotation. The Network also supports payments, on- and off-ramp providers, and stablecoin settlement flows. Learn more about the Fireblocks Network.
Fireblocks Network channels
A Network channel is a named grouping within your workspace for organizing Fireblocks Network connections. You can create channels to separate connections by activity type, such as lending, payments, or trading. Each workspace includes a default channel named after the workspace, with a corresponding vault called "Network deposits."
Fireblocks Network connections
A Network connection is an established link between your workspace and another Fireblocks Network member. Transfers with Network connections benefit from Automated Address Authentication and Automatic Address Rotation, removing the need to manage deposit addresses manually for recurring counterparties.
Fireblocks Network members
Fireblocks Network members are Fireblocks customers who have joined the Fireblocks Network. Any member can connect with other members to become a counterparty, enabling authenticated transfers without manual address management.
Fireblocks Permissioned DeFi
Fireblocks Permissioned DeFi allows verified institutions to participate in DeFi liquidity pools where all participants have completed KYC. This enables firms to access DeFi yields and liquidity while remaining within a compliant, known-counterparty environment. Learn more about Permissioned DeFi.
Fireblocks REST API
The Fireblocks REST API provides programmatic access to your workspace, enabling you to create and manage transactions, query balances, configure vault accounts and asset wallets, manage users, and integrate Fireblocks capabilities into your own applications and workflows. SDKs are available for TypeScript, Python, and Java. Explore the Fireblocks API.
Fireblocks Self (direct) custody
Fireblocks is a direct custody platform, meaning you retain full ownership and control of your private keys and assets at all times. Unlike traditional custodians, Fireblocks never takes possession of your complete private keys: key shares are split using MPC-CMP and distributed across your devices and Fireblocks-secured hardware, so no single party can access your assets unilaterally. Learn more about Fireblocks' custody principles.
Fireblocks Staking
Fireblocks Staking lets you earn rewards on supported proof-of-stake protocols directly from your vault through integrations with third-party staking partners. Learn more about staking on Fireblocks.
Fireblocks Tokenization Engine
The Fireblocks Tokenization Engine lets you mint, issue, and manage tokenized assets, including stablecoins, security tokens, and real-world assets, using Fireblocks' smart contract infrastructure. It integrates with Tokeny for permissioned token issuance and end-to-end tokenization workflows. Learn more about tokenization on Fireblocks.
Fireblocks Vault
The Fireblocks Vault is your secure solution for wallet and address management. Fireblocks lets you create and manage multiple vault accounts, each of which contains your asset wallets. In MPC workspaces, wallet addresses are derived for each vault account and asset wallet using HD derivation (BIP44), with the underlying keys protected by Fireblocks MPC technology. In KeyLink workspaces, vault accounts are linked to keys that you manage externally in your own HSM or KMS. Learn more about the Fireblocks Vault.
Fireblocks workspace
A Fireblocks workspace is your organization's private environment within the Fireblocks platform. It contains your vault, connected accounts, users, policies, and configuration, all built on a unique BIP32 hierarchical deterministic (HD) wallet structure with its own cryptographic keys. Workspaces come in three types: sandbox, testnet, and mainnet (production). Learn more about workspace environments.
H
Hierarchical deterministic (HD) wallets
A hierarchical deterministic (HD) wallet generates and manages a tree of public and private key pairs from a single seed. Fireblocks uses BIP32-compatible HD wallets as the foundation of the Fireblocks Vault, enabling scalable address management across multiple vault accounts and asset wallets without requiring separate key management for each one.
Hot, warm, and cold wallet configurations
Fireblocks supports three wallet configurations that determine how signing components are stored and how transactions are initiated and signed:
- Hot: All key shares are online and connected to the internet. Transactions are created and signed automatically via API Co-signer, with no manual intervention required.
- Warm: Signing is automated via API Co-signer, but transactions require manual approval from a human approver before the Co-signer signs.
- Cold: Key shares are kept offline. Transactions require manual initiation and signing, providing the highest level of security for assets that don't need frequent movement.
Your wallet configuration is determined by how you set up your API Co-signer and policy rules. Many workspaces use a combination of configurations across different vault accounts depending on operational needs.
I
Intel SGX security layer
Intel Software Guard Extensions (SGX) is a hardware isolation technology that creates secure enclaves: protected memory regions inaccessible to any process outside the enclave, including the operating system. Fireblocks uses SGX to protect MPC key shares stored at its cloud data centers and to secure the Policy and Workflow Engine, preventing both external attackers and internal users from tampering with transaction policies or approvals. Learn more about Fireblocks' security model.
Internal unmanaged wallets
Internal unmanaged wallets are whitelisted addresses that belong to your own organization but exist outside your Fireblocks vault; for example, a wallet you manage on another platform. Unlike external unmanaged wallets, internal unmanaged wallets benefit from Fireblocks monitoring the blockchain and displaying their current balance. Their addresses count toward Fireblocks Address Package pricing. They can be accessed via the Console or API. Learn more about whitelisted addresses.
J
Java SDK
The Fireblocks Java SDK lets you integrate Fireblocks API functionality into Java-based applications. View the Java SDK on GitHub.
K
Key Share Backup and Recovery
Key Share Backup and Recovery is the disaster recovery process for the mobile MPC key share held by your workspace Owner. It is distinct from Workspace Keys Backup, which recovers the full extended private keys for your entire workspace. There are two recovery methods: device reset by Owner (requires access to another Admin or Signer's mobile device) and recovery by passphrase. Learn more about Key Share Backup and Recovery.
M
Managed wallets
Any wallet you create in your Fireblocks Vault is a managed wallet. The private keys are protected by MPC-CMP and all signing occurs through Fireblocks' secure infrastructure. Managed wallets are distinct from unmanaged wallets (whitelisted addresses for destinations outside your vault), which come in internal and external varieties.
Multi-layer security
Fireblocks' security model combines four layers of protection to secure assets during both storage and transfer. The first layer is MPC-CMP wallet infrastructure, which eliminates single points of failure by splitting private keys across multiple devices and secure environments. The second is Intel SGX hardware isolation, which protects key shares and policy configurations in tamper-resistant secure enclaves. The third is the Policy and Workflow Engine, which enforces transaction authorization rules and is itself secured by SGX to prevent tampering. The fourth is the Fireblocks Network, which replaces manual deposit address management with authenticated, encrypted transfers between verified counterparties. Learn more about Fireblocks' security model.
N
NFT SDK
The Fireblocks NFT SDK provides programmatic support for NFT lifecycle management, including transfer, mint, and burn operations for ERC-721, ERC-1155, and custom NFT standards. It is part of the Fireblocks DeFi SDK. View the NFT SDK on GitHub.
Notifications
Notifications let Admin-level users configure alerts for audit log events in their Fireblocks workspace. Alerts can be delivered via email, webhook, or public Slack channel, and are organized by event category, so enabling a category delivers notifications for all events within it. Notifications are typically used by security and compliance teams to monitor workspace activity. They are distinct from API webhooks, which are used for programmatic integration with Fireblocks. Learn more about notifications.
O
One-time address (OTA) transactions
A one-time address (OTA) transaction lets you transfer assets to a destination that has not been whitelisted in your workspace. OTA transfers are disabled by default and must be enabled by your workspace Owner. Because OTA destinations lack the identity metadata of whitelisted addresses, they are incompatible with Travel Rule compliance requirements. Use with caution and consider setting policy rules to govern OTA usage. Learn more about OTA transactions.
Owner role
The Owner is the root user of a Fireblocks workspace and the only role that can approve the initial Admin Quorum configuration, onboard new signing devices, and authorize certain sensitive workspace actions. Every workspace requires exactly one Owner. The Owner must use the Fireblocks Mobile app for signing and approvals.
For security purposes, the Owner role is assigned by Fireblocks Support and cannot be self-assigned. If the Owner wants to change their signing device, migrate to a new mobile device, or unfreeze the workspace, they must first verify their identity with Fireblocks Support via a short video call.
P
Policies
Policies define the rules that govern transaction authorization in your Fireblocks workspace. Each policy rule specifies who can initiate a transaction, what conditions it must meet (such as source, destination, asset, and amount), and what approvals are required before it can proceed. Together, your policy rules form a verification layer that enforces your organization's controls on every outbound transaction.
Policies are configured in the Policy and Workflow Engine and are secured by Intel SGX, preventing both external attackers and internal users from tampering with rules or approvals. Changes to your policies require Admin Quorum approval. Learn more about Policies.
Python SDK
The Fireblocks Python SDK lets you integrate Fireblocks API functionality into Python-based applications. View the Python SDK on GitHub.
R
Raw Signing API
The Raw Signing API provides access to blockchain protocols, transaction types, and DeFi applications that are not yet fully supported through the standard Fireblocks API. It lets you generate ECDSA and EdDSA signatures to sign any transaction type or message, and supports aggregating up to 127 messages for signing in a single operation. Raw signing uses the same security mechanisms as standard Fireblocks transactions, including MPC signing, key protection, and policy enforcement. Learn more about the Raw Signing API.
S
Smart Contract (DeFi) API
The Smart Contract (DeFi) API enables you to interact programmatically with smart contracts on EVM-compatible blockchains. Use it to initiate DeFi transactions, NFT transfers, and other contract operations not natively supported through the standard Fireblocks API. Learn more about the Smart Contract (DeFi) API.
Smart Contract (DeFi) SDK
The Smart Contract (DeFi) SDK provides an interoperability layer between the Smart Contract (DeFi) API and common DeFi libraries, simplifying programmatic interaction with DeFi protocols. It includes support for NFT lifecycle management, including transfer, mint, and burn, for ERC-721, ERC-1155, and custom NFT standards. View the DeFi SDK on GitHub.
Stablecoin
A stablecoin is a digital asset designed to maintain a stable value by pegging it to an external reference, most commonly a fiat currency such as the US dollar or euro, but also commodities or other assets. Unlike cryptocurrencies such as Bitcoin or Ethereum, stablecoins are designed to minimize price volatility, making them suitable for payments, settlements, and treasury operations that require predictable value.
There are three main types of stablecoins:
- Fiat-backed: Backed 1:1 by fiat currency reserves held by an issuer (for example, USDC, USDT).
- Commodity-backed: Backed by physical assets such as gold.
- Algorithmic: Maintain their peg through programmatic mechanisms rather than direct asset reserves.
Fireblocks supports the full stablecoin lifecycle, from custody and transfers to issuance, compliance, and settlement, across all major stablecoin types and the blockchains they run on.
Status page
The Fireblocks status page logs real-time and historical status updates for all Fireblocks systems. Visit status.fireblocks.com to check current system status or review past incidents.
Sweeping via API
Sweeping is the process of periodically consolidating funds from intermediary deposit accounts into a central omnibus vault account using the Fireblocks Create Transaction API. It is commonly used in segregated vault structures to aggregate balances efficiently. If you don't want to implement your own sweeping logic, the Fireblocks Gas Station can automate fee replenishment for EVM-based networks as part of this workflow. Learn more about the Fireblocks API.
T
TRES integrations
Tokenization
Tokenization is the process of representing ownership of a real-world or financial asset as a digital token on a blockchain. Tokenized assets can include fiat currencies (stablecoins), securities, commodities, real estate, and other instruments. Tokenization enables programmable ownership, automated compliance, and faster settlement compared to traditional asset management. Fireblocks supports tokenization through the Fireblocks Tokenization Engine and its integration with Tokeny. Learn more about tokenization on Fireblocks.
Travel Rule
The Travel Rule is a regulatory requirement originating from the Financial Action Task Force (FATF) that obligates virtual asset service providers (VASPs) to collect, verify, and transmit identifying information about the originators and beneficiaries of digital asset transfers above a defined threshold. The rule is designed to prevent money laundering and terrorist financing by ensuring that transaction parties can be identified across the transfer chain.
Fireblocks supports Travel Rule compliance through an integration with Notabene, enabling automated collection and transmission of the required counterparty data as part of your transaction workflow.
Typed Message Signing
Typed Message Signing lets you sign messages using specific standard formats (ETH_MESSAGE and EIP712) that prefix the message with a fixed string. This mitigates the risk of an attacker tricking a signer into signing a valid malicious transaction disguised as a message. Learn more about Typed Message Signing.
U
User roles
Fireblocks workspaces have nine user roles, each with a defined set of permissions. Roles follow a principle of least privilege: users should be granted only the access they need to perform their responsibilities. The nine roles are:
- Owner: The root user of the workspace. Approves the initial Admin Quorum, onboards signing devices, and authorizes sensitive workspace actions. Every workspace has exactly one Owner.
- Admin: Full signer permissions plus workspace management; can manage users, settings, whitelisted addresses, and Fireblocks Network connections. A key approver for Admin Quorum actions.
- Non-signing Admin: Same administrative permissions as Admin but cannot sign transactions.
- Signer: Can sign and approve transactions via the Fireblocks Mobile app. Cannot manage workspace settings or users.
- Approver: Can approve transactions but cannot sign them or manage workspace settings.
- Editor: Can create and manage vault accounts and asset wallets but cannot sign transactions or manage users.
- Viewer: Read-only access to workspace data. Cannot initiate or approve any actions.
- Security Auditor: Read-only access to everything in the Console, including Settings, Policies, and Fireblocks Security Posture Management (FSPM). Provides broader viewing access than the Viewer role. Intended for auditors and security personnel conducting compliance reviews.
- Security Admin: Manages platform security and operation configurations (including user lifecycles, IP allowlists, user groups, 2FA resets, and FSPM) without participating in business or value-transfer operations. Does not hold MPC keys and cannot initiate or sign transactions. Security Admins land on the Security Center page when logging into the Console.
UTXO Multiple Destinations
UTXO Multiple Destinations is an API feature that lets you specify multiple destination addresses in a single UTXO transaction using the destinations parameter. This maximizes efficiency and minimizes fees for UTXO-based blockchain transactions initiated via the API. Learn more about the Fireblocks API.
V
Vault account
A vault account is a unique wallet within the Fireblocks Vault, secured by MPC technology. Each vault account contains one or more asset wallets (one per supported asset) and has its own set of blockchain addresses. Vault accounts appear under the Vault tab on the Accounts page in the Console. You can create multiple vault accounts to reflect your operational structure, such as separating funds by client, team, or purpose.
W
WalletConnect
WalletConnect is an open protocol for connecting wallets to Web3 applications. Fireblocks offers a native WalletConnect integration in the Console, giving you access to hundreds of compatible DeFi, NFT, and GameFi applications, including apps on non-EVM blockchains such as Algorand, while keeping all signing and approvals within Fireblocks' secure infrastructure. Learn more about WalletConnect on Fireblocks.
Webhooks
Fireblocks webhooks provide real-time push notifications for workspace events, enabling you to build automated workflows and integrations without polling the API. Events include transaction status updates, incoming and outgoing transfers, vault and wallet changes, and more. Webhooks v2 is the current version and is documented on the Developer Portal. An earlier version exists but is not recommended for new integrations.
Fireblocks also supports audit event notifications via webhook. These are configured separately in the Console under Settings > Notifications and are intended for security and compliance monitoring rather than programmatic integration. Learn more about webhooks.
Whitelisted addresses
Whitelisted addresses are saved destinations in your workspace that have been approved for use in transactions. Whitelisting a destination associates it with an identity — a person, company, or contract — making it easier to reuse in policy rules and giving approvers clear context when reviewing transactions. There are three types:
- Internal wallets: Your own addresses outside the Fireblocks vault.
- External wallets: Your external counterparties' addresses.
- Contract wallets: Whitelisted smart contracts for Web3 applications.
Requests to whitelist external wallets and contract wallets require Admin Quorum approval. Fireblocks recommends whitelisting all transaction recipients rather than using one-time addresses (OTAs), both for security and Travel Rule compliance. Learn more about whitelisted addresses.
Workspace Keys Backup and Recovery
Workspace Keys Backup and Recovery is the disaster recovery process for your entire workspace. It allows you to reconstruct the full extended private key seed for your Fireblocks Vault using your workspace Owner's recovery passphrase, giving you complete access to your assets in a recovery scenario. It is distinct from Key Share Backup and Recovery, which covers only the Owner's mobile key share. Learn more about Workspace Keys Backup and Recovery.