> For the complete documentation index, see [llms.txt](https://docs.gage.cash/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gage.cash/pool/the-floor.md).

# The sGAGE floor

Half of creator fees and the full deal fee buy GAGE for standing bids in the GAGE/sGAGE pool.

**50% of received creator ETH buys GAGE for floor liquidity. The other 50% goes to the deployment/operations wallet.** The full 1% deal fee also buys GAGE for these bands, through a separate route with no operations deduction.

`CreatorFeeSplitter` and `FeeFloor` are two names for the same deployed contract. It is the recipient GAGE's creator fees are claimed to from Pons's fee escrow.

## How a creator-fee clip works

1. Claim available Pons creator fees into FeeFloor. Fees can accrue during bonding-curve trading; graduation is not required for the curve-fee route.
2. Open a batch when the gross ETH balance reaches 100 USDG equivalent, valued at the ETH/USDG pool.
3. Send half the processed ETH to operations; use the other half to buy GAGE within the 1% swap impact bound. No caller bounty is deducted.
4. Add the GAGE as one-sided liquidity in the GAGE/sGAGE pool, in a 480-tick-wide band (about 4.9%) just below the current sGAGE price in GAGE.

The keeper performs these calls automatically when the balance, route, gas and price-impact checks allow it. After graduation, conversion of any token-denominated Pons fees still depends on Pons's own fee processing. ETH already claimable from its escrow can be claimed independently.

## The bands

A GAGE-only band is a standing bid: sellers of sGAGE can receive GAGE by trading through it. Later deposits top up the band at the current price or create another one. Existing bands keep their ranges.

FeeFloor owns these NFTs and has no function to transfer them to operations or let the owner withdraw their principal. Once a band has fully converted to sGAGE, anyone may `sweep(tokenId)`: its liquidity is removed and the sGAGE is burned; the GAGE fees it earned stay for the next deposit. `collect(tokenId)` burns collected sGAGE fees and retains GAGE fees for future floor deposits.

Floor bands receive swap fees but no LP emissions. Their backing is finite, and GAGE itself changes in price. This is liquidity support, not a guaranteed minimum price or redemption value.

The floor shows on the Protocol page's pool card as **sGAGE floor**; the GAGE behind it and the number of bands are under the page's **More numbers**. The page leads with the GAGE bought back, as a share of all GAGE.

## Separate from the launch seed

The full-range launch seed is NFT **2126377**, held in the [365-day seed timelock](https://docs.gage.cash/protocol/addresses.md). Its fees compounded into that same NFT until October 2026 and now accrue in it, uncollected; its release date stays fixed. Creator and deal fees create or increase FeeFloor's separate positions in the same GAGE/sGAGE pool.

See [Deal fees and floor liquidity](https://docs.gage.cash/pool/buyback.md) for batching, gas policy and the second funding route.


---

# 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.gage.cash/pool/the-floor.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.
