2020-07-10 22:11:07 -07:00
|
|
|
---
|
|
|
|
|
title: Deterministic Transaction Fees
|
|
|
|
|
---
|
2019-09-22 20:38:34 -07:00
|
|
|
|
|
|
|
|
## Calculating fees
|
|
|
|
|
|
2022-06-22 16:46:37 -07:00
|
|
|
Before sending a transaction to the cluster, a client may query the network to
|
|
|
|
|
determine what the transaction's fee will be via the rpc request
|
2022-06-24 14:45:31 -07:00
|
|
|
[getFeeForMessage](/developing/clients/jsonrpc-api#getfeeformessage).
|
2019-09-22 20:38:34 -07:00
|
|
|
|
|
|
|
|
## Fee Parameters
|
|
|
|
|
|
2022-06-22 16:46:37 -07:00
|
|
|
The fee is based on the number of signatures in the transaction, the more
|
|
|
|
|
signatures a transaction contains, the higher the fee. In addition, a
|
|
|
|
|
transaction can specify an additional fee that determines how the transaction is
|
|
|
|
|
relatively prioritized against others. A transaction's prioritization fee is
|
|
|
|
|
calculated by multiplying the number of compute units by the compute unit price
|
|
|
|
|
(measured in micro-lamports) set by the transaction via compute budget
|
|
|
|
|
instructions.
|
