> For the complete documentation index, see [llms.txt](https://lfg314.gitbook.io/lfg314/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://lfg314.gitbook.io/lfg314/revenue-sharing.md).
# Revenue Sharing
Sharing
You need to hold a minimum of 10 LFGAI tokens, with no staking or lockup required—simply hold the tokens in your wallet.
Revenue share is distributed in ETH by default.
To claim rewards, you must accumulate a minimum of 0.1 ETH. Claiming rewards retrieves all available unclaimed rewards.
During each reward epoch (occurring every 2 hours), you can sell or transfer up to 200 LFGAI without penalty. Exceeding this amount forfeits all unclaimed rewards back into the rewards pool, except for referral rewards.
Auto-compounding is enabled by default, automatically swapping your ETH rewards for LFGAI, thereby increasing your revenue share. You can disable this feature if desired.
Connect your wallet to the rewards dashboard to claim your rewards.
40% of all bot transaction fees and 2% of all LFGAI volume traded contribute to the revenue pool.
We currently only provide guaranteed support for the Metamask wallet. If you encounter issues, ensure that any other web wallet extensions besides Metamask are disabled in your browser (e.g., Phantom wallet).
ETH earned from revenue sharing is automatically exchanged for LFGAI. Accumulated LFGAI contributes to your revenue share calculation without requiring manual claiming.
LFGAI acquired via auto-compounding incurs a 0% tax rate, in contrast to the standard 4%.
Auto-compounded rewards can be claimed after accumulating just 1 LFGAI.
To manage your rewards settings, access the rewards dashboard, and click on the "User Rewards Settings" button located in the top right corner, then toggle the desired setting.
---
# 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://lfg314.gitbook.io/lfg314/revenue-sharing.md?ask=&goal=
```
`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.