> For the complete documentation index, see [llms.txt](https://docs.bedrock.technology/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bedrock.technology/bedrock-lrt/introduction/intro-to-liquid-restaking.md). # Intro to Liquid Restaking Restaking, or more formally the rehypothecation of assets securing a network, has recently seen an explosion of interest as stakers rush to generate additional yield on top of their existing PoS staking returns. Introduced by [EigenLayer](https://www.eigenlayer.xyz/) on Ethereum, restaking tokens have seen their [cumulative market cap balloon to over US$4B](https://www.coingecko.com/en/categories/liquid-restaking-tokens)n in less than a year. **By taking on incremental slashing conditions on their staked assets, users can generate increased yield through restaking** in this rapidly growing market. Bedrock aims to provide users with more options and opportunities to earn additional yields. After the successful launch of uniETH, a Liquid Restaking Token with EigenLayer on the Ethereum network in February 2024, we are now introducing the first Liquid Restaking Token with Babylon! Let's dive into the world of LRTs. --- # 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.bedrock.technology/bedrock-lrt/introduction/intro-to-liquid-restaking.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.