> For the complete documentation index, see [llms.txt](https://docs.novarpc.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.novarpc.xyz/nova-rpc/why-use-a-private-mempool/understanding-mev/fee-markets.md).

# Fee Markets

With the goal of further improving the user experience, Ethereum's fee market was overhauled with the [EIP-1559 upgrade](https://eips.ethereum.org/EIPS/eip-1559), replacing the first price auction system (highest bidder wins) with a system that encompasses the following:

* **Base fee:** Algorithmically determined by the protocol itself, base fees represent the minimum fee for your transaction to be considered valid, and are burned upon inclusion.
* **Priority Fee (Tip):** Users can optionally add a tip to incentivize validators to prioritize their transactions. This is especially relevant when the network is busy since block space is limited, or when a contentious state change exists.

Whilst EIP-1559 attempted to improve the accuracy and predictability of Ethereum transaction fees, the capacity constraints of blockspace mean rank and inclusion latency remain dependant on tips users pay.&#x20;

For this reason, price discovery for blockspace remains inefficient...


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.novarpc.xyz/nova-rpc/why-use-a-private-mempool/understanding-mev/fee-markets.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
