> For the complete documentation index, see [llms.txt](https://stonkmarket.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://stonkmarket.gitbook.io/docs/smart-contracts/stonk-fee-locker.md).

# StonkFeeLocker

The fee locker is where trade fees accrue and where beneficiaries claim them. The [StonkHook](/docs/smart-contracts/stonk-hook.md) withholds 1% from the backing-asset leg of every swap and credits it here, split three ways; each beneficiary later withdraws their own balance.

## Overview

| Property | Value                |
| -------- | -------------------- |
| Contract | `StonkFeeLocker.sol` |

| Network                | Address                                                                                                                                  |
| ---------------------- | ---------------------------------------------------------------------------------------------------------------------------------------- |
| Base mainnet (8453)    | [`0xbA368cC2829f87893133C4821f2066c4292ce861`](https://basescan.org/address/0xbA368cC2829f87893133C4821f2066c4292ce861)                  |
| Robinhood Chain (4663) | [`0x122C20f114Bb6c78299E5CB78A765Bdf6D942A46`](https://robinhoodchain.blockscout.com/address/0x122C20f114Bb6c78299E5CB78A765Bdf6D942A46) |

Fees accrue in the locker on the chain the token was launched on; claims are per chain.

## What It Holds

Fees are always denominated in each token's **backing asset** — WETH or USDC on Base, WETH or USDG on Robinhood Chain — never the launched token. The locker tracks, per token and per beneficiary, how much has been credited and how much has been claimed, so anyone can withdraw exactly what they are owed and no more.

## The Split

Every 1% of asset-leg fee is credited in the shares recorded for that token at launch:

| Share               | Recipient                                                                                                               | Referred | Unreferred |
| ------------------- | ----------------------------------------------------------------------------------------------------------------------- | -------- | ---------- |
| Creator             | The token's deployer                                                                                                    | 10%      | 10%        |
| Platform referrer   | The listed platform that referred the launch                                                                            | 10%      | —          |
| Treasury (protocol) | [`0x72338634020f2BFcbaCa591B8CB67ECe577A3b02`](https://basescan.org/address/0x72338634020f2BFcbaCa591B8CB67ECe577A3b02) | 80%      | 90%        |

When a launch has no listed platform referrer, the platform's 10% folds into the treasury, so the effective split is **10 / 90**.

## Claiming

Fees **accrue** as trading happens and sit in the locker until claimed. Each beneficiary — creator, platform referrer, or treasury — withdraws their own accrued balance for a given token; the withdrawal moves the amount from "owed" to "claimed."

## Conservation

The locker's accounting is conservative by construction: for every token and asset,

```
credited == claimed + owed
```

Every unit the hook ever credits is either already withdrawn or still claimable — nothing is created or lost inside the locker.


---

# 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://stonkmarket.gitbook.io/docs/smart-contracts/stonk-fee-locker.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.