> ## Documentation Index
> Fetch the complete documentation index at: https://developers.fireblocks.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Add a Hedera Asset Wallet

> Create HBAR and Hedera Token Service (HTS) asset wallets in a vault account, and choose how each HTS token is associated with the account on-chain.

## Overview

On Hedera, an account must be associated with a Hedera Token Service (HTS) token on-chain before it can receive that token. Creating an HTS asset wallet in Fireblocks does not perform this association by default. Fireblocks creates an internal representation of the wallet only, and the token is associated on-chain later depending on the funding option you choose.

All HTS asset wallets in a vault account share the vault's base HBAR deposit address. This behavior mirrors Solana, where each SPL token requires its own on-chain token account that is commonly funded by the first sender. See [Create Direct Custody Wallets](/docs/create-direct-custody-wallets) for how this compares to other blockchains.

## Add an HBAR asset wallet to a vault account

To add an HBAR asset wallet using the Fireblocks Console:

1. Go to **Accounts** > **Vault** in your Fireblocks Console.
2. Select the vault account to which you want to add the HBAR asset wallet.
3. Select **+ Create Wallet**.
4. In the Add Asset Wallet window, select **HBAR** from the drop-down list. You can also begin typing the asset's name to search for it. You can add only one wallet per asset type per vault account.
5. Select **Add**.

You can also create the wallet with the [Create Vault Wallet](/reference/create-vault-wallet) API flow.

## Add an HTS asset wallet to a vault account

Create the HTS asset wallet the same way as the HBAR wallet above, selecting the HTS token from the drop-down list. Creating the wallet registers the asset internally in Fireblocks. No on-chain association transaction is submitted at that point.

The token association fee is covered by one of two funding options:

1. **First sender covers the fee:** The fee is deducted when the first incoming transaction occurs. No upfront action is required.
2. **Fund from the vault HBAR balance:** The fee is deducted from the vault's HBAR balance immediately after wallet creation. This option requires transaction signing.

When creating the wallet via API, set the `blockchainWalletType` parameter to select the funding option. See [Hedera HTS tokens](/reference/create-vault-wallet#hedera-hts-tokens) for details.

<Note>
  Not all senders support transfers to accounts that are not yet associated with the token. Fireblocks supports outgoing transfers to destinations that are not associated with the token.
</Note>

## HBAR wallets created before July 2026

HBAR wallets created before July 2026 do not support sender-funded association. For these wallets, associate each HTS token before receiving deposits by creating the token wallet with the **Fund from the vault HBAR balance** option.

## Deposits to unassociated accounts

Deposits to an account that is not associated with the token, where the sender does not cover the association fee, fail on-chain with the `TOKEN_NOT_ASSOCIATED_TO_ACCOUNT` error. If a deposit fails with this error, associate the token with the account and ask the sender to retry the transfer.

## Listing HTS tokens

To add an unlisted HTS token to your workspace, contact Fireblocks Support with a link to the token's page on the relevant block explorer. [Learn more about adding unlisted tokens](/docs/add-your-tokens-1).

For token operations that are not yet natively available through the Fireblocks Console and APIs, see the [Hedera Token Service SDK](/reference/hedera-token-service-sdk).