What Is Fireblocks?

Fireblocks is designed primarily for institutions, developers, exchanges, banks, fintech companies, and Web3 businesses that need controlled digital asset operations across multiple regions. It is not simply a consumer wallet: the platform combines wallet infrastructure, transaction approvals, account management, and connections to external venues and apps.

The main security model separates key material, approval rules, and transaction connectivity. This helps organizations reduce risks from compromised credentials, incorrect addresses, insider collusion, and operational mistakes, although no custody or software platform eliminates all security, availability, or counterparty risks.

Key Takeaways

• Fireblocks is an institutional platform for securing, managing, moving, and issuing digital assets, rather than a basic retail wallet.
• MPC-CMP, Secure Enclaves, the Policy Engine, and the Fireblocks Network address different parts of the transaction-security workflow.
• Wallet type, user role, admin quorum, and Transaction Authorization Policy determine how transactions are approved and controlled.
• Fireblocks supports wallet infrastructure, tokenization, treasury operations, and connectivity, but service availability and risk controls depend on the organization’s configuration and terms.

What is Fireblocks?

Source: Fireblocks official website

Fireblocks is a platform for digital asset security, the development of decentralized products, and user asset management. Its services support institutions, developers, and applications that use digital assets across multiple regions. It combines MPC cryptography, hardware isolation, policy controls, and connectivity tools to reduce exposure to internal fraud, cyber attacks, and human error.

It achieves this through digital asset custody, a form of self-custody comprising multiple security layers and designed to reduce counterparty risk. The direct custody model is based on five fundamental principles regarding custody and risk:

• Create an environment with zero counterparty risk.
• Protect against internal and external attacks.
• Ensure continuity of business operations.
• Facilitate tight control and visibility of all transactions.
• Always deliver user-friendly, high-performance products and services.

History of Fireblocks

Source: Fireblocks official website

The Fireblocks project was built by Michael Shaulov, Pavel Berengoltz, and Idan Ofrat after they worked together on a task force investigating the 2017 hack of four South Korean exchanges attributed to the Lazarus Group. Their investigation highlighted how digital assets required security controls designed for programmable, internet-connected financial systems.

The three founders had more than twenty years of combined cybersecurity experience, including work in mobility and other critical infrastructure, before extending their expertise to the blockchain industry. They then created Fireblocks to protect digital assets with MPC technology.

How Does Fireblocks Work?

Source: Fireblocks official website

To support digital asset security, Fireblocks uses a multi-layer system consisting of MPC-CMP, Secure Enclaves, the Policy Engine, and the Fireblocks Network. Each layer addresses a different part of the workflow, from protecting signing material to enforcing approval rules and reducing address errors.

The platform establishes a secure environment for storing, transferring, and issuing digital assets. It is designed to protect these assets from a range of cyber threats, human errors, and potential internal collusion.

The first security layer is MPC-CMP, which uses multi-party computation (MPC). MPC divides sensitive signing information into shares held by multiple parties or environments. A transaction can be authorized only when the required shares participate in the signing process, so a complete private key does not need to be assembled in one location.

Fireblocks uses MPC because it can work with existing blockchain signature schemes without changing the underlying networks. The approach is flexible, and signing is performed off-chain before the resulting transaction is broadcast.

Fireblocks utilizes this technology through the MPC-CMP layer, which enhances the ECDSA and EdDSA signatures commonly used across all blockchains. This approach creates a new level of private key security, ensuring that the private key is never gathered into a single unit, effectively stopping hackers from accessing users’ assets.

The MPC-CMP layer not only enhances security but is described by Fireblocks as eight times faster than traditional MPC in its signing design because it requires fewer transaction rounds. This is a platform claim about a specific implementation, not a guarantee for every transaction or deployment. The layer is also compatible with cold-wallet workflows, where key shares remain offline.

Furthermore, the platform introduces an additional layer of security by distributing cryptographic MPC shares across multiple tier-one cloud environments, reducing the risk of breaches even if one of the physical data centers is compromised.

The second layer is the Secure Enclave, implemented using Intel SGX, a hardware-level environment designed to protect specific code and data. It helps safeguard the underlying infrastructure and cryptographic algorithms, including MPC and zero-knowledge proofs, while limiting access to sensitive software components.

Since the MPC key shares are stored in the SGX, they cannot be accessed by malicious parties who gain control over the server. This is because the memory space and the data stored in the SGX Enclave are encrypted.

The third layer of security is the Policy Engine. This allows users to create certain rules that dictate how transactions are approved and executed. A rule can decide whether or not a transaction is blocked or approved. It can also determine if extra signers are required by applying filters like source, destination, asset, and amount.

The Policy Engine is also protected by the SGX, while the Fireblocks platform spreads out the process of policy verification across various MPC servers. Policy rules created are signed by a team of admins and are encrypted within the SGX. After completing the process, the engine is integrated within the SGX enclave, which safeguards it from tampering by both hackers and employees, ensuring the integrity of the implemented rules and the Policy Engine’s logic.

The platform’s final layer is the Fireblocks Network, which enables users to transfer assets while reducing the risks associated with manually sharing deposit addresses. It uses address authentication and rotation workflows, including test transfers and whitelisting procedures, rather than treating a copied address as sufficient verification.

The network helps reduce losses caused by deposit spoofing and human errors, such as sending assets to an address associated with a counterparty that is no longer part of the intended transaction.

Features and Services of Fireblocks

Fireblocks combines custody, wallet management, transaction policy, tokenization, and connectivity services in one digital asset platform. Its applications can support exchanges, banks, fintech companies, Web3 businesses, and developers operating across different regions. Common uses include securing assets, approving transactions, connecting counterparties, and building blockchain applications and apps.

Aside from its security layers, Fireblocks also has features and services that help users manage applications, apps, wallets, and transactions across regions. These features include:

Hot, Warm, and Cold MPC-CMP Wallets

Fireblocks has three types of wallets: hot wallets, cold wallets, and warm wallets. These wallets are separated by where the third MPC share is placed and the process used for transaction approvals. In the case of the hot wallet, the third MPC key is managed by an API co-signer, allowing for automated transaction approvals.

With a cold wallet, the third MPC key share is held on the user’s offline device, and transaction approvals require scanning a QR code from both ends. With the warm wallet, the third MPC key share is placed on the online device, and transaction approval is received on the Fireblocks mobile app.

Workspaces

Fireblocks offers a distinctive feature known as Workspace, enabling users to manage various accounts and digital assets while keeping track of their transactions. Each workspace operates on a separate BIP32-HD wallet structure, each with its unique security measures and transaction policies.

There are three types of workspaces, each with its own capabilities and operating boundaries:

• Mainnet Workspace: Supports real-world digital asset operations, including transfers, vault accounts, address whitelisting, exchange connections, and MPC-CMP device configuration.
• Testnet Workspace: Provides a testing environment for integrations and trial operations without using production assets. Its features and fee behavior may differ from mainnet.
• Developer Sandbox: Provides a development and experimentation environment where developers can create APIs and generate the certificate materials needed for testing.

Role-based Access Control

Fireblocks has a role-based access control feature that grants users certain permissions based on their roles. Based on their roles, users can gain access to parts of the platform, the types of actions they can perform, and the MPC key shares that they hold to sign transactions.

Admin Quorum

Fireblocks Admin Quorum is the lowest gathering of workspace admins required to approve certain workspace decisions. They can decide on approving network connections, adding new users or removing malicious ones, and, lastly, adding whitelisted addresses.

Admin Quorum can reduce the risk of a single administrator approving a sensitive action, but it does not remove the need for role separation, secure devices, and independent review.

Accounts

The accounts feature is made up of the three types of accounts Fireblocks has to offer:

• Vault Account: An on-chain wallet for storing and transferring digital assets. It is protected by Fireblocks’ MPC-CMP architecture.
• Exchange Account: An account that uses exchange API credentials to transfer assets between exchanges and other Fireblocks accounts.
• Fiat Account: An account for transferring fiat currency within a Fireblocks workspace and through supported network connections.

Vaults

The Fireblocks Vault is the platform’s solution for managing wallets and addresses. With it, users can effortlessly create and oversee multiple vault accounts, each consisting of various asset wallets.

Asset Wallets

Asset wallets are specialized wallets designed to manage internal deposits linked to various asset types. Each asset wallet includes at least one deposit address specific to its type of asset. This service supports over 1,200 different assets.

Transaction Authorization Policy (TAP)

The Transaction Authorization Policy (TAP) serves as a framework of rules that define the boundaries for transactions within a user’s Fireblocks workspace. With TAP, users can manage various aspects of transactions, including who is permitted to execute them, the maximum transfer amount allowed at any one time, the timeframe during which transactions can occur, and the methods by which each transaction is authorized.

Additionally, these rules can be applied to transactions involving smart contracts, such as deploying, upgrading, or executing ongoing operations.

Use Cases of Fireblocks: Wallet-as-a-Service, Self-Custody Infrastructure, Tokenization, and Treasury Management

Fireblocks is used by organizations that need secure digital asset operations rather than a simple consumer wallet. Its services can help teams create applications, manage accounts, approve transactions, and coordinate asset movement across regions. The primary use case depends on whether an organization needs custody, payments, tokenization, trading connectivity, or treasury controls.

Fireblocks has several features that help the platform provide services for users and developers. By making use of these features, developers can build different applications and apps for users, while organizations can manage transactions across regions. Fireblocks can be used to create the following:

Wallet-as-a-Service

With Wallet-as-a-Service, developers can easily create and integrate tailored, secure wallets into their applications and apps. This API-driven solution offers robust MPC wallets, allowing developers to effectively create, manage, and secure wallets for countless users without the need to develop their own security infrastructure.

Self-Custody Infrastructure

Fireblocks’ Self-Custody Infrastructure provides API access, MPC controls, multiple security layers, and Intel SGX-based protections for organizations managing their own digital asset operations. The term self-custody does not remove operational, software, regulatory, or key-management risks.

Tokenization

Fireblocks provides tools for asset tokenization and blockchain-based application development. Its API supports tasks such as creating, managing, redeeming, and issuing tokens, including stablecoins and security tokens.

Developers can use the tokenization feature to tokenize any asset, mint new tokens, manage smart contracts, execute smart contract functions, secure custody of tokens, and much more.

Treasury Management

Treasury Management allows users to store their funds securely in hot and cold wallets, connect to exchanges, manage fund operations, and connect to trading counterparties. It gives users complete control over their assets across several wallets, allowing them to manage transaction risks and liquidity.

With Fireblocks Treasury, teams can make controlled transfers, move assets between approved venues, set governance rules, and protect fund operations.

Summary

Fireblocks is an institutional digital asset operations platform that combines MPC-CMP, Secure Enclaves, policy controls, custody workflows, tokenization, and network connectivity. These layers can reduce selected security and operational risks, but they do not eliminate the possibility of compromised accounts, incorrect configuration, service outages, or irreversible transfer errors. Its practical role depends on the organization’s products, policies, integrations, and regional requirements.

FAQ

Is Fireblocks a crypto exchange?

Fireblocks is primarily digital asset infrastructure and security software for institutions, developers, and businesses. It can connect organizations to exchanges and other counterparties, but it is not itself a general-purpose retail exchange.

How does Fireblocks protect private keys?

Fireblocks uses MPC-CMP to split signing authority across multiple key shares so that a complete private key is not assembled in one place during normal signing. Secure Enclaves and access policies add hardware and authorization controls, but device, account, configuration, and insider risks still require independent controls.

What is the Fireblocks Network used for?

The Fireblocks Network supports connections and transfers between participating organizations while helping authenticate deposit addresses and counterparties. The exact participants, supported assets, and workflows depend on the relevant service configuration.

What are Fireblocks wallets?

Fireblocks supports hot, warm, and cold MPC-CMP wallet workflows. They differ mainly in where the third key share is held and how transaction approval is completed. The appropriate setup depends on automation needs, signing procedures, and operational risk tolerance.

Who uses Fireblocks?

Common users include exchanges, banks, fintech companies, Web3 businesses, asset managers, developers, and other organizations that need digital asset custody workflows, payments, tokenization, treasury controls, or blockchain connectivity.