Request for Testnet Account and Guidance on Required Production Settings

Developer Discussion
1

Hi Fireblocks team :waving_hand:,

I’ve been testing my integration successfully on the Fireblocks Sandbox environment, and everything is working as expected.

In my sandbox setup:

  • I created separate vaults for each network (Ethereum, BSC, and TRON)

  • I’m supporting USDT on all those networks

  • I’ve enabled Auto Gas Fuel, which is working correctly

Now, I’m preparing to move my service to Production (Mainnet), and I want to make sure I follow the correct process and configuration best practices.

I have two questions:

  1. How can I request or activate a Fireblocks Testnet account?
    I’d like to run a full test in a Testnet environment before going live on Mainnet, as recommended in the Fireblocks documentation.
    Is there a specific request process (via Support or my Account Manager) to create a Testnet workspace?

  2. For my current setup (multi-chain vaults with USDT and Auto Gas Fuel), what configurations are required or recommended in the Production Fireblocks environment?
    Specifically, I’d like to confirm which Production settings (e.g., vault structure, network enablement, policy configuration, Auto Gas setup) need to be created or adjusted to match my Sandbox setup.

Thank you in advance for the guidance!
I’d like to ensure a smooth transition from Sandbox → Testnet → Production following Fireblocks’ recommended practices.

—
My current Sandbox setup:

  • Networks: ETH / BSC / TRON

  • Assets: USDT

  • Features: Auto Gas Fuel enabled

2

Hi @dung.nguyen.trung

Great to hear that your integration is working smoothly in the Sandbox.

For your first question:
:right_arrow: Access to a Testnet workspace (as well as a Production/Mainnet environment) requires an active paid subscription. You can explore available subscription plans and request access through our pricing page: https://www.fireblocks.com/pricing/.

For your second question:
When moving from Sandbox to Production, your vault structure and configuration should primarily reflect your business use case rather than just the supported assets. You can refer to our detailed best practices here:
:small_blue_diamond: Vault structure best practices

To further fine-tune your setup, you may also find these guides helpful:
:small_blue_diamond: Policy engine examples
:small_blue_diamond: User & group management best practices

These resources cover common configurations for production environments, including how to align your policies, user roles, and automation settings for secure operations.

Hope this helps ensure a smooth transition from Sandbox → Testnet → Production :rocket:

Séba from Fireblocks