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 your Fireblocks Console. It’s where you can view and access all of your workspace’s vaults, and see the value of assets in them. You can also see your aggregate balances across all vaults, exchanges, or fiat accounts.

Admin role

In your Fireblocks workspace, there are 3 Admin level user roles: Owner, Admin, and Non-signing Admin. An Admin has all signer role permissions, can expand the network, approve new whitelisted addresses, edit all workspace settings, add new workspace users, and manually confirm and credit inbound transactions by marking inbound transactions as complete. Certain core approvals can only be made by the Owner role, but other Admins are key approvers for rules requiring an Admin Quorum.

Admin Quorum

A specific threshold of how many Admin users must approve certain administrative actions or activities in your workspace. Setting up or changing your Admin Quorum must be approved by your Owner. For example, you may have 6 Admins, but only a Quorum of 3 is needed to approve a specific action such as whitelisting a deposit address or adding a Fireblocks Network connection.

Admin Quorum threshold

This is the number of Admin level approvers required to approve a specific workspace action. The threshold is defined by your Admin Quorum settings that your workspace Owner must approve.

AML integrations & DIY AML via API 

Fireblocks has integrations with two top digital asset Anti-Money Laundering (AML) software providers Chainalysis and Elliptic and also enables you to manage AML compliance yourself via API. These compliance-focused AML integrations and DIY AML capabilities enable you to automate transaction monitoring, freezing/unfreezing of flagged funds for your transactions, and more. 

Amount Caps for Approve Transactions  

A DeFi security feature that allows you to pre-set caps on the value of transactions for DeFi smart contracts in your Console. This solves a security risk from ERC-20 token transfers, which forces you to pre-approve for the contract to be able to withdraw any amount from the wallet you connect.

API Co-Signer

An alternative for approving transactions manually with the Fireblocks Mobile App, you can program automated software that approves or signs based on custom logic. Allows you to automate transaction signing, wallet approvals, and other approvals that are initiated via API. The API Co-Signer holds an MPC key share for your Fireblocks Vault and a Configuration Change Key for automated signing and approvals. It can be deployed in a cloud environment or on-prem. 

API idempotency

With Fireblocks API you can use idempotent requests to ensure a request will not be processed twice via the API Gateway, avoiding replay attacks, double-spending issues, or other transaction errors.

Approval groups

A specific threshold of how many users must approve certain or activities in your workspace. Setting up or changing approval groups must be approved by your Owner and Admin Quorum. For example, you may have 6 users in the approval group, but only 3 are needed to approve a specific action such as whitelisting a deposit address or adding a Fireblocks Network connection.

Assets page

The Assets page in your Console shows you how any specific token or fiat currency is distributed across different venues and vaults, and the total value for each asset across all venues and vaults.

Audit log  

Allows Admins to track, audit, and export workspace events like logins, address whitelisting, Fireblocks Network connections, adding/removing wallets, 3rd party connections (exchanges/fiat), vault creation, transactions (submitted, signed, approved, canceled, note changed, confirmation overwritten), policy updates, user management, and workspace updates. You can access your Audit log via the Fireblocks Console and you can set up push alerts using the Console’s Notification Center. 

Automated Address Authentication  

A feature of the Fireblocks Network. Network members can transfer faster, avoid manual errors and avoid hacks by eliminating manual whitelisting, test transfers, and copy and pasting of deposit addresses because transfers with Network connections have Automated Address Authentication. 

Automatic Address Rotation

A feature of the Fireblocks Network. Network members automatically generate a new deposit address for every transfer for UTXO-based tokens with a Network connection. This preserves your transaction-level privacy on the blockchain by not linking all transfers to one deposit address. 

Automated ERC-20 Listing   

A feature that allows you to automatically add 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 done by a third party

This is when you use a Disaster Recovery Service (DRS) for your Workspace Keys Backup, Key Share backup, or both.

Backup done by your company

This is when you manage Workspace Keys Backup, Key Share Backup, or both internally at your company. 

Backup simulation workspace

This is a special test workspace you can request in order to test your Workspace Keys Recovery process in a non-production environment.

Blockchain integrations  

You can use any of 40+ integrated blockchains using Fireblocks, spanning across the top Layer 1 and Layer 2 blockchains by market cap and DeFi TVL. Integrations with a blockchain can range from basic blockchain support allowing custody and transfer for a blockchain’s native asset to more robust integrations that include DeFi and staking support for a chain. 

C

Callback handler  

Part of API Co-Signer. Provides an approval or rejection response upon request for your API Co-Signer and acts as an integration point with customer core banking services to provide more information while processing transactions. Implementation Examples: Distributed Policy verification, KYC verification, Transaction verification, and Velocity control. More on API Co-Signer callback handler. 

Communal test co-signer

A co-signer designed to use only in testnet environments when adding new API users. Allows you to avoid configuring an API Co-signer for every user.

Fireblocks Console  

You can manage your workspace using the Fireblocks Console, a web-based application that allows you to access the Fireblocks platform and manage all your digital assets, transactions, third-party accounts, Fireblocks Network connections, Web3 activity, and more from one easy-to-use interface.

The Console UI is not intended to be offered to your end clients. Normally, you would want to develop or integrate a client-facing application using the Fireblocks API to abstract Fireblocks' wallet infrastructure and provide a better user experience and functionality to end clients.

Contract Call Decoding (Contextualization)  

A feature allowing you to better contextualize the content of contract calls (transactions on smart contract-based blockchains) that are executed on the Fireblocks platform. Fireblocks maintains a database of smart contracts and their Application Binary Interfaces (ABI), which defines the methods and structures used to interact with the contract. This lets us decode contract calls before they are mined on the blockchain, providing further insight into the transaction's context.

D

DeFi / Web3 gateways  

Three features that enable you to securely connect to Web3 applications (DeFi, NFT, GameFi, etc) through Fireblocks: WalletConnect native integration, Fireblocks Chrome Extension, and DeFi API.

Smart Contract (DeFi) API   

Feature enabling you to connect to Web3 applications programmatically via API. You can use Fireblocks DeFi API to initiate special transactions that interact directly with any smart contract that’s deployed on an EVM-compatible network. This allows you to run contract operations that are not natively supported on the Fireblocks API, such as DeFi transactions and NFT transfers.

Smart Contract (DeFi) SDK

Fireblocks Smart Smart Contract (DeFi) SDK provides an interoperability layer between Fireblocks DeFi (Smart Contract) API and common DeFi libraries. The DeFi SDK offers a simplified way to perform actions through the DeFi API with fewer engineering resources.

Deposit Control and Confirmation Policy  

A feature that allows you to set a custom confirmation policy that defines when funds are credited in your wallet during a transaction. Your Deposit Control & Confirmation Policy defines how many network confirmations are required before an incoming transaction can be cleared. When the transaction clears, it is accounted for in your “available balance” and its outputs (for UTXO blockchains) are spendable in your vault.

Disaster recovery (DR)

A mandatory feature that enables you to maintain access to your assets at all times, even if you lose access to all of your key shares. As the custodian of your assets held on Fireblocks, it is your duty to back up your cryptographic keys during your workspace onboarding and before using Fireblocks. You are also obligated to complete this step as part of your license agreement with Fireblocks. Your DR process can be set up by your company or you can use Fireblocks’ Coincover DRS integration.

DRS (Disaster Recovery Service) integration

Our recommended DRS provider is our partner Coincover. Learn more about DRS and Coincover's services here.

E

Emergency workspace freeze 

Allows Owners and Admins to block all user activity in a workspace. Once a workspace is frozen, transfers are still received in the workspace, but users are blocked from sending transfers, whitelisting addresses, setting up new fiat and exchange connections, adding Fireblocks Network peers, and more.

Exchange API

Fireblocks offers APIs for all your workspace operations. Using Fireblocks APIs, you can query the balance of your connected exchange accounts with a single API endpoint, acting as a unified layer across them. From there you can transfer from any connected exchange account to a vault, whitelisted address, Fireblocks Network counterparty, or other exchange account using one unified API transaction endpoint.

Exchange main accounts  

Your default account for Fireblocks integrated exchanges that you have connected to your workspace. Only your exchange main accounts can deposit to or withdraw from your Fireblocks Vault. 

Exchange sub-accounts  

Some integrated exchanges also let you connect directly to your exchange sub-accounts in your Console. You can use sub-accounts to segregate teams or accounts, and hedge risk. Funds can be transferred between exchange subaccounts but must be moved into your exchange main account in order to withdraw them from your Fireblocks Vault.

Exchange to exchange transfer

You can transfer funds directly between your integrated exchange main accounts. When transferring from one of your exchange wallets in your Fireblocks Console, you will see a menu where you can select from your other exchange wallets to execute a direct transfer.

Exchange trading accounts

Some Fireblocks integrated exchanges let you connect directly to your exchange trading accounts. You gain visibility to spot, margin, futures, and options accounts and can rebalance between them. Transfers can only be sent between exchange trading accounts and their associated main accounts.

External unmanaged wallets

Your Whitelisting new addresses on Fireblocks can also be classified as unmanaged wallets. Your external whitelisted address wallets do not show their balances and are not counted as part of Fireblocks Address Package pricing. External unmanaged wallets can be accessed via API or in your Console.

F

Fiat integrations

Fireblocks’ integrations with crypto-friendly banks like Signature and BLINC. Allows you to connect fiat accounts to your workspace and easily transfer or settle with fiat if your counterparty also has a Signature SEN or BLINC BCB account.

Fiat account

Enables you to transfer fiat to any other account within your Fireblocks workspace or network connections that supports that also supports the same fiat provider. The supported fiat providers are Signature and BCB. 

Fireblocks Chrome Extension

Feature enabling you to connect to Web3 applications (dApps) through a Fireblocks-branded web extension. The Fireblocks Chrome Extension is designed to connect to Web3 apps through the same integration the apps use to connect to MetaMask. Web3 apps recognize our extension as a MetaMask wallet but actually connect to your Fireblocks workspace and secure wallet infrastructure.

Fireblocks fiat on & off ramps 

If you want to convert between USD and stablecoin or crypto through Fireblocks, you can do so through a Signature SEN fiat account, Coinbase, or Circle accounts. Send a wire transfer to Signature, Coinbase, or Circle. Then use Coinbase or Circle to convert to/from USDC. You can also withdraw USDC from your USD balance in your Coinbase account on Fireblocks. Read more from Coinbase.

Fireblocks Gas Station

A feature that automates gas replenishment for transaction fees on EVM-based networks like Ethereum and BSC. This frees you from monitoring and manually transferring funds to these vaults to pay for future fees to sweep funds out. You can also set caps to avoid overfilling or transferring when gas fees are high. 

Fireblocks MPC (MPC-CMP)

The primary layer of Fireblocks' multi-layer security. Your Fireblocks Vault uses MPC (multi-party computation signing. With MPC, wallet private keys, used to execute transactions, are split across multiple devices to eliminate single points of failure. MPC-CMP is an open,  free-to-use MPC protocol developed by Fireblocks R&D that pushes transaction signing up to 8X faster than legacy MPC.

For each signing device in your workspace, one key share is generated on the device and two corresponding shares are generated on separate Fireblocks secured SGX hardware. Each conducts a computation on its own unique share to collectively sign transactions without any one device knowing the details of all the key shares. The private key can only be determined if all shares are controlled.

Fireblocks Network

A feature available to all Fireblocks customers that allows them to discover liquidity, lending, and trading counterparties and transfer faster, with less risk with any Fireblocks Network connections:

• Find, connect with, and enable instant secure settlements with 1,800+ verified counterparties.
• Stores and manages digital assets and streamlines operations from one platform, connecting to trading venues, liquidity pools, and counterparties for instant settlement.
• With Fireblocks Network, transferring digital assets between two counterparties no longer requires managing deposit address vulnerabilities.
• Don't need to worry about whitelisting (one & done), deposit addresses, or address rotation.

Fireblocks Permissioned DeFi 

A feature that allows firms that pass KYC to participate in permissioned DeFi markets. Permissioned DeFi markets allow you to participate in DeFi liquidity pools with only known participants who have also passed KYC. Fireblocks’ LLC entity is a regulated money services business (MSB) and is authorized to KYC, conduct ongoing monitoring, and whitelist institutions for permissioned markets.

Fireblocks REST API 

Allows you to programmatically create transactions on the Fireblocks platform and view information regarding your vault and fiat accounts, connected wallets, exchanges, and Fireblocks Network connections.

Use our REST API to automate operations and remove human barriers, build digital asset management systems for your end clients, and create new workflows between Fireblocks features and systems and features outside of Fireblocks. We offer SDKs in Python and JavaScript. Learn more in the Fireblocks Dev Portal.

Fireblocks Policy and Workflow Engine 

Policy layer of Fireblocks’ multi-layer security. You can create and modify policies related to workspace configuration (address whitelisting, Fireblocks Network connections, and third-party exchange and fiat account connections) and transactions (TAP) with maximum flexibility and customizability. Define Admin Quorums and rules across filters like initiator, source, destination, asset, and amount for compliance and control.

Fireblocks Staking 

A feature that enables you to accrue rewards on staking protocols like Ethereum 2.0, Tezos, Polkadot, Cardano, Kusama, and Solana through integrations with third-party staking partners. You can stake on each protocol except ETH2.0 directly from your Fireblocks Vault. You can stake ETH2.0 through Figment’s WalletConnect app and any protocol above via API with each partner.

Fireblocks Tokenization Engine 

A feature that enables you to mint, issue, distribute, and service investors for tokenized financial, fiat (stablecoins), and real-world assets using Fireblocks’ minting engine or integration with Tokeny for permissioned token issuance, smart contract creation, and advanced dashboards and servicing.

Fireblocks Transaction Authorization Policy (TAP) 

The transaction layer of the Fireblocks Policy and Workflow Engine. A set of rules you create that dictate the limits and boundaries of the movement of funds. With TAP, you control which users can move funds, how much can be transferred in a single transaction or per day, and how transactions are approved. The right TAP rules ensure no assets are moved anywhere without the required approvals.

Fireblocks Vault

Your secure MPC-CMP solution for wallet and address management. The Vault allows you to create and manage multiple vault accounts, which contain your asset wallets. Depending on the asset type, you may or may not be able to have multiple deposit addresses or accounts within a single vault account. Learn more about the Fireblocks Vault.

Fireblocks vault account

A unique on-chain wallet on Fireblocks, with your private key secured by our MPC-CMP architecture, that enables you to securely store and transfer your digital assets.

Fireblocks workspaces

The Fireblocks workspace is a unique feature of the Fireblocks platform with a broad range of capabilities that allows you to manage your various accounts, digital assets, transactions, and more.

Each workspace is a unique BIP32-HD wallet structure with unique security and transaction policies.

Learn more about different types of Fireblocks workspace environments.

Fully automatic operation mode 

Your transactions are submitted through API, which will then be handed to the MPC signing process leveraging the API user and API Co-Signer server, thus requiring no human (manual) intervention. It is possible to automate the signing/approval process while integrating a custom Callback Handler providing custom logic for approval or denial of such requests

H

Fireblocks hierarchical deterministic (HD) wallets

Your Fireblocks Vault contains BIP32-compatible Hierarchical Deterministic (HD) wallets, a public/private key tree that enables the generation and management of public/private key pairs in multiple unique currencies. These keys (addresses) are off-chain and enable single signing, allowing you to avoid gas fees that multi-sig wallets can’t.

Fireblocks hot wallet configuration

Wallet setup using API Co-Signers where your signing components (key shares) of the wallet are fully “online,” meaning they are connected to the internet. Transactions can be created in an automated manner and signing is automated.

I

Fireblocks’ insurance policy 

Fireblocks is covered by an insurance $30M insurance policy that covers Technology Errors and Omissions and Professional Liability, Cyber Liability, Multimedia Liability, eCrime Loss, First Party Loss, and Breach Costs. For more about Fireblocks’ insurance policy or recommended customer specie insurance coverage from our insurance partners, contact your Customer Success Manager.

Fireblocks integrated exchanges

Exchanges that are integrated with Fireblocks through exchange APIs. For these exchanges, you can connect your exchange wallet in your Fireblocks Console and easily transfer funds to or from your exchange wallet to your vaults, other exchange accounts, or counterparties.

Internal unmanaged wallets

Your whitelisted addresses on Fireblocks can also be classified as unmanaged wallets. Internal unmanaged wallets benefit from Fireblocks watching the blockchains and showing their current balance. Their addresses count as part of the Fireblocks Address Package pricing. Internal unmanaged wallets can be accessed via API or your Console.

J

Fireblocks Javascript SDK

Easily utilize Fireblocks REST API with a dedicated SDK for JavaScript.

K

Key Share Backup and Recovery (Soft Key Recovery)

One disaster recovery method for the mobile MPC key share of your workspace Owner. There are two methods for Key Share Backup and Recovery: device reset by owner and recovery by passphrase. With device reset by Owner, you can recover your private key with key share recovery if you have access to a mobile device of another Admin or Signer user.

M

Fireblocks managed wallets

Any wallet you create in your Fireblocks Vault is considered a managed wallet, whether your configuration is hot, warm, or cold. The private cryptographic keys are split using MPC-CMP and users sign transactions from these wallet addresses, which is unlike external unmanaged wallets like whitelisted addresses or connected exchange accounts.

Manual operation mode

Your transactions are submitted through the UI or API, however, approval is via the quorum definition in the TAP policy (2-tier configuration). Users who are assigned an authorizer role will be notified through the Fireblocks mobile app, then they will approve until a quorum has been reached (n of m).

Fireblocks mobile app

The Fireblocks mobile app is the companion to your workspace and enables you to securely approve and sign transactions on your mobile device. Any users with signer roles in your workspace must use the app for transaction signing and connecting new DeFi apps using WalletConnect. Admins and Owners must use the app to approve user or policy changes initiated in the Console or API. Available for Android and iOS.

Multi-layer security

The Fireblocks security philosophy and implementation combine four layers of security to ensure your assets remain secure during both custody and transfer. The layers are:

• MPC-CMP wallet infrastructure
• An Intel SGX hardware layer
• The Fireblocks Policy and Workflow Engine
• The Fireblocks Network

N

Fireblocks Network channels

Within your workspace, users can set up multiple Fireblocks Network channels that allow you to manage your Network connections. You can create channels for different connections or groups of connections and sort channels by activity like lending, payments, or trading. Each workspace has a default channel named after the workspace and a corresponding vault called "Network deposits." 

Fireblocks Network connections

When you use the Fireblocks Network feature, any member you connect with becomes your Fireblocks Network Connection. When transferring with these counterparties you benefit from the security and efficiency of Automated Address Authentication and Automatic Address Rotation.

Fireblocks Network members

Fireblocks customers who use the Fireblocks Network feature are members of the Fireblocks Network. They can become connections and counterparties for other members, and benefit from the security and efficiency features like Automated Address Authentication and Automatic Address Rotation.

NFT SDK

Easily manage your NFTs across their entire lifecycles and deploy services in just a few lines of code using Fireblocks NFT SDK, part of our DeFi SDK. Includes programmatic support for transfer, mint, and burn for ERC-721, ERC-1155, or any custom NFT standard. Available in our GitHub public repository.

Notification Center

Admins and Owners can set up Audit Log notifications for workspace users. Users (restricted to settings access) can elect to receive emails, Slack, and webhook notifications on designated Audit Log events. This provides visibility into workspace events like logins, transactions, whitelisting, vault activity, and AML events. Enables faster responses to security / compliance-related risks.

O

OEMS (O/EMS) integrations  

Fireblocks is integrated into the software of two top OEMS (Order Execution Management System) providers, AlgoTrader and Talos. Contact your Customer Success Manager to connect with either provider.

One-time address (OTA) transactions  

A feature allowing you to transfer assets to non-whitelisted addresses. It’s disabled by default and your workspace Owner must ask to enable it. Because OTAs have no metadata description about the person or company it represents, it is against compliance rules including Travel Rule. Due to the risks, consider setting policies to use this feature.

Owner role

An Owner is the root user of a workspace and the Admin who approves multi-party computation (MPC) signing devices. The Owner is a mandatory approver of the Admin Quorum for approving new users. Every workspace requires one - and only one - Owner to set up the Vault.

For security purposes, the Owner role must be assigned to the respective user by Fireblocks Support. If the Owner wants to change their role, migrate to a new mobile device, or unfreeze the workspace, they must first verify their identity with Fireblocks Support by scheduling a short video call.

P

Permissioned token tokenization 

You can create smart contracts for, mint, and issue permissioned tokens using the Fireblocks Tokenization Engine and Tokeny integration. Tokeny’s ERC-3643 standard tokens use identity technology called ONCHAINID to ensure onboarded investors have been identified as KYC compliant.

Fireblocks platform

Any reference to the Fireblocks platform refers to the full range of Fireblocks MPC-CMP wallet infrastructure and Network technology, including all Console and API-based features.

Policy rule parameters

Within your TAP, there is a wide range of parameters and filters you can set to define custom policy rules for your workspace and users. These parameters include Initiator, Type, Source, Source Name, Destination, Destination Names, Whitelisted/OTA, Amount, Time Period, Asset, Action, Approved By, Initiator Counts as Approver?, Designated Signer, and Comments. 

Fireblocks Python SDK 

Easily utilize Fireblocks REST API with a dedicated SDK for Python.

R

Raw Signing API

Provides access to protocols, transaction types, and DeFi apps that are not yet fully supported on Fireblocks. With the Raw Signing API, users can generate ECDSA and EdDSA signatures to sign any transaction type or message. Raw signing can aggregate up to 127 messages for signing at once. Raw Signing uses the Fireblocks platform's existing security mechanisms, including MPC signing, key protection, transaction flow in a trusted execution environment, and your transaction authorization policies.

Recent activity panel

The Recent activity panel (formerly Active Transfers panel) on the right side of your Fireblocks Console shows a list of all pending, ongoing, and recently completed transactions within your workspace. It can be filtered by direction, venue, asset, and status. You can select any transfer to see more details.

S

Fireblocks self (direct) custody

Fireblocks’ MPC-CMP wallet infrastructure and custody technology allow you to keep control of your private keys and assets. Unlike custodians, we do not take possession of your full private keys and you are not dependent on Fireblocks operating hours or SLAs to access your assets.

Fireblocks segregated vault structure

Manage funds in unique wallets, where every wallet is assigned to a specific client identifier. The advantages of using segregated vaults include:

• Using blockchain as a single source of truth ledger. Removes the need for reconciliation.
• Settlements are inherently atomic (on-chain), which reduces complexity and counterparty risk
• Simplifies tracking and auditing

Disadvantages of using segregated vaults include:

• In case most settlements are internal, which requires on-chain transactions and corresponding fees
• Most public blockchains offer lower transaction per second volume than required by Enterprises
• Requires extra measures to mitigate customer privacy concerns

Self-Service user and workspace management

Admins for your workspaces can manage user and workspace settings directly in your Console, without relying on Fireblocks Support to implement changes. 

Semi-automatic operation mode

Uses TAP rules that are configured as 2-tier (n of m quorum). This forces transactions to be approved manually using personal operators, but the MPC signing is automated through the API Co-Signer server setup - using an API user with the signing privileges to automatically sign transactions submitted by the initiator.

Settings tab

A page in your Console where you can access and request changes to Admin Quorums, Amount Caps for Approve Transactions, view your transaction authorization policies, manage users, view audit logs, and more depending on your role in the workspace.

(Intel) SGX security layer

Fireblocks’ Intel SGX hardware isolation is part of Fireblocks' multi-layer solution. With Fireblocks MPC-CMP wallets, private keys are protected and stored in Intel SGX hardware, which is secure enclaves that are protected and inaccessible to any processes outside of the enclave itself (including the operating system itself and processes with higher privileges). One key share is held on your mobile device and two others are held in SGX-secured enclaves at top-tier cloud providers, or the mobile key share can alternatively be hosted at an API Co-Signer through an SGX-enabled platform.

The SGX layer enables you to protect both your transfers and policies from malicious insiders who may want to tamper with either. In addition to securely storing key shares, Fireblocks SaaS also uses Intel SGX enclaves to store its code and the secure configuration of customers' transaction policies.

Smart contract creation with Tokeny

If you are interested in issuing tokenized fiat, financial, commodity, or real-world assets, the first step is creating a smart contract. You can combine the Fireblocks Tokenization Engine with our integration with Tokeny for end-to-end tokenization all the way from smart contract creation.

Smart contract development using Fireblocks API

Securely develop, deploy, and operate your on-chain smart contracts with Fireblocks' security layers. Provide granular role-based access control for managing which developer is allowed to deploy smart contracts, perform upgrades, or call sensitive smart contracts operations, such as pausing or updating contract data. Learn how to deploy and operate smart contracts using the Fireblocks API.

Stablecoin support

Fireblocks offers robust custody and transfer support for top stablecoins, tokens that are pegged to the value of a fiat currency, across any supported blockchains that they are built on top of.

Status page 

A web page that logs status updates on all Fireblocks systems where you can view the historical status of incidents dating back to March 2021. The URL is status.fireblocks.com.

Sweeping via API  

API capability that enables you to set up automation to periodically transfer funds from intermediary deposit accounts into an omnibus vault account using the Create Transaction API. If you don't wish to implement a fueling logic on your end, you can use an automated fueling service known as the Fireblocks Gas Station.

Fireblocks Support 

Contact Fireblocks Support if you need assistance or have other questions. Support is available 24/7.

T

Tax integrations

Integrations with leading automated crypto tax software providers TaxBit and Cryptio to help you with tax compliance, accounting, and reporting across both DeFi and CeFi transactions for your workspaces.

Third-party accounts

You can connect your existing accounts from third-party exchanges and fiat accounts from crypto-friendly banks that have integrations with Fireblocks. The full list of integrated parties is here.

Tokenization Integration

Integration with tokenization specialist Tokeny for end-to-end tokenization all the way from smart contract creation. Added value integration to the Fireblocks Tokenization Engine if you want to issue permissioned tokens or seek an all-in-one tokenization solution that includes smart contract creation. Includes white-labeled Tokeny investor onboarding and issuance dashboards for advanced servicing.

Transaction Authorization Policy (TAP)

The rules-based engine that defines limitations for all transactions executed within the Fireblocks workspace. Your TAP serves as an additional security level to verify that each transaction is processed according to the desired policy determined by the client. Learn more about TAP.

Transaction Reports

Review transactions in the Transaction History tab of your Console and download Transaction Reports.

Typed Message Signing

Allows you to sign messages, but only using specific standard formats that prefix the message with a magic string, mitigating the risk of exploits to sign a valid malicious transaction. Used for ETH_MESSAGE and EIP712 message types. Learn more here.

U

User roles

There are seven types of roles for users in your Fireblocks workspace. The roles are Owner, Admin, Non-Signing Admin, Signer, Approver, Editor, and Viewer. Roles are defined by workspace Admins through the Settings menu of your Fireblocks Console. Role types have different levels of access to features and workplace settings, and you can define custom policies based on specific user roles.

Fireblocks unmanaged wallets

Your whitelisted addresses on Fireblocks can also be classified as unmanaged wallets. There are two types, internal and external unmanaged wallets:

• Your internal unmanaged wallets benefit from Fireblocks watching the blockchains and showing their current balance. Their addresses count as part of the Fireblocks Address Package pricing.
• Your external whitelisted address wallets do not show their balances and are not counted as part of the Fireblocks Address Package pricing.

Internal and external unmanaged wallets have different API endpoints but show in the same part of your Console.

UTXO Multiple Destinations

A feature that maximizes efficiency and minimizes fees for UTXO transactions initiated via the API. You may use the destinations parameter to specify multiple addresses as documented here.

W

WalletConnect DeFi integration

One of the three Fireblocks DeFi gateways. We offer a native integration in your Console through WalletConnect, an open protocol for communicating securely between wallets and DeFi apps. Through a DeFi Apps tab in your Console, access 100s of apps that work with WalletConnect, including apps for non-EVM blockchains like Terra and Algorand, which don’t work with MetaMask.

Fireblocks webhooks (Push API)

Setting webhooks allows you to get real-time notifications right after workspace events occur and get signed transactions automatically sent to the blockchain without manual intervention. Receive push notifications on events like requests to sign transactions, incoming and outgoing transactions, transaction status updates, new vaults, new wallets, new external/internal addresses, and many more.

Once your webhook is connected, you will start receiving notifications on events in that workspace. The full list of event types you can receive Webhook notifications for is here in the Developer Portal. Your Notification Center in your Console also allows webhook notifications but based on a different base source: audits. To connect a webhook to your workspace refer to this article.

Whitelisted addresses

Fireblocks allows you to maintain a secure list of whitelisted addresses to make transfers easier. Whitelisting is needed to use an address as a destination of a withdrawal.

• Internal wallets are your personal whitelisted addresses outside Fireblocks.
• External wallets are your external counterparties’ whitelisted addresses.
• Contract wallets are your whitelisted smart contracts for Web3 apps.

Note that requests to whitelist an external wallet or a contract wallet must be approved by your Admin Quorum.

Whitelisted addresses have a wallet name, which enables compliance for the known beneficiary person or company. They can be easily reused in places like your Transaction Authorization Policy or easily approved when seeing them as destinations using the Fireblocks mobile app. We recommend whitelisting all transaction recipients compared to using One-Time Addresses.

Workspace Keys Backup and Recovery (Hard Key Recovery)

The disaster recovery process allows you to recover your full extended private keys for your whole workspace. You can reconstruct the private key seed to your Fireblocks Vault, allowing you to control your vault and fully recover your assets in a recovery scenario using your workspace owner's recovery passphrase that was in use when the backup was created.