انتقل إلى المحتوى الرئيسي

Transaction Fees

The small fees paid to process instructions on the Solana blockchain are known as "transaction fees".

As each transaction (which contains one or more instructions) is sent through the network, it gets processed by the current leader validation-client. Once confirmed as a global state transaction, this transaction fee is paid to the network to help support the economic design of the Solana blockchain.

NOTE: Transaction fees are different from account rent! While transaction fees are paid to process instructions on the Solana network, rent is paid to store data on the blockchain.

You can learn more about rent here: What is rent?

Why pay transaction fees?

Transaction fees offer many benefits in the Solana economic design described below. Mainly:

  • they provide compensation to the validator network for the CPU/GPU resources necessary to process transactions,
  • reduce network spam by introducing real cost to transactions,
  • and provide long-term economic stability to the network through a protocol-captured minimum fee amount per transaction

NOTE: Network consensus votes are sent as normal system transfers, which means that validators pay transaction fees to participate in consensus.

Basic economic design

Many blockchain networks (e.g. Bitcoin and Ethereum), rely on inflationary protocol-based rewards to secure the network in the short-term. Over the long-term, these networks will increasingly rely on transaction fees to sustain security.

The same is true on Solana. Specifically:

  • A fixed proportion (initially 50%) of each transaction fee is burned (destroyed), with the remaining going to the current leader processing the transaction.
  • A scheduled global inflation rate provides a source for rewards distributed to Solana Validators.

Why burn some fees?

As mentioned above, a fixed proportion of each transaction fee is burned (destroyed). This is intended to cement the economic value of SOL and thus sustain the network's security. Unlike a scheme where transactions fees are completely burned, leaders are still incentivized to include as many transactions as possible in their slots.

Burnt fees can also help prevent malicious validators from censoring transactions by being considered in fork selection.

Example of an attack:

In the case of a Proof of History (PoH) fork with a malicious, censoring leader:

  • due to the fees lost from censoring, we would expect the total fees burned to be less than a comparable honest fork
  • if the censoring leader is to compensate for these lost protocol fees, they would have to replace the burnt fees on their fork themselves
  • thus potentially reducing the incentive to censor in the first place

Calculating transaction fees

Transactions fees are calculated based on two main parts:

  • a statically set base fee per signature, and
  • the computational resources used during the transaction, measured in "compute units"

Since each transaction may require a different amount of computational resources, they are alloted a maximum number of compute units per transaction known as the "compute budget".

The execution of each instruction within a transaction consumes a different number of compute units. After the maximum number of compute units has been consumed (aka compute budget exhaustion), the runtime will halt the transaction and return an error. This results in a failed transaction.

Learn more: compute units and the Compute Budget in the Runtime and requesting a fee estimate from the RPC.

Prioritization fee

Recently, Solana has introduced an optional fee called the "prioritization fee". This additional fee can be paid to help boost how a transaction is prioritized against others, resulting in faster transaction execution times.

The prioritization fee is calculated by multiplying the requested maximum compute units by the compute-unit price (specified in increments of 0.000001 lamports per compute unit) rounded up to the nearest lamport.

You can read more about the compute budget instruction here.

Fee Collection

Transactions are required to have at least one account which has signed the transaction and is writable. Writable signer accounts are serialized first in the list of transaction accounts and the first of these accounts is always used as the "fee payer".

Before any transaction instructions are processed, the fee payer account balance will be deducted to pay for transaction fees. If the fee payer balance is not sufficient to cover transaction fees, the transaction will be dropped by the cluster. If the balance was sufficient, the fees will be deducted whether the transaction is processed successfully or not. In fact, if any of the transaction instructions return an error or violate runtime restrictions, all account changes except the transaction fee deduction will be rolled back.

Fee Distribution

Transaction fees are partially burned and the remaining fees are collected by the validator that produced the block that the corresponding transactions were included in. The transaction fee burn rate was initialized as 50% when inflation rewards were enabled at the beginning of 2021 and has not changed so far. These fees incentivize a validator to process as many transactions as possible during its slots in the leader schedule. Collected fees are deposited in the validator's account (listed in the leader schedule for the current slot) after processing all of the transactions included in a block.