# Actively Validated Services (AVS)

Several protocols have already expressed interest in joining the Eigenlayer AVS ecosystem. Let's take a closer look at some of the prominent AVSs.

* **EigenDA**: This AVS is being developed by EigenLabs. It focuses on hyperscale data availability for any execution layer. EigenDA is designed to scale with each added node, which helps to reduce the overall load from Eigenlayer Node operators. Notable EigenDA adopters include Celo, Mantle, Fluent and more.
* **Espresso Systems**: Creating a shared sequencer that enables rollup decentralization, improved interoperability, and a scalable DA layer. Espresso captures value through cross-rollup MEV. The project is backed by Yale's Ben Fisch and investors like Greylock and Sequoia.
* **Lagrange**: Known for ZK-powered cross-chain messaging using state committee, leveraging EigenLayer restaking for dynamic scaling of state proof security.
* **Omni Network**: It is an L1 built using Cosmos SDK for cross-rollup messaging. It provides cheaper transaction fees and fast-finality. They are supported by a Harvard-origin team and investors such as Pantera.
* **Blockless**: Delivers ZK verifiable serverless functions, optimizing decentralized applications. It uses EigenLayer to secure transaction consensus.
* **Hyperlane**: Employs EigenLayer to safeguard interchain application developers' messages from Ethereum using restaked economic security.


---

# Agent Instructions: 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.bedrock.technology/eigenlayer/ecosystem/actively-validated-services-avs.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.