> 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/buyback.md).

# Deal fees and floor liquidity

The full 1% deal fee buys GAGE and adds floor liquidity in GAGE/sGAGE.

The launch configuration sends the entire **1% deal fee** to GAGE/sGAGE floor liquidity. The deployed route is:

**DealVault → FeeSink → DealFeeRouter → FeeFloor → GAGE/sGAGE floor bands.**

The native engines (V2 and V3) credit their fees to DealFeeRouter directly. DealFeeRouter converts USDG to ETH, buys GAGE, and deposits that GAGE into FeeFloor. This route has no operations deduction and pays no caller bounty. It does not swap GAGE into sGAGE or burn the purchased GAGE. The old standalone Buyback contract was not deployed for this launch. FeeSink retains the historical `BUYBACK` enum and `setBuyback` naming, but its configured destination is DealFeeRouter.

## Accumulation and execution

The trigger is **100 USDG** accumulated in the deal-fee bucket. Creator fees have a separate 100 USDG-equivalent trigger on the gross ETH balance before their 50:50 split. Once a batch opens, smaller remaining clips can complete below the trigger.

The keeper limits purchases to 1,000 USDG per clip, reduces clips to respect the 1% price-impact bound, and waits when estimated gas would exceed 1% of the amount being converted. The on-chain thresholds are owner-adjustable within 10–10,000 USDG. Keeper gas limits and clip sizing are operating policy; they do not mean every caller must use that same policy.

Execution therefore happens in batches, not on every trade or deal. Anyone may run a batch (`DealFeeRouter.process`); each swap takes its minimum from the pools' price in the same transaction, at most 1% from it, so a batch buys GAGE at the pools' price of that moment, and someone who moves GAGE's price first can make it buy fewer GAGE. A small balance, unfavorable price impact, an unavailable route or expensive gas can delay it.

## Where the GAGE goes

GAGE becomes one-sided liquidity that bids for sGAGE in the same pool. This supports sGAGE in GAGE terms, not a guaranteed dollar price. Once a band has fully converted into sGAGE, it can be swept and that sGAGE burned. See [The sGAGE floor](https://docs.gage.cash/pool/the-floor.md) for the band mechanics and [Contract addresses](https://docs.gage.cash/protocol/addresses.md) for the deployed route.

## V2 fees

[V2](https://docs.gage.cash/start-here/v2.md) adds reclaim-right sales, lender-position sales and cash-out alongside loan activation. All four fees use the same GAGE-only floor route:

| Fee                                                                         | Calculation                                                                                |
| --------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------ |
| **1% origination**                                                          | Gross funded principal, charged once when the loan is funded                               |
| **1% reclaim-right sale** (the earlier engines; none on the Intent cores)   | The price paid for the right through Gage, deducted from the seller's proceeds             |
| **1% lender-position sale** (the earlier engines; none on the Intent cores) | The price paid for the selected quarters through Gage, deducted from the seller's proceeds |
| **0.5% cash-out**                                                           | Remaining cash after repaying the full cap and financing costs                             |

Normal full-cap repayment has no additional cash-out fee.


---

# 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/buyback.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.
