> For the complete documentation index, see [llms.txt](https://docs.memecore.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.memecore.com/memecore/transaction-fees-and-burn.md).

# Transaction Fees & Burn

How gas fees are priced on MemeCore, which part of every fee is burned, and how anyone can verify the burned amount on-chain.

***

## Transaction Fees & Burn

Every transaction on MemeCore pays a gas fee in **$M**. MemeCore implements the EIP-1559 fee market from the genesis block, so each fee is split into two parts:

* a **base fee**, set by the protocol and **burned**, and
* an optional **priority fee (tip)**, set by the sender and paid to the PoM reward contract.

```
gas fee           = gasUsed × effectiveGasPrice
effectiveGasPrice = baseFeePerGas + priorityFeePerGas
burned per tx     = gasUsed × baseFeePerGas
```

{% hint style="info" %}
**Example** — A simple $M transfer uses 21,000 gas. At the minimum base fee of 15 Gwei, the transaction burns `21,000 × 15 Gwei = 315,000 Gwei = 0.000315 M`. Any priority fee is paid to the PoM reward contract on top of that.
{% endhint %}

### Base fee

The base fee is the minimum price per unit of gas required for a transaction to be included in a block. It is not chosen by users: the protocol calculates it for every block from the gas used by the previous block.

* If the previous block used **more** gas than the target, the base fee goes **up**.
* If it used **less** gas than the target, the base fee goes **down**.
* The change is capped at **±12.5% per block**.
* The base fee never drops below the **minimum base fee** (see [Fee parameters](#fee-parameters)).

```
gasTarget        = gasLimit / ElasticityMultiplier
delta            = parentBaseFee × (parentGasUsed − gasTarget) / gasTarget / BaseFeeChangeDenominator
nextBaseFee      = max(parentBaseFee + delta, MinBaseFee)
```

{% hint style="info" %}
This is a simplified version. See [EIP-1559](https://eips.ethereum.org/EIPS/eip-1559) and [`consensus/misc/eip1559/eip1559.go`](https://github.com/memecore-foundation/Go-MemeCore/blob/master/consensus/misc/eip1559/eip1559.go) in the MemeCore client for the exact implementation.
{% endhint %}

### Priority fee

The priority fee (tip) is an optional amount on top of the base fee. It is **not burned**. Priority fees flow into the reward contract together with the block reward and are distributed to validators and delegators.

### Fee burn

#### What is burned

| Fee component                          | Burned?                                           | Since                |
| -------------------------------------- | ------------------------------------------------- | -------------------- |
| Base fee (`gasUsed × baseFeePerGas`)   | **Yes, 100%**                                     | Genesis (block 0)    |
| Blob fee (`blobGasUsed × blobBaseFee`) | **Yes, 100%**                                     | CanPraTree hard fork |
| Priority fee (tip)                     | No — paid to the PoM reward contract (`coinbase`) | —                    |

#### How the burn works

The base fee of every block is deducted from the sender and **is not credited to any address** — not to the reward contract, not to a treasury, and not to a burn address such as `0x…dEaD`. The amount simply leaves the circulating supply at the protocol level, in the same way as on Ethereum after the London upgrade.

```
burned per block = block.gasUsed × block.baseFeePerGas   (+ blobGasUsed × blobBaseFee after CanPraTree)
```

{% hint style="warning" %}
**Blob fees** — Blob-carrying transactions (EIP-4844) are supported from the CanPraTree hard fork, and their blob fee is burned as well. As of the latest measurement no blob transactions have been observed on mainnet, so blob fees have not yet contributed to the burned total.
{% endhint %}

### Fee parameters

<table><thead><tr><th width="265.8984375">Parameter</th><th width="131.39453125">Value</th><th>Notes</th></tr></thead><tbody><tr><td>Fee market</td><td>EIP-1559</td><td>Active from genesis (<code>LondonBlock = 0</code>)</td></tr><tr><td>Minimum base fee</td><td><strong>15 Gwei</strong></td><td>Since GasTree hard fork. <strong>1,500 Gwei</strong> before</td></tr><tr><td>Max base fee change per block</td><td><strong>±12.5%</strong></td><td><code>BaseFeeChangeDenominator = 8</code></td></tr><tr><td>Elasticity multiplier</td><td><strong>2</strong></td><td>Gas target = gas limit ÷ 2 (<code>DefaultElasticityMultiplier</code>)</td></tr><tr><td>Base fee destination</td><td>Burned</td><td>Not credited to any address</td></tr><tr><td>Blob fee destination</td><td>Burned</td><td>Since CanPraTree</td></tr></tbody></table>

Source: [`params/protocol_params.go`](https://github.com/memecore-foundation/Go-MemeCore/blob/master/params/protocol_params.go), [`consensus/misc/eip1559/eip1559.go`](https://github.com/memecore-foundation/Go-MemeCore/blob/master/consensus/misc/eip1559/eip1559.go) in the MemeCore client.

### Verify the burn yourself

Because burned fees are not sent to any address, you verify the burn by recomputing it from block headers rather than by checking a balance. Every MemeCore block header includes `gasUsed` and `baseFeePerGas`.

```bash
RPC=https://rpc.memecore.net
BLOCK=7850000

# Burned in a single block (wei)
GAS=$(cast block $BLOCK --field gasUsed --rpc-url $RPC)
FEE=$(cast block $BLOCK --field baseFeePerGas --rpc-url $RPC)
cast from-wei $(echo "$GAS * $FEE" | bc)   # → amount in M
```

```javascript
import { JsonRpcProvider, formatEther } from "ethers";

const provider = new JsonRpcProvider("https://rpc.memecore.net");

async function burnedInRange(from, to) {
  let total = 0n;
  for (let n = from; n <= to; n++) {
    const b = await provider.getBlock(n);
    total += b.gasUsed * (b.baseFeePerGas ?? 0n);
  }
  return formatEther(total); // in M
}
```


---

# 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.memecore.com/memecore/transaction-fees-and-burn.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.