> For the complete documentation index, see [llms.txt](https://docs.usetrickle.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.usetrickle.xyz/the-protocol/what-is-trickle.md). # What is Trickle Trickle is a passive savings protocol built for **HyperEVM and Solana**. Every time you make an eligible swap, Trickle automatically sets aside 1% into savings in the background. On HyperEVM, that applies to swaps involving HYPE/WHYPE, USDC, or USDT0; on Solana, it applies to swaps involving SOL/WSOL or USDC. You trade exactly as you always do. There is nothing new to learn, nothing to manage after setup, and no habit to build. Your savings accumulate automatically because you trade, and you trade anyway. The idea is simple: active traders move meaningful volume every day, and a consistent 1% slice of that activity can compound into a real position over time. Trickle turns normal trading flow into automatic accumulation, whether you want to save in a stable asset, the native asset, or the collected token itself. Trickle starts as a savings automation layer. The savings habit is the foundation, and what you do with the accumulated position expands over time. Who it is for: active traders on HyperEVM and Solana who want to build a savings position without changing how they trade. If you regularly swap eligible assets on either chain, Trickle works with near-zero friction after a one-time setup. Trickle is built as a multichain product: one savings experience, adapted to each chain’s native execution model. On HyperEVM, Trickle uses Permit2; on Solana, it uses SPL delegate authority, while keeping the same core behavior of automatically redirecting 1% of eligible swaps into savings. --- # 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.usetrickle.xyz/the-protocol/what-is-trickle.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.