> For the complete documentation index, see [llms.txt](https://docs.shuffle.family/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.shuffle.family/fees/shuffle-fees.md). # $SHUFFLE Trading fee SHUFFLE’s configured **PONS trading fee is 4%**. Collected revenue supports the Shuffle Index and the team. ## Fee split Half goes to the Shuffle Index as WETH backing. The other half goes to the team; see [Fee flows and buybacks](/fees/where-fees-go.md). ## How the basket receives its share Every hour, an automated job collects the fees from PONS and sends half to the index as WETH. No new XSHUFFLE is minted, so every existing share is backed by more. There is no direct wallet payout. A later rebalance can invest that WETH, subject to execution checks. ## Does this fee buy back SHUFFLE? No, SHUFFLE buybacks are funded by **Shuffle Index entry and exit fees**. --- # 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.shuffle.family/fees/shuffle-fees.md?ask=&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.