Redefining AVS: From Actively Validated to Autonomous Verifiable Services

This week, we updated our documentation to reflect an evolution in our thinking about AVSs. These services are about more than the act of validation. What developers are building are Autonomous Verifiable Services.

When we introduced the concept of Actively Validated Services (AVS) back in February 2023, we intended to describe how EigenLayer ensured correctness and security for services built in decentralized environments. Since its initial Mainnet launch, EigenLayer has empowered developers to quickly build scalable, secure services by leveraging decentralized, shared security, freeing them to focus on innovation rather than trust and infrastructure. 

As our understanding of this technology’s potential has grown, we realized there is a better way to describe what AVSs represent.

Why the Change?

"Actively Validated" describes how these services are continuously monitored and validated to ensure they function correctly. The "Autonomous Verifiable" framing highlights two critical characteristics of these services: 

1. Autonomous: These services run on their own. Once deployed, they don’t rely on any central authority or ongoing intervention.
2. Verifiable: If a commitment is violated, it can be detected, tested, and verified, triggering consequences like slashing to maintain system integrity.

Combining autonomy and verifiability creates a powerful dynamic, which is precisely what makes EigenLayer unique. It’s not just about building services; it’s about building services that are open, scalable, and secure by design.

Note: There’s no technical change to the implementation at this time - we are simply evolving our terminology to better reflect the potential of these services. 

Let’s Break It Down: Autonomous + Verifiable

Autonomous: Permissionless and Self-Sustaining

When we say these services are autonomous, we mean they’re designed to operate without constant supervision. They’re open to anyone who wants to participate. You can stake, run, and contribute to them without needing special permission.

This autonomy isn’t just a technical feature—it’s a principle. It ensures that innovation remains open and that no single party controls the system’s functionality. This is a core aspect of what makes decentralized ecosystems so powerful.

Verifiable: Ensuring Safety and Correctness

"Verifiable" means that any deviation from expected behavior can be objectively identified. Whether a service fails to meet its promises or engages in malicious behavior to exploit the system, these violations can be verified and penalized.

In EigenLayer, this often involves operator ejection or slashing mechanisms. If a service violates its conditions, participants who allocate stake to it can be penalized, ensuring that bad behavior has real consequences. This keeps the ecosystem honest and secure.

A Look Ahead

As we continue to refine and expand the role of Autonomous Verifiable Services with EigenLayer, this shift in definition will help set the tone for the future of decentralized infrastructure more broadly. Our goal is to create systems that don’t just work today but can adapt and thrive in the evolving landscape of Web3.

We believe this change better reflects that vision, and we’re excited to see how developers, stakers, and consumers interact with these new and improved AVS-powered services.

Thanks for being part of this journey. Let’s keep building!