> 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/eigenlayer/challenges-with-eigenlayer.md). # Challenges with EigenLayer While EigenLayer's staking numbers are booming, many might not realize they still need to delegate their restaked ETH to operators. Choosing wisely is crucial - a subpar operator node can result in your ETH getting slashed, and even good operators running on strict AVSs can be susceptible to slashing. * **Operator and AVS selection:** Each Actively Validated Service (AVS) offers unique security levels and rewards, but deciphering them requires patience and knowledge. Strict slashing rules mean understanding where operators use your staked ETH is crucial. * **Unintuitive User Experience:** As mentioned above, staking on EigenLayer is not straightforward. Users need to delegate their tokens to an operator to start earning rewards. To solve these problems, a multitude of restaking protocols have surfaced. 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/eigenlayer/challenges-with-eigenlayer.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.