> 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/eigenlayer-components.md). # EigenLayer Components At its core, EigenLayer leverages the following components: * **Actively Validated Services (AVSs):** These custom-built applications leverage the security of the EigenLayer validator/operator set, performing their own consensus tasks alongside securing the mainnet. * **Shared Operators:** These are individuals or entities running validator nodes within EigenLayer's AVSs. They contribute their validator power to secure multiple applications, earning rewards while boosting network resilience. Imagine dYdX, a popular DeFi platform, wanted to boost its security with EigenLayer. Here's how it might work: * **dYdX as AVS:** dYdX would create its own AVS, a dedicated security layer powered by shared validators. This means anyone staking ETH on EigenLayer could contribute to dYdX's security, earning rewards in the process. * **EigenLayer Operators as Validators:** Operator nodes on EigenLayer could choose to participate in dYdX's AVS, acting as validators. They'd earn rewards for validating dYdX's transactions and securing its platform while also contributing to other AVSs on EigenLayer. --- # 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/eigenlayer-components.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.