Welcome to Fireblocks!

This onboarding guide will simplify your journey with Fireblocks. Please review it and prepare the requirements to make your onboarding as smooth and fast as possible.

Before you begin

Come prepared with the following for the kickoff call.

User Types and Roles

Each Fireblocks workspace contains different user types and permissions. Here are four of the main user roles:

• Owner: This is the first user to access the workspace. The workspace Owner must approve adding users with signing permissions, changes to governance policies, and resetting of mobile devices. There is only one Owner per workspace.
• Admin: Admin users can sign transactions (which is necessary to broadcast them to the blockchain) and can approve workspace changes.
• Signer: Signers can sign transactions to be broadcast to the blockchain.
• Non-Signing Admin: An admin without signing privileges.

Kickoff call preparation

• Determine the Owner while considering both operational needs and security
• Think about who the Admins and Signers should be--remember, they must have a physical mobile device to sign transactions
• Have at least one other Admin or Signer in addition to the Owner

Mobile hardware requirements

All users with signing capabilities must have a mobile device with biometric identification functions according to the following specifications:

• Android: A 64-bit device running Android 8.1 or later with authentication capabilities, such as Yubikey, fingerprint, or face authentication. The device must have the Google Play Store application in order to download the Fireblocks application.
• iOS: An Apple device running iOS 13.1 or later with authentication capabilities, such as Yubikey, Touch ID, or Face ID. The device must have the Apple App Store application in order to download the Fireblocks application.

Admin Quorum

The Admin Quorum can consist of three user types: Owner, Admins, and Non-Signing Admins. Changes to workspace configurations, such as adding new users, whitelisting new addresses, and connecting exchange accounts, require approval from the Admin Quorum. Consolidating the admins who can approve workspace changes into a quorum ensures that change requests are centralized.

Kickoff call preparation

• Determine which Admin-level users should be in the Admin Quorum
• Decide on the Admin Quorum threshold--how many quorum members are required to approve each workspace change
• Ensure the threshold is at least two so that a single user can’t approve their own changes

Security Contact

Fireblocks requires a security point of contact for communication regarding security incidents and issues.

Kickoff call preparation

• Provide the name, title, email address, and phone number of the security contact

Wallet Architecture

When using the Fireblocks platform, you may choose an appropriate custody model.

• Self-Custody: Holding assets for your own uses.
• Segregated: Holding assets on behalf of your customers.
• Omnibus: Holding assets on behalf of a large number of end users.

Kickoff call preparation

• Determine whether you plan on holding assets on your own or on behalf of your customers.
• Should you choose to hold assets on behalf of your customers, consider how many wallets you will need to create. A wallet can hold different assets, meaning you need just one per customer.

API

Optionally, you can use the Fireblocks REST API for workspace management and transaction flow automation. When you have a high transaction volume, it's important to have enough resources to manage the requests.

Note that certain endpoints are subject to rate limits. Consider reducing your redundant API requests to comply with the limits. However, you can purchase increased limits if necessary.

Kickoff call preparation

• Consider setting up multiple API Co-Signers across different geographical locations to build an active-active, high-availability configuration. This will require setting up at least one server over the cloud, using either Microsoft Azure or Amazon Web Services (AWS).
• Have the option to store a private key safely, so that you can sign requests sent over the Fireblocks platform.

Third-party integrations

Fireblocks supports connecting to different smart contract providers, which allows for seamless integration and creation of contract calls. The following providers are supported:

• Tokeny
• OpenZeppelin
• Defender
• Any WalletConnect-based dApp that allows contract creation and deployment

Kickoff call preparation

• Check that your third-party accounts are ready to integrate with the Fireblocks platform. Some vendors require long KYC processes so it is important to start this process as soon as possible.

Tokenization

Different tokenization operations can be performed using Fireblocks. You can use the Fireblocks Console to perform the following:

• Transfer, mint, and burn ERC-20 and Stellar tokens
• View ownership and metadata of ERC-721 non-fungible tokens (NFTs)

Additionally, we support any EVM-based contract using our Contract Call operation. Tokenization on non-EVM blockchains may require Raw Signing.

Kickoff call preparation

• Consider the required infrastructure for your Tokenization operations, such as Solidity code. Understanding how you will manage your contract or token will simplify the onboarding process and help the Fireblocks onboarding team to ensure a smooth setup.

Pre-kickoff checklist

• Determine the workspace Owner
• Think about who the Admins and Signers should be
• Have at least one other Admin or Signer in addition to the Owner
• Determine which Admin-level users should be in the Admin Quorum
• Decide on the Admin Quorum threshold and ensure the threshold is at least two
• Provide the name, email address, and phone number of the security POC
• Determine whether you plan on holding assets on your own or on behalf of your customers
• Determine which wallet architecture model is optimal for your use case
• Consider the amount of API resources required for your use case
• Think about the tokenization infrastructure required for your business operations

Have a question?

We're here to help. Reach out to your Sales Director with any questions you have or if you need any assistance.

Terms of Service

Please refer to your executed order forms and MSA for the full terms and conditions related to your purchase of Fireblocks services.

Unless explicitly stated in your ordering documents, the service term of your subscription will commence upon execution of the ordering documents. The subscription term will commence accordingly, regardless of whether or not you have started actively using the service. Note that Fireblocks does not allow for deferral of the service start date or freezing of subscriptions.

Subscriptions are non-cancellable and non-refundable for the duration of the term.

An invoice will be issued in accordance with the terms of your contract, which will typically be upon execution of the ordering documents. Payment is due in accordance with your contract and late payment may result in additional fees and/or suspension of service.

When sending payment, please follow these remittance instructions. This allows us to ensure timely and accurate attribution of your payment to any outstanding balances.