Free 30-min Web3 Consultation
Book Consultation
Smart Contract Security Audits
View Audit Services
Custom DeFi Protocol Development
Explore DeFi
Full-Stack Web3 dApp Development
View App Services
Free 30-min Web3 Consultation
Book Consultation
Smart Contract Security Audits
View Audit Services
Custom DeFi Protocol Development
Explore DeFi
Full-Stack Web3 dApp Development
View App Services
Free 30-min Web3 Consultation
Book Consultation
Smart Contract Security Audits
View Audit Services
Custom DeFi Protocol Development
Explore DeFi
Full-Stack Web3 dApp Development
View App Services
Free 30-min Web3 Consultation
Book Consultation
Smart Contract Security Audits
View Audit Services
Custom DeFi Protocol Development
Explore DeFi
Full-Stack Web3 dApp Development
View App Services
LABS
Glossary

Restaked Security

A security model where the economic stake securing a primary blockchain is 'restaked' to provide cryptoeconomic security to additional services like modular chains or AVSs.
Chainscore © 2026
definition
BLOCKCHAIN CONSENSUS

What is Restaked Security?

A paradigm for reusing staked assets to secure multiple decentralized services, pioneered by EigenLayer.

Restaked security is a cryptoeconomic mechanism that allows staked assets, such as ETH, to be "restaked" to provide security and cryptoeconomic guarantees to other software modules, called Actively Validated Services (AVS). This creates a shared security marketplace where services like new consensus layers, data availability networks, and oracles can bootstrap trust without needing to bootstrap their own token and validator set from scratch. The core innovation is the ability to extend Ethereum's robust staking base to secure a broader ecosystem.

The mechanism works by enabling Ethereum validators to opt-in to additional slashing conditions by restaking their staked ETH. When a validator restakes, they run the software for an AVS and face penalties (slashing) if they act maliciously or fail to perform their duties for that service. This creates a powerful economic alignment: the validator's primary ETH stake is now at risk for their performance across multiple networks. This model is often contrasted with sovereign security, where each network maintains its own independent validator set and token.

Key components of the restaked security model include the restaking pool, where assets are committed, the AVS registry, and a delegation layer that allows liquid staking token (LST) holders to delegate their stake to operators who run the node software. This separation of capital provision (delegators) and node operation (operators) allows for specialization and broader participation. The security budget for an AVS is a function of the total economic value (the cryptoeconomic security) that is restaked and delegated to operators serving it.

A primary use case is securing bridges and oracles, which are critical infrastructure often targeted by exploits. By leveraging Ethereum's massive stake, these services can achieve a much higher security guarantee. Other applications include shared sequencers for rollups, data availability layers, and light client networks. This model aims to solve the security fragmentation problem in a multi-chain ecosystem, where new chains often launch with insufficient validator decentralization or stake.

The restaking model introduces new risk vectors, primarily correlated slashing and centralization pressures. Correlated slashing occurs if a fault or attack on one AVS triggers slashing that cascades to others, potentially destabilizing the entire ecosystem. There is also a concern that a small set of large operators could dominate the market for running AVSs, creating centralization risks. These trade-offs between pooled security and systemic risk are central to the design and critique of restaking protocols like EigenLayer.

how-it-works
MECHANISM

How Does Restaked Security Work?

Restaked security is a cryptoeconomic mechanism that extends the security properties of a primary proof-of-stake blockchain, like Ethereum, to other networks and services.

Restaked security, also known as restaking, is a process where validators on a proof-of-stake (PoS) blockchain can re-pledge their already staked assets—such as ETH—to secure additional services beyond the base consensus layer. This is achieved by allowing staked assets to be "opted-in" to new validation duties for actively validated services (AVS), which can include rollups, oracles, bridges, and other middleware. The core innovation is the creation of a cryptoeconomic security marketplace, where AVSs can lease security from the established validator set of a major chain like Ethereum, rather than bootstrapping their own.

The mechanism operates through a slashing framework. When a validator opts their staked ETH into securing an AVS, they enter into a new set of commitments. If they act maliciously or fail to perform their duties for that AVS—such as signing incorrect data for an oracle—they can be slashed, losing a portion of their original staked ETH. This slashing risk is what cryptoeconomically aligns the validator's behavior with the correct operation of the new service. Protocols like EigenLayer pioneered this model, creating a standardized set of smart contracts and interfaces for validators and AVSs to interact.

This model offers significant efficiency gains. For AVS developers, it eliminates the need to bootstrap a new token and validator ecosystem from scratch, a process known as the "trust bootstrap" problem. For stakers, it provides a way to earn additional rewards (paid in the AVS's native token or other forms) on top of their base staking yield, a concept called "pooled security". However, it introduces new complexities, including slashing risk concentration and the challenge of designing correct fault proofs for diverse services.

The security guarantees are not automatic; they are carefully scoped. An AVS defines its own fork-choice rules and validation logic, and the restaking protocol simply enables slashing enforcement based on those rules. The strength of the security is directly proportional to the total value restaked by honest validators, creating a powerful disincentive for attacks. This makes restaking particularly suitable for services where the cost of corruption must be extremely high, such as cross-chain bridges or data availability layers.

In practice, restaked security is transforming the modular blockchain landscape. It allows for the creation of highly secure, specialized networks—often called "EigenLayer AVSs"—that leverage Ethereum's robust validator set. This shifts the security paradigm from isolated, fragmented networks to a more interconnected and capital-efficient ecosystem, where the strongest security layer can be shared as a reusable resource across the decentralized web.

key-features
MECHANISMS & ARCHITECTURE

Key Features of Restaked Security

Restaked security is a modular framework that allows blockchain networks to share cryptoeconomic security from a base layer, such as Ethereum. These are its core operational components.

04

Slashing & Cryptoeconomic Security

Slashing is the enforced penalty mechanism that underpins the security of the restaking ecosystem. It ensures operators have "skin in the game."

  • Process: If an operator acts maliciously or goes offline for a secured AVS, a portion of their (and their delegators') restaked assets can be slashed (burned).
  • AVS-Specific Slashing: Each AVS defines its own slashing conditions in a smart contract, which must be approved by the EigenLayer governance.
  • Security Guarantee: The total value slashed for a fault is proportional to the total value restaked to that AVS, creating a strong economic disincentive for attacks.
05

Shared Security Pool

The shared security pool refers to the aggregated capital (restaked ETH) that is made available to be allocated across multiple AVSs. This is the core resource of the system.

  • Capital Efficiency: A single staking deposit can secure Ethereum and multiple AVSs simultaneously, improving capital efficiency for stakers.
  • Dynamic Allocation: Operators choose how to allocate their backing across different AVSs, creating a market-driven security budget.
  • Scalability: The model allows for the horizontal scaling of secure services without linearly increasing the total amount of capital locked in the ecosystem.
06

Interoperability & Modularity

Restaked security is inherently modular, separating the security layer from the application logic layer. This enables unprecedented interoperability between blockchain components.

  • Modular Stack: AVSs can be seen as modular "plug-ins" for security, each providing a specialized service (DA, oracles, etc.) to rollups and other chains.
  • Composability: A single rollup can use multiple AVSs—e.g., one for data availability and another for a fast finality bridge.
  • Ecosystem Effect: Reduces fragmentation by allowing new projects to build on a unified security base, fostering a cohesive multi-chain environment.
examples
RESTAKED SECURITY

Examples and Implementations

Restaked security is implemented through various protocols and mechanisms that allow validators to rehypothecate their staked ETH to secure additional networks. This section details the primary models and key projects in the ecosystem.

06

Risk & Slashing Conditions

A critical implementation detail is defining and enforcing slashing conditions for each AVS. This is how the restaked capital is put at risk to ensure honest validation.

Implementation Process:

  1. AVS Definition: Each service specifies its own fault proofs and slashing logic (e.g., double-signing, data withholding).
  2. Operator Opt-in: Operators choose which AVS slashing conditions to subject themselves to.
  3. Delegation: Restakers delegate to operators, inheriting their chosen risk profile.
  4. Enforcement: A Slasher contract, often run by the AVS, submits proof of a fault to EigenLayer's Manager contract to trigger slashing.

This modular slashing framework is the core security mechanism of the system.

visual-explainer
MECHANISM

Visualizing the Restaked Security Flow

A step-by-step breakdown of how capital is secured, delegated, and utilized within a restaking protocol to provide cryptoeconomic security to multiple services.

The restaked security flow begins when a user, known as a staker, deposits their liquid staking tokens (e.g., stETH, rETH) or native ETH into a restaking protocol like EigenLayer. This action, called restaking, creates a new cryptographic commitment. The staker then delegates this restaked capital to one or more operators, who are node operators responsible for running the software of actively validated services (AVSs) such as new blockchains, oracles, or bridges.

Upon delegation, the operator's potential to earn fees and rewards from the AVS is balanced by the cryptoeconomic security now backing it. If the operator acts maliciously or fails in its duties (e.g., going offline, double-signing), the underlying restaking protocol's slashing conditions are triggered. This results in a slash—a punitive reduction of the staker's delegated funds, which are programmatically burned or redistributed. This slashing risk financially aligns the operator's incentives with honest behavior.

The flow is circular and self-reinforcing. As AVSs attract more restaked capital, their security budget increases, making them more resilient to attacks. Successful operators earn rewards from the AVSs, a portion of which is typically shared with their delegators. This creates a security marketplace where stakers seek the best risk-adjusted returns by delegating to reputable operators running valuable services, all secured by the same pooled base layer of Ethereum stake.

security-considerations
RESTAKED SECURITY

Security Considerations and Risks

Restaked security introduces a novel risk model by pooling validator collateral across multiple protocols. This section details the core security trade-offs and attack vectors inherent to this architecture.

01

Slashing Risk Amplification

In restaking, a single validator fault can trigger slashing penalties across multiple Actively Validated Services (AVS) simultaneously. This creates a multiplicative loss scenario where the total penalty exceeds the base Ethereum slashing amount. For example, a validator penalized 1 ETH by Ethereum could face an additional 2 ETH in penalties from two separate AVSs, leading to a total loss of 3 ETH. This amplifies the financial risk for operators and requires sophisticated risk management.

02

Correlated Failure & Systemic Risk

The security of multiple AVSs becomes interdependent, creating systemic risk. A critical bug or successful attack on one major AVS could cascade, causing widespread slashing events that destabilize the entire restaking ecosystem. This correlation contrasts with isolated security models where a failure is contained. It necessitates rigorous, independent audits for each AVS and careful monitoring of aggregate risk exposure across the network.

03

Operator Centralization Pressure

To mitigate slashing risk, node operators may gravitate towards running only the safest, least complex AVSs, or delegate their stake to large, professional staking pools. This can lead to:

  • Centralization of AVS security among a few large operators.
  • Reduced economic support for newer or more innovative AVSs.
  • Potential cartel formation where large operators exert undue influence over AVS governance and fee markets.
04

AVS Operator Collusion

Restaking enables a new collusion vector where a malicious AVS developer and a malicious node operator conspire. The developer could create an AVS with intentionally vulnerable code or governance, the operator could then get slashed on purpose, potentially triggering a denial-of-service or creating a cover for a separate exploit on a correlated system. This requires robust, decentralized operator sets and AVS code verification.

05

Liquidity & Withdrawal Risks

Liquid Restaking Tokens (LRTs) introduce secondary market risks. The value of an LRT is a derivative of the underlying restaked ETH plus accrued rewards, minus potential future slashing. Key risks include:

  • Depeg Risk: LRT price diverging from its net asset value.
  • Withdrawal Queue Contention: During mass exits, users face delays from Ethereum's validator exit queue and potential AVS unbonding periods.
  • Liquidity Fragmentation across multiple LRT issuers.
06

Economic Security vs. Cryptoeconomic Security

Restaking provides cryptoeconomic security (slashable stake), not byzantine fault tolerance (BFT) security. This is a critical distinction:

  • BFT Security: Prevents malicious chain finalization (e.g., Tendermint).
  • Cryptoeconomic Security: Deters malicious activity post-facto via financial penalties. An AVS secured by restaking can still experience liveness failures or incorrect state transitions; the slashing merely punishes provable malfeasance after the fact. The security guarantee is ultimately economic, not algorithmic.
COMPARISON

Restaked Security vs. Other Models

A technical comparison of security models for decentralized networks, focusing on capital efficiency, validator requirements, and economic guarantees.

Security Model FeatureRestaked Security (e.g., EigenLayer)Sovereign PoS ChainShared Security (e.g., Polkadot)Layer 2 (Rollup)

Underlying Security Source

Re-staked Ethereum (or other L1) validators

Dedicated validator set

Primary Relay Chain validator set

Settled on an L1 (e.g., Ethereum)

Capital Efficiency

High (reuses existing stake)

Low (requires new capital)

Medium (shared, but dedicated slot)

High (shares L1 security)

Validator Set Overlap

Economic Slashing

Protocol Governance

Service-specific AVS

Sovereign

Parachain + Relay Chain

Sovereign (Sequencer)

Time to Finality

L1 Finality (~12 min)

Chain-specific (~varies)

Relay Chain Finality (~12-60 sec)

L1 Finality + Proving Delay

Bootstrapping Complexity

Low (leverages L1)

High (needs new validators)

Medium (auction for slot)

Low (deploy contract)

Example

EigenLayer AVSs

Cosmos app-chain

Polkadot parachain

Arbitrum, Optimism

ecosystem-usage
RESTAKED SECURITY

Ecosystem Usage and Applications

Restaked security is a foundational mechanism that enables blockchain networks to bootstrap or enhance their cryptoeconomic security by leveraging the pooled capital of a larger, established ecosystem. This section details its primary applications.

02

Shared Security for Rollups

Restaking provides a path for sovereign rollups and optimistic/zk-rollups to inherit the robust security of Ethereum without being fully dependent on its execution layer. Validators restaking ETH can be tasked with sequencing transactions, proposing blocks, or verifying proofs for a rollup. This creates a modular security model where the rollup's liveness and correctness are secured by the same economic stake securing Ethereum L1.

  • Benefit: Reduces the capital cost and complexity of launching a new, secure L2.
  • Contrast: Differs from native rollups (e.g., Arbitrum, Optimism) that use Ethereum exclusively for data and settlement.
03

Interoperability & Cross-Chain Bridges

Restaked security is a powerful primitive for securing trust-minimized bridges. Instead of relying on a new, potentially under-collateralized multisig, a bridge can use a decentralized network of restakers to attest to the validity of cross-chain messages. Validators are cryptoeconomically accountable; if they sign an invalid state transition or message, their restaked assets can be slashed. This aims to improve upon the security models of existing light client bridges and multisig bridges.

  • Goal: Mitigate bridge hacks, which are a major source of DeFi exploits.
  • Example: Restaked validators could secure a ZK light client verifying state proofs from another chain.
04

Oracle Networks & Data Feeds

Decentralized oracle networks, which provide external data (like price feeds) to smart contracts, can leverage restaking to enhance their security and decentralization. Node operators staking in a protocol like Chainlink could restake their collateral (e.g., LINK or ETH) to also secure the oracle service. This creates a stronger cryptoeconomic security guarantee for the data feed, as malicious reporting would lead to slashing of the operator's primary stake. It aligns the security of the oracle with the underlying blockchain's security pool.

05

The Restaking Stack & Middleware

The application of restaked security relies on a technical stack of smart contracts and coordinator networks. Key components include:

  • Restaking Pools: Smart contracts (e.g., EigenLayer) where assets are deposited and delegated.
  • AVS Registries: Directories where services publish their slashing conditions and quorum requirements.
  • Operator Networks: Node operators who run software for multiple AVSs and manage delegations.
  • Slashing Managers: Modules that monitor for faults and trigger penalty execution.

This stack enables the permissionless marketplace for cryptoeconomic security.

06

Economic & Risk Considerations

Using restaked security introduces unique economic trade-offs and systemic risks. Key considerations include:

  • Yield for Validators: Operators earn additional rewards (paid in AVS tokens or fees) for the extra work and risk.
  • Slashing Risk: Validators face correlated slashing across multiple services for a single fault.
  • Security Dilution: If capital is over-extended across too many AVSs, the cost-of-corruption for each may decrease.
  • Restaking Leverage: The same underlying stake secures multiple systems, creating financial leverage on that security.
RESTAKED SECURITY

Common Misconceptions

Restaked security is a foundational concept in modular blockchain design, but its mechanics and implications are often misunderstood. This section clarifies the most frequent points of confusion.

No, restaking is not the same as staking. Staking is the primary act of locking a native asset (like ETH) to secure a single blockchain's consensus, such as Ethereum's Beacon Chain. Restaking is a secondary action where an already staked asset, along with its staking rewards and slashing conditions, is "re-deployed" to secure additional services like Actively Validated Services (AVS), including other blockchains, oracles, or bridges. It leverages existing economic security rather than bootstrapping it from scratch.

RESTAKED SECURITY

Frequently Asked Questions

Restaked security is a novel mechanism for securing multiple blockchain services by leveraging the economic security of a primary blockchain, most commonly Ethereum. This FAQ addresses common questions about its purpose, mechanics, and key projects.

Restaked security is a cryptoeconomic mechanism that allows a blockchain's staked assets (like ETH) to be 'restaked' to provide security for other, independent services, such as oracle networks, bridges, or layer-2 networks. It works by allowing validators or stakers to opt-in to run additional software modules (called Actively Validated Services or AVSs) and extend their existing stake's slashing conditions to secure those services. This creates a shared security layer where the economic weight of the primary chain's stake is reused, rather than fragmented across many separate networks.

For example, a validator on Ethereum can choose to also secure a data availability layer. If they act maliciously on that layer, they risk having their staked ETH on Ethereum slashed, creating a powerful economic disincentive. This model aims to bootstrap security for new services more efficiently than launching a new token and validator set from scratch.

evolution
RESTAKED SECURITY

Evolution and Future Outlook

Restaked security is a novel cryptoeconomic primitive that extends the security and validation services of a base blockchain, like Ethereum, to other applications and networks, creating a shared security marketplace.

Restaked security is a cryptoeconomic mechanism that enables the pooled security of a Proof-of-Stake (PoS) blockchain, typically Ethereum, to be "restaked" to secure additional services. This is achieved by allowing validators to commit their staked assets, such as ETH, to provide validation for other protocols, including Actively Validated Services (AVSs) like rollups, oracles, and bridges. In return for taking on additional slashing risk, validators earn extra rewards, creating a more efficient capital utilization model for network security.

The concept was pioneered by EigenLayer, which introduced a set of smart contracts on Ethereum that facilitate this restaking. The system's architecture involves three core roles: the stakers (who deposit ETH), the operators (who run node software for AVSs), and the service managers (who deploy and manage the AVSs). This separation of duties allows for specialization and creates a permissionless marketplace where new services can bootstrap security by tapping into Ethereum's established validator set and economic trust.

The evolution of restaked security addresses a key challenge in blockchain scalability: the security fragmentation that occurs when new networks launch with their own, often weaker, validator sets. By leveraging Ethereum's substantial economic security, restaked security provides a more robust alternative to isolated security models. This paradigm is central to the development of a modular blockchain stack, where execution, settlement, consensus, and data availability layers can be decoupled yet still inherit strong, shared cryptoeconomic guarantees.

Looking forward, the future outlook for restaked security hinges on its ability to scale securely. Key areas of development and research include inter-subjective slashing for faults that are not objectively verifiable on-chain, the mitigation of correlation risks where a single failure could impact multiple AVSs, and the design of effective delegation mechanisms for liquid staking token (LST) holders. The success of this model could fundamentally reshape how decentralized applications and infrastructure secure themselves, moving from isolated security silos to a cohesive, economically bonded ecosystem.

ENQUIRY

Get In Touch
today.

Our experts will offer a free quote and a 30min call to discuss your project.

NDA Protected
24h Response
Directly to Engineering Team
10+
Protocols Shipped
$20M+
TVL Overall
NDA Protected Directly to Engineering Team