> 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/challenges-with-restaking-protocols.md). # Challenges with Restaking Protocols The rapid growth of restaking protocols within the EigenLayer ecosystem has been a boon for users, offering a diverse range of options and strategies. However, this abundance of choices has also introduced new challenges: * **Decision Fatigue:** Evaluating multiple platforms with varying features, risk profiles, fee structure, and yield projections can be overwhelming, leading to decision fatigue. Users are faced with the daunting task of comparing and contrasting a multitude of options, often without clear guidance. * **Fragmentationj:** Fragmented liquidity across numerous LRTs hinders seamless engagement on DeFi platforms across chains. * **Yield-searching Hurdles:** To maximize yield, you need to choose where to deposit you LRT among the multiple platforms that are available. You need to weight different parameters like yield offered, risks involved, duration of token lock, etc. before taking this decision. This process requires a lot of time and effort at your end. These challenges highlight the need for a solution that consolidates all the restaking protocols under one umbrella and optimizes the restaking experience for the user. Such a solution should give users access to diversified rewards, by opening up new yield-generating avenues, and reducing LRT fragmentation in the L2s. --- # 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/challenges-with-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.