Actively Validated Services (AVSs)

Launching a new decentralized protocol has traditionally faced a massive hurdle known as "bootstrapping trust." To create a new oracle network, sidechain, or bridge, developers historically had to launch a new token, convince a distributed network of validators to buy and stake that token, and maintain enough economic value to prevent attacks. This is expensive and inefficient.

Actively Validated Services (AVS) change this equation. Instead of building a new trust network from scratch, an AVS "rents" security from an existing, highly secure blockchain like Ethereum. This concept, popularized by protocols like EigenLayer, allows developers to tap into the billions of dollars already staked on Ethereum to secure their own applications.

However, while AVSs lower the barrier to entry for security, they introduce new complexities regarding data accuracy and interoperability. This is where Chainlink plays a pivotal role, providing the industry-standard data and cross-chain infrastructure that AVSs need to operate safely and connect with the broader Web3 economy.

What Is an Actively Validated Service (AVS)?

An AVS is any system that requires distributed validation for its verification logic but chooses to use shared security rather than its own independent consensus mechanism.

Think of it like cloud computing. In the past, every internet startup had to build its own physical server farm (bootstrapping its own security). Today, startups use Amazon Web Services (AWS) to rent server space. Similarly, an AVS uses a "Shared Security" marketplace to rent validation services.

The most common examples of AVSs include:

• Data Availability Layers: Systems that store blockchain transaction data cheaply.
• Oracle Networks: Protocols that verify offchain data.
• Bridges: Systems that validate messages between blockchains.
• Sequencers: Services that order transactions for Layer 2 rollups.

How AVSs Work: The Restaking Mechanism

The engine powering most AVSs is a mechanism called restaking.

In the traditional model, an Ethereum validator stakes 32 ETH to secure the Ethereum network. In the AVS model, that same validator can "restake" their 32 ETH. This means they pledge their staked ETH to secure both Ethereum and the new AVS simultaneously.

The process involves three key parties:

1. The AVS Developer: Builds a protocol (e.g., a new bridge) but doesn't want to launch a new token for security.
2. The Staker/Validator: Agrees to run the AVS software in exchange for additional yield. They accept the risk that if they act maliciously or fail to validate correctly, their staked ETH could be "slashed" (penalized).
3. The Operator: The technical entity managing the node infrastructure that performs the actual validation tasks for the AVS.

Benefits of the AVS Model

The AVS model offers significant efficiency improvements for the blockchain industry.

• Lower Capital Costs: New projects do not need to raise millions of dollars to incentivize a validator set. They can tap into existing Ethereum security immediately.
• Increased Yield for Stakers: ETH holders can earn rewards from multiple sources (Ethereum execution layer + AVS fees) without needing to move their capital.
• Unbundled Trust: Developers can focus on building their application logic without worrying about the underlying validator infrastructure.

Risks and Challenges

While promising, the AVS market is nascent and carries distinct risks.

• Slashing Risks: If an AVS has a bug in its code, honest validators might be accidentally penalized (slashed), losing a portion of their ETH.
• Centralization: validating multiple AVSs requires powerful hardware. If only large, institutional node operators can afford this hardware, the network could become centralized.
• Systemic Risk: If a major AVS fails, it could theoretically impact the security of the underlying Ethereum mainnet if a large portion of staked ETH is slashed simultaneously.

The Role of Chainlink in the AVS Ecosystem

While an AVS provides a security model, it does not automatically solve the problems of data access or connectivity. A "restaked" protocol still needs to know the price of Bitcoin or how to send a token to Solana.

Chainlink supports the AVS ecosystem by providing the necessary infrastructure for these services to be useful.

• Reliable Data Inputs: Many AVSs are designed to facilitate DeFi or financial applications. These applications rely on the Chainlink Data Standard to receive accurate, tamper-proof market data. Without high-quality data, even a securely validated AVS cannot function correctly.
• Cross-Chain Interoperability: AVSs are often specific to one ecosystem. The Chainlink Interoperability Standard (CCIP) allows AVSs to communicate securely with other blockchains, enabling them to serve a global market rather than a siloed user base.
• The Original AVS: Conceptually, Chainlink Decentralized Oracle Networks (DONs) were the first proven "actively validated services." Chainlink nodes have been performing offchain computation and validating it onchain for years, securing tens of trillions in transaction value. Chainlink's architecture serves as the blueprint for how distributed validation should be managed at scale.

Future Outlook

The rise of AVSs signals a shift toward a modular blockchain future. We are moving away from monolithic chains that do everything, toward a stack of specialized services—one layer for settlement (Ethereum), one for data availability (EigenDA), and one for real-world connectivity (Chainlink).

As this ecosystem matures, the distinction between "blockchains" and "applications" will blur. The Chainlink Runtime Environment (CRE) will play a critical role here, orchestrating workflows across these various AVSs and blockchains, ensuring that despite the fragmentation of underlying technology, the user experience remains unified and secure.