> For the complete documentation index, see [llms.txt](https://docs.kintsu.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kintsu.xyz/overview/introduction.md). # Introduction Welcome to Kintsu! {% hint style="info" %} This documentation will regularly be updated to represent the current state of the project. This version was last updated November 2025. {% endhint %} Kintsu is a Composable Liquid Staking Protocol. Our mission is to boost the GDP of DeFi by allowing users to participate in on-chain activities while also benefitting from the yield-bearing staking that secures the blockchain. Kintsu solves a number of challenges faced by Proof-of-Stake blockchains around liquidity, accessibility, and more. No longer does on-chain liquidity need to compete with L1 staking & security. Traditional staking methods on Proof-of-Stake (PoS) blockchains can hinder participants from engaging in the broader realm of decentralized finance. Once tokens are staked, they become locked and inaccessible for other purposes, limiting users' ability to actively participate in the dynamic DeFi landscape. In PoS networks, security competes with the use cases built on the network such as leveraging decentralized exchanges, diverse lending and borrowing platforms, participating in governance mechanisms, gaming, and exploring other innovative decentralized applications. --- # 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 following URL with the `ask` and `goal` query parameters: ``` GET https://docs.kintsu.xyz/overview/introduction.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 `build a script that syncs our docs to a CMS` 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.