Skip to main content
Every transaction on a blockchain network requires a fee — commonly called “gas” — paid to validators for processing your transaction. On EVM-compatible chains like Ethereum, these fees are denominated in the network’s native token (ETH, BNB, MATIC, etc.) and must be available in the sending address before a transaction can be submitted. Gas Tanks solve the operational problem of ensuring that gas is always present when you need it, without requiring manual top-ups before every transaction.

​
What Is Gas?

Gas is the unit of computation cost on a blockchain network. When you send tokens, interact with a contract, or sweep funds, the network charges a gas fee calculated as:
For example, a standard ETH transfer on Ethereum costs 21,000 gas units. At a gas price of 10 gwei, that equals 0.00021 ETH. More complex operations — such as ERC-20 token transfers — cost more gas. The fee is always paid in the native token of the chain (ETH on Ethereum, BNB on BSC, AVAX on Avalanche, and so on).

​
What Is a Gas Tank?

A Gas Tank is a pre-funded reserve managed by Finrock that ensures your wallet addresses always have sufficient native token to cover transaction fees. Instead of manually topping up each address with small amounts of native token before every operation, you fund a single Gas Tank for a given chain, and Finrock automatically routes gas to your addresses when they need it.
Gas Tanks are specific to a blockchain network. You maintain a separate Gas Tank balance for each chain you operate on (e.g., one for Ethereum, one for BSC, one for Polygon).

​
Why You Need a Gas Tank

Without a Gas Tank, every address that needs to send tokens must also hold a small balance of the chain’s native token. Managing this at scale — across hundreds or thousands of addresses — creates significant operational overhead and is a common cause of stuck or failed transactions.

Seamless User Experience

Your users and automated systems never need to think about gas. Transactions execute immediately without waiting for manual fee top-ups.

Cost Management

Pre-fund your Gas Tank when native token prices are lower. Manage your fee budget centrally rather than across thousands of individual addresses.

Transaction Automation

Automated sweeps, payouts, and contract interactions run without constant human intervention to keep addresses funded with gas.

Prevent Failed Transactions

Transactions submitted without sufficient gas fail — and you still pay any gas that was consumed. A funded Gas Tank eliminates this failure mode entirely.

​
Automatic Gas Refill

When you create or update an address, you can set the auto_refill flag to true. With this flag enabled, Finrock automatically draws from your Gas Tank to fund that address with native token whenever its gas balance falls below the threshold required to execute a transaction.
This is the recommended configuration for any address involved in automated workflows — including omnibus addresses, sweep destinations, and high-frequency payout addresses.
Manual Sweep operations may fail if your Gas Tank has insufficient funds. Always ensure your Gas Tank holds an adequate reserve before initiating bulk sweeps or high-volume transaction periods. Monitor your Gas Tank balance via the API and set up alerts to avoid interruption.

​
Supported Blockchains

Gas Tanks are available for all major EVM and fee-token blockchains supported by Finrock:

Ethereum

ETH

Binance Smart Chain

BSC (BNB)

Tron

TRX

Solana

SOL

Avalanche C-Chain

AVAX

Polygon

POL (formerly MATIC)

Fantom

FTM

Cronos

CRO

Arbitrum

ARB

Harmony

ONE

Optimism

OP_ETH

Klaytn

KLAY

​
Managing Gas Tanks via the API

You can view your Gas Tank balances and manage funding programmatically through the Finrock REST API. Use the following endpoints: Refer to the Gas Tanks API reference for full request and response schemas, authentication requirements, and examples.
Set up a regular job or webhook listener to monitor your Gas Tank balance. Proactively top up before high-volume periods (e.g., batch payout runs, end-of-day sweeps) to avoid transaction failures.