> For the complete documentation index, see [llms.txt](https://docs.stakeease.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stakeease.com/background/restaking-protocols/benefits-of-restaking-protocols.md). # Benefits of Restaking Protocols Restaking protocols bridge the gap between user expectations and EigenLayer's intricate architecture. They offer several advantages: * **Abstraction of Complexity:** Users don't need to grapple with AVS selection, operator analysis, or slashing risks. Restaking platforms handle these technical details behind the scenes, allowing users to focus on their desired risk-reward profile and desired yield. * **Amplified Security:** Through diversification across multiple AVSs and operators, restaking protocols mitigate the impact of potential slashing events, adding an extra layer of protection to user funds. * **Yield Optimization:** Many protocols employ sophisticated algorithms to automatically rebalance user positions and maximize potential returns, further amplifying the benefits of participating in EigenLayer. * **Staying Liquid:** EigenLayer does not provide users with any liquid restaking token against their staked ETH. Kelp issues [rsETH](https://etherscan.io/address/0xA1290d69c65A6Fe4DF752f95823fae25cB99e5A7), Ether.fi issues [eETH](https://etherscan.io/token/0x35fa164735182de50811e8e2e824cfb9b6118ac2), serving as proof of the user's stake. Users can swap these tokens for other tokens on AMMs for instant liquidity or choose to redeem underlying assets through the respective contracts. The advent of restaking protocols marks a crucial development in EigenLayer's evolution. They address the key challenges hindering its wider adoption, making it accessible, secure, and rewarding for everyone. However, the problem of the multi-step staking process and poor UX still exists. In addition to this, with the rising number of restaking platforms, a new problem has emerged. Read the next section for more details. --- # 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.stakeease.com/background/restaking-protocols/benefits-of-restaking-protocols.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.