> 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/why-eigenlayer.md).

# Why EigenLayer?

EigenLayer’s innovative architecture unlocks significant advantages:

* **AVS design flexibility:** Applications have considerable freedom in designing their AVS, enabling creative solutions and innovative use cases.
* **Boosts application security: ️**Shared validator sets across AVSs create a multifaceted defense against malicious actors. This redundancy bolsters AVSs’ resilience, safeguarding user funds and ensuring network stability. 
* **Improves Ethereum scalability:** By bolstering the security of other networks, EigenLayer will facilitate the offloading of traffic from Ethereum, thereby reducing pressure on the mainnet and paving the way for faster transactions and lower fees.
* **Increased participation:** Lower transaction costs and a better UX democratize DeFi, opening doors for new users.
* **Operator empowerment:** Anyone can participate as an operator within the EigenLayer ecosystem and earn rewards directly through operator node operation.
* **Slashing mechanisms:** Robust slashing mechanisms incentivize honest behavior and protect the EigenLayer network from malicious actors. 


---

# 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:

```
GET https://docs.stakeease.com/background/eigenlayer/why-eigenlayer.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.