> For the complete documentation index, see [llms.txt](https://whitepaper.after-bell.uk/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.after-bell.uk/economics/resolution-fees.md).

# Resolution Fees

Defines the 0.1% fee associated with market resolution.

### Resolution fee

AFTERBELL specifies a **0.1% resolution fee**. It is the protocol fee associated with market resolution.

This fee is conceptually distinct from the 0.5% trading fee. The trading fee is associated with trading activity. The resolution fee belongs to the resolution stage of a market’s lifecycle.

{% hint style="info" %}
The source specifies the 0.1% rate. It does not specify the exact technical charging event or the complete resolution-fee base.
{% endhint %}

### Illustrative calculations

The following figures apply the stated rate to an applicable resolution amount:

| Applicable resolution amount |     Calculation | Resolution fee |
| ---------------------------: | --------------: | -------------: |
|                       $1,000 |   $1,000 × 0.1% |             $1 |
|                      $10,000 |  $10,000 × 0.1% |            $10 |
|                     $100,000 | $100,000 × 0.1% |           $100 |

For example:

```
$1,000 applicable resolution amount × 0.1% = $1 resolution fee
```

These are illustrative calculations, not records of protocol activity. They do not define which amount is applicable in any individual market. The source does not state that all trading volume is subject to a resolution fee. It would be inaccurate to apply the 0.1% rate automatically to the protocol’s $100,000 daily trading-volume model.

### Resolution in market economics

A prediction market does not end when a participant buys a Yes or No outcome. The market eventually reaches a resolution stage. That lifecycle can be expressed economically as:

```
Market → trading → resolution → resolution fee → protocol fee pool → distribution
```

Resolution turns a defined market condition into a verified outcome. The resolution fee therefore belongs to a different protocol event than the trading fee. It recognizes the economic role of closing a market’s outcome cycle without changing the stated trading rate.

The fee model should not be extended beyond the source. It does not specify cancellation fees, withdrawal fees, redemption fees, gas fees, listing fees, or settlement penalties. It also does not specify a separate fee for delayed resolution.

### Resolution dependencies

Resolution relies on the market’s defined condition, relevant price or event data, verification, and resolution logic. These determine whether the market can progress from trading to an outcome.

The source states that an oracle disagreement exceeding 5% pauses the market and can lead to manual resolution. Economically, this matters because resolution is a protocol event. An oracle exception can delay that event. The source does not attach a financial penalty, additional charge, or revenue assumption to such a delay.

This page does not restate the technical resolution process. Its narrower point is that the 0.1% fee is linked to a lifecycle stage whose timing depends on verified resolution. Readers should separate that dependency from the fee calculation itself.

### Contribution to the fee pool

Resolution fees contribute to the same stated protocol fee distribution:

| Destination            | Share |
| ---------------------- | ----: |
| Treasury               |   70% |
| Market Maker Subsidies |   20% |
| Keeper Bot             |   10% |

If the protocol collected $100 in resolution fees, direct allocation arithmetic would be $70 to the treasury, $20 to market-maker subsidies, and $10 to the keeper bot. This is an illustration of the stated percentages. It does not specify timing, custody, or transfer mechanics.

The allocation makes resolution activity part of the protocol’s broader economics. It can contribute to the same pool that supports treasury retention, liquidity bootstrapping, and keeper operations. It does not establish that resolution fees alone fund any particular cost.

### Trading fees and resolution fees

The two fee types should not be collapsed:

| Fee            | Rate | Associated protocol event |
| -------------- | ---: | ------------------------- |
| Trading fee    | 0.5% | Trading activity          |
| Resolution fee | 0.1% | Market resolution         |

The rates are source facts. The totals depend on the relevant underlying activity. A trading-volume calculation can reproduce gross trading-fee revenue. It cannot reproduce resolution-fee revenue without the applicable resolution amount.

This distinction is especially important in break-even analysis. The source provides a daily trading-volume figure and a projected net figure. It does not disclose enough intermediate inputs to calculate daily resolution-fee revenue from daily trading volume.

### Model boundaries

The source states the resolution fee, but it does not define every operational detail. It does not describe a charging trigger, an exact fee base, or how a fee behaves during manual resolution. Those omissions should remain explicit.

Resolution-fee arithmetic is therefore useful only when an applicable resolution amount is known. It should not be presented as realized revenue or as a forecast. Actual resolution activity can vary across markets and time.

AFTERBELL is under development. Smart contracts are not yet audited, with an audit planned before mainnet. The economic model is also subject to liquidity, volume, regulatory, and operational uncertainty. The source provides no evidence that projected fee revenue has been realized.


---

# 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://whitepaper.after-bell.uk/economics/resolution-fees.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.
