Estimate Fee

The estimateFee endpoint estimates the fee for a transaction on the TON blockchain. This endpoint allows you to calculate the expected fees before actually sending a transaction.

👍

Get you own node endpoint today

Start for free and get your app to production levels immediately. No credit card required.

You can sign up with your GitHub, X, Google, or Microsoft account.

📘

TON pricing is the same for full, archive, v2, v3

There's no difference between a full node an archive node in data availability or pricing.
All data is always available and all node requests are consumed as 1 request unit.

Parameters

• address (string, required) — The address of the smart contract.
• body (string, required) — The body of the transaction in base64 format.
• ignore_chksig (boolean, optional) — Whether to ignore the signature check. Default: false.

Response

The response includes the estimated fees for both the source and destination of the transaction.

Source Fees

• in_fwd_fee (integer) — The incoming forward fee.
• storage_fee (integer) — The storage fee.
• gas_fee (integer) — The gas fee.
• fwd_fee (integer) — The forward fee.

Destination Fees

• in_fwd_fee (integer) — The incoming forward fee.
• storage_fee (integer) — The storage fee.
• gas_fee (integer) — The gas fee.
• fwd_fee (integer) — The forward fee.

Use case

The estimateFee endpoint is useful for various applications that need to estimate transaction costs on the TON blockchain:

1. Wallet applications can use this to show users the expected cost of a transaction before they send it.
2. Smart contract developers can use this to estimate the cost of deploying or interacting with contracts.
3. DApp developers can integrate this to provide users with accurate fee estimates for transactions.
4. Automated trading systems can use this to factor in transaction costs when making trading decisions.
5. Fee optimization tools can use this endpoint to suggest optimal transaction parameters.

Try the estimateFee RPC method yourself