> For the complete documentation index, see [llms.txt](https://whitepaperv2.pwrlabs.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaperv2.pwrlabs.io/transaction-fee-model.md).

# Transaction Fee Model

Since PWR Chain is not a smart contract platform, transaction fees are primarily determined by the size of the transaction and the signature scheme used. The total transaction fee is calculated as follows:

*Transaction Fee = (Fee Per Byte × Transaction Size) + Signature Verification Fee*

1. **Fee Per Byte**
   * Reflects the cost per byte of data within a transaction.
   * The exact base value is determined before PWR Chain’s mainnet launch.
   * In case of congestion, users can choose to pay a higher rate to prioritize their transactions.
2. **Signature Verification Fee**
   * Represents the computational effort required to verify a signature.
   * Because PWR Chain supports multiple signature schemes—each varying in complexity—the fee differs accordingly.
   * Each fee amount is predefined based on how much processing power is required to verify a given signature type.

This structure allows PWR Chain to accurately attribute costs to the resources consumed, ensuring that network participants pay fees commensurate with the complexity and size of their transactions.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://whitepaperv2.pwrlabs.io/transaction-fee-model.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.