TON High-Load Wallets

• Increase throughput: Enable parallel transaction execution.
• Remove bottlenecks: Bypass the “one-transaction-at-a-time” constraint of standard wallets.
• Support high-frequency use cases: Scale for exchanges, payment processors, and similar workloads.

​

Creating a High-Load Wallet

​

Immutable implementation selection

​

API integration example

import { VaultsApiFp } from "@fireblocks/ts-sdk";

// ... initial client setup ...

const vaultAccountId = "12"; // Your Vault ID
const assetId = "TON";       // Asset ID
const blockchainWalletType = "highload_v3";

// Generate the request function
const requestFn = await VaultsApiFp(fireblocks.vaults.configuration).createVaultAccountAsset(
    vaultAccountId,
    assetId,
    undefined,
    undefined,
    { params: { blockchainWalletType } } // Pass the wallet type in query params
);

// Execute the request
const { data: asset } = await requestFn(fireblocks.vaults.axios, fireblocks.vaults.basePath);

console.log(`Asset Created: ${asset.id} with Address: ${asset.address}`);

​

Transaction flow and monitoring

​

Limitations

1. Single TON address per vault: You can create only one TON wallet (either TON_V4 or HLW) in a vault account.
2. No batching: Fireblocks does not currently support batched TON transactions. Each transaction supports a single transfer only.
3. Parallel transaction sending: To enable sending multiple transactions in parallel, contact Fireblocks Support and provide the vault ID of your HLW.