Skip to main content

Manage asset wallets

Overview of asset wallets

Asset wallets manage the deposit addresses for your digital assets within a vault account. Each asset wallet contains at least one deposit address for its asset type and is assigned to a single asset supported by Fireblocks. Depending on the asset type, a wallet may support multiple address types or formats.

Any user with the appropriate permissions can create an asset wallet without secondary approval, except for wallets on blockchains that require manual confirmation.

Create an asset wallet

Via the Fireblocks Console

  1. Go to Accounts > Vault and select the appropriate vault account.
  2. Select Create wallet.
  3. On the Create asset wallet dialog, enter or search for the asset or token name. Token names can exist on multiple networks, so make sure to select the correct one.
  4. Select Create wallet.

Via the Fireblocks API

See Create a vault wallet on the Fireblocks Developer Portal.

Activating asset wallets

Each vault account can contain two types of asset wallets: base asset wallets, which represent a blockchain's native currency (for example, ETH or SOL), and token asset wallets, which represent tokens built on top of that blockchain (for example, USDC or USDT).

To receive funds in a vault account, at least one asset wallet must exist in that account. Creating the first asset wallet (whether a base asset wallet or a token asset wallet) generates the vault account's deposit address and tells Fireblocks to begin monitoring that address for incoming transfers.

How Fireblocks processes incoming transfers

When Fireblocks detects an incoming transfer to a monitored address, it follows these steps:

  • Checks whether the incoming asset is globally listed or locally listed in your workspace. If it is not listed, the balance is processed onchain but not reflected in Fireblocks since there is no corresponding asset wallet.
  • Checks whether an asset wallet for that asset already exists in the vault account. If one does not exist, Fireblocks creates one automatically.
  • Shows the incoming transfer, updates the asset wallet balance, and creates a record of the transfer in your transaction history.

When a token asset wallet is created (whether manually or automatically) and the vault account does not yet contain the corresponding base asset wallet, Fireblocks also creates the base asset wallet automatically. For example, adding a USDC token asset wallet to an empty vault account also creates an ETH base asset wallet.

Note

If automatic asset enablement is disabled in your workspace, incoming base asset transfers to a valid deposit address still create a new base asset wallet if one does not exist. For example, an incoming BNB transfer to a vault account with only an ETH wallet creates a new BNB wallet.

EVM

On EVM chains, a vault account uses a single deposit address shared across all EVM asset wallets in that vault account, regardless of chain or token. You only need to create one EVM asset wallet (base or token) to generate this address and activate monitoring for all EVM assets.

Once monitoring is active, Fireblocks automatically creates an asset wallet for any incoming globally listed EVM asset that does not yet have one in the vault account. This applies across all supported EVM chains. For assets not globally listed, first add the asset to your workspace via the Console or API. Its asset wallet is then created automatically upon receipt, just like globally listed assets.

Fireblocks recommends not creating EVM asset wallets in advance. Share the vault's EVM address, and Fireblocks creates the asset wallet automatically when the first deposit is detected.

Solana

On Solana, a vault account uses the base SOL address as its deposit address for both the SOL base asset wallet and all Solana token asset wallets. You only need to create one Solana asset wallet (base or token) to generate this address and activate monitoring.

When Fireblocks creates a Solana token asset wallet (whether manually or upon first receipt), it is created as an internal representation only; no on-chain transaction is performed at the time of wallet creation. The on-chain account is created upon the first incoming transaction, with the sender covering the rent cost. Share the vault's base Solana address with the sender, and Fireblocks handles the rest automatically upon first receipt.

Archive or unarchive an asset wallet

Since you can't delete asset wallets, archiving is one way to keep your Vault organized. Fireblocks recommends archiving wallets when your workspace has fewer than 100 vault accounts accessed primarily via the Console, or when you have wallets with little to no activity that you want to remove from view.

Important

  • Archived wallets can still receive incoming transactions. When this happens, the wallet is automatically unarchived.
  • You cannot select an archived wallet in the Console as a transaction's source or destination. However, archived wallets are always available via the Fireblocks API.
  • Archived wallets are not included in your Vault's balance chart.
  • Transactions involving archived wallets still appear in your transaction history.

Archive an asset wallet

  1. Go to Accounts > Vault.
  2. Open the appropriate vault account, find the wallet you want to archive, and select More actions > Archive.
  3. Select Archive.

Unarchive an asset wallet

  1. Go to Accounts > Vault.
  2. Open the appropriate vault account and select Show archived to see its archived wallets.
  3. Select Unarchive for the appropriate wallet.

Related resources

Was this article helpful?
3 out of 6 found this helpful

Related Articles