> For the complete documentation index, see [llms.txt](https://docs.stakestone.io/stakestone-dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stakestone.io/stakestone-dev/introduction.md). # Introduction StakeStone is an omni-chain LST (Liquid Staking Token) protocol aiming to bring native staking yields and liquidity to Layer 2s in a decentralized manner. With its highly scalable architecture, StakeStone not only supports leading staking pools but is also compatible with the upcoming restaking. Meanwhile, it establishes a **multi-chain liquidity market** based on STONE, StakeStone’s native LST, provides users of STONE with more use cases and yield opportunities. StakeStone pioneers the first decentralized solution for liquid staking through an innovative mechanism called the Optimizing Portfolio and Allocation Proposal(OPAP). Unlike traditional approaches that rely on MPC wallets, StakeStone provides full transparency for underlying assets and yields. Meanwhile, OPAP allows optimization of STONE’s underlying assets, ensuring STONE holders to receive optimized staking yields automatically and effortlessly. Based on LayerZero, STONE is a non-rebase OFT (Omnichain Fungible Token) that supports both assets and prices to be transferred across multiple blockchains seamlessly. Developers on Layer2s can effortlessly integrate STONE without additional complexities, leaving it as the most accessible LST ready for mass adoption. Twitter: [https://twitter.com/Stake\_Stone](https://twitter.com/Stake_Stone?s=20) Telegram: Medium: --- # 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://docs.stakestone.io/stakestone-dev/introduction.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.