> For the complete documentation index, see [llms.txt](https://killswitchofficial.gitbook.io/killswitch/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://killswitchofficial.gitbook.io/killswitch/feature/boost/jellopy.md). # Jellopy **JellopyTokens** are like receipts, you will receive **Jellopy "KSW" tokens** from depositing into the pool. As a pool generates profit, the number of JellopyTokens in your wallet remains the same while receiving rewards as tokens from partnered platforms. ![example using the TWX pool](/files/v8AYGi2xBl619OwupA5z) If users want to withdraw, users will need this "receipt" **JellopyTokens** which users will hand in to redeem the deposited tokens and yield. It is essential to hold onto those **JellopyTokens** which means that users should deposit receipts and should not sell or exchange them with strangers, otherwise users will lose possession of staked assets in the pool. If you already have **JellopyTokens** in your pool, you can stake to get rewards without additional investments. Likewise for withdrawing liquidity, users must unstake in the respective "boost" pool first. --- # 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://killswitchofficial.gitbook.io/killswitch/feature/boost/jellopy.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.