> For the complete documentation index, see [llms.txt](https://jigsaw.gitbook.io/jigsaw-protocol/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://jigsaw.gitbook.io/jigsaw-protocol/tokenomics/fee-structure.md). # Fee Structure ### Fee Structure Jigsaw employs a transparent fee model: * A **15% platform fee** is applied to all yield generated, supporting operations and sustainability. * Withdrawing jUSD incurs a **50bps fee**, which contributes to protocol revenue. By rewarding participants and tying incentives to productive outcomes, Jigsaw fosters a robust and sustainable ecosystem. ### Peg Maintenance Jigsaw will apply an increased fee structure to users who have exited the ecosystem by selling jUSD through our liquidity pools. A portion of these fees will be used to incentivize users who purchase and rebalance the jUSD pools. The remaining fees will further strengthen Jigsaw’s protocol-owned liquidity. --- # 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://jigsaw.gitbook.io/jigsaw-protocol/tokenomics/fee-structure.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.