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

Shared Security

A security model where a primary blockchain provides economic security to auxiliary chains, rollups, or other systems, often through restaking or validation services.
Chainscore © 2026
definition
BLOCKCHAIN CONSENSUS

What is Shared Security?

A foundational model where multiple independent blockchains or applications pool their economic security from a single, robust base layer.

Shared security is a blockchain architectural model where multiple independent blockchains, known as parachains or app-chains, derive their consensus and economic security from a single, more secure primary blockchain, called a relay chain or hub. This model, pioneered by networks like Polkadot and Cosmos, allows newer or smaller chains to bootstrap their security by leasing it from an established, high-value network, rather than needing to build and maintain their own validator set from scratch. The security is "shared" because the validators of the primary chain are responsible for validating the state transitions of all the connected chains.

The core mechanism enabling shared security is a proof-of-stake (PoS) system where validators on the primary chain stake the network's native token (e.g., DOT or ATOM). These validators are then randomly assigned to validate blocks for the connected chains. In Polkadot's model, collators on each parachain gather transactions and propose blocks, which are then validated and finalized by the relay chain's validators. This creates a unified security umbrella: an attack on any single parachain would require compromising the economic security of the entire, much larger, validator set of the primary chain, making it prohibitively expensive.

This model presents significant advantages over isolated, standalone blockchains. It eliminates the security fragmentation problem, where new chains with small market capitalizations are vulnerable to 51% attacks. It also allows developers to focus on application logic and innovation without the overhead of bootstrapping a global validator community. However, it introduces a degree of sovereignty trade-off, as the shared security provider ultimately has final authority over block finality and may impose governance or upgrade schedules on the connected chains.

Key implementations vary. Polkadot offers tightly coupled shared security via its nominated proof-of-stake (NPoS) relay chain. Cosmos, through its Interchain Security feature, allows the Cosmos Hub to validate blocks for consumer chains. Ethereum's rollup-centric roadmap is another form of shared security, where Layer 2 rollups (like Optimism or Arbitrum) post their transaction data and proofs to Ethereum, inheriting its settlement guarantees. The model is fundamental to the vision of a scalable, interconnected multi-chain ecosystem.

how-it-works
BLOCKCHAIN ARCHITECTURE

How Does Shared Security Work?

Shared security is a foundational model in modular blockchain design where a primary, highly secure blockchain provides economic and cryptographic security to multiple secondary chains or applications.

Shared security is a model where a primary blockchain, often called a Layer 1 or consensus layer, provides its robust security guarantees—derived from its validators and economic stake—to other, often more specialized, chains. These secondary chains, known as rollups, parachains, or appchains, do not need to bootstrap their own independent validator set. Instead, they outsource the critical tasks of transaction ordering and finality to the secure base layer. This creates a security-as-a-service economy, allowing developers to focus on execution and innovation without the immense cost and complexity of securing a new blockchain from scratch.

The mechanism typically involves the secondary chain publishing its transaction data or state commitments to the primary chain. For example, in an optimistic rollup, transaction data is posted to Ethereum, and a fraud-proof window allows anyone to challenge invalid state transitions. In a zk-rollup, validity proofs are submitted to the L1 for instant verification. Similarly, in a parachain model like Polkadot, a central relay chain coordinates consensus and security for all connected parachains, with validators being randomly assigned to secure different chains. In all cases, the security of the secondary chain is ultimately anchored by the cryptoeconomic security of the larger, more decentralized parent chain.

This model offers significant advantages. It dramatically lowers the security bootstrap problem for new chains, as they inherit the established trust of a major network like Ethereum or Cosmos. It also enhances interoperability, as chains sharing a security provider can communicate and transfer assets more trustlessly. However, it introduces dependencies; the security and liveness of all subordinate chains are tied to the health and performance of the primary chain. Furthermore, it often involves ongoing economic costs, such as paying transaction fees or staking tokens on the base layer to lease security.

key-features
ARCHITECTURAL PRINCIPLES

Key Features of Shared Security

Shared security is a model where a primary blockchain (the provider) extends its economic security and consensus finality to other, often smaller, chains or applications (the consumers).

02

Unified Consensus & Finality

Consumer chains rely on the provider chain's consensus mechanism (e.g., Proof-of-Stake) for state validation and finality. Transactions are not considered final until they are settled on the secure base layer. This eliminates the need for consumers to run complex consensus logic, simplifying their architecture and ensuring a single source of truth.

03

Validator Set Reuse

The same set of validators from the provider chain is responsible for validating the state of all connected consumer chains. This is a core mechanism in interchain security (Cosmos) and restaking (EigenLayer). Validators run additional software for each consumer but their stake and slashing conditions are managed by the primary chain.

04

Slashing & Accountability

Malicious behavior on a consumer chain (e.g., signing invalid blocks) can result in slashing penalties applied to the validator's stake on the provider chain. This creates strong economic disincentives for validators to misbehave on any secured chain, aligning security incentives across the entire ecosystem.

05

Sovereignty vs. Security Trade-off

Consumer chains gain robust security but often cede some degree of sovereignty. They may be bound by the provider's upgrade timelines, governance decisions, or economic policies. This is a key differentiator from bridges and sidechains, which may have independent validator sets and greater autonomy.

06

Modular Architecture Enabler

Shared security is foundational to modular blockchains. It allows execution layers (like rollups) and data availability layers to specialize, while outsourcing consensus and security to a dedicated settlement layer (e.g., Ethereum, Celestia). This separation of concerns is key to scalable blockchain design.

examples
SHARED SECURITY

Examples & Implementations

Shared security is implemented through various models, from pooled validator sets to economic slashing. This section details the primary architectures and real-world projects that define the landscape.

05

Rollups as a Service

Platforms like Conduit and Caldera abstract the complexity of launching a dedicated rollup. They provide a managed service that handles node infrastructure, often defaulting to a shared sequencer set. While the underlying security derives from Ethereum (via fraud or validity proofs), the operational security and liveness are managed by the service provider, representing a form of shared operational security.

  • Key Feature: Managed node infrastructure and sequencing.
  • Benefit: Rapid deployment of an app-specific rollup.
06

Economic Security vs. Validator Security

A critical distinction in implementation models:

  • Validator Security: The provider chain's validators actively produce or validate blocks for the consumer chain (e.g., Cosmos ICS, Polkadot). Security is technical and algorithmic.
  • Economic Security: Staked capital from the provider chain is used as a slashable guarantee for services on another system, but the provider's validators do not run its software (e.g., EigenLayer). Security is primarily financial and enforced via smart contracts.
BLOCKCHAIN SECURITY MODELS

Shared Security vs. Sovereign Security

A comparison of two fundamental security architectures for blockchain networks, focusing on the relationship between a main chain (or validator set) and its connected chains.

FeatureShared SecuritySovereign Security

Core Security Source

Borrowed from a parent chain (e.g., Ethereum, Cosmos Hub)

Self-provided, independent validator set

Settlement & Data Availability

Typically inherits from the parent chain

Handled by the sovereign chain's own consensus

Upgrade Autonomy

Often requires coordination with or approval from the parent chain

Full, unilateral control over protocol upgrades

Validator Sovereignty

Validators are typically those of the parent chain

Chain controls its own validator set and slashing logic

Economic Bond / Stake

Uses the parent chain's native asset (e.g., ETH, ATOM)

Uses its own native asset for staking and security

Example Frameworks

Ethereum L2 Rollups (Optimistic, ZK), Cosmos Interchain Security

Traditional L1s, Cosmos SDK zones, Avalanche subnets

Typical Throughput vs. Security Trade-off

Higher throughput, with security rooted in a robust parent chain

Maximum flexibility, with security directly proportional to own validator stake

Forking Capability

Generally cannot fork without parent chain coordination

Can fork or change consensus rules independently

benefits
KEY ADVANTAGES

Benefits of Shared Security

Shared security is a model where a primary blockchain (the security provider) validates and secures the transactions of multiple independent chains (the security consumers). This architecture offers several fundamental advantages over isolated security models.

01

Capital Efficiency

Projects launching new blockchains (app-chains, rollups) do not need to bootstrap their own decentralized validator set. They can lease security from an established chain like Ethereum or Cosmos, avoiding the immense capital and time cost of attracting and incentivizing a large, independent staking ecosystem from scratch.

02

Stronger Security Guarantees

Consumer chains inherit the cryptoeconomic security of the provider chain. An attacker must compromise the provider's validator set, which typically has a far higher total value staked (TVS) than a new chain could achieve alone. This creates a formidable economic barrier against 51% attacks and other consensus-level threats.

03

Faster Innovation & Specialization

Developers can focus on building application-specific logic and optimizing for performance without being security experts. This enables rapid experimentation with new virtual machines, transaction formats, and fee models, as the underlying consensus and data availability are handled by the secure provider layer.

04

Interoperability by Default

Chains secured by the same provider often share a native, trust-minimized communication pathway. For example, rollups on Ethereum can communicate via the base layer, and chains in the Cosmos ecosystem using Inter-Blockchain Communication (IBC) benefit from shared security to enable secure cross-chain messaging and asset transfers.

05

Reduced Validator Overhead

Validators on the provider chain can secure multiple consumer chains without significant additional operational cost or hardware. This is efficient for validators and creates a more sustainable economic model for the overall ecosystem, as security costs are amortized across many applications.

06

Examples in Practice

  • Ethereum Rollups (L2s): Secured by Ethereum's consensus and data availability (e.g., Optimism, Arbitrum, zkSync).
  • Cosmos Interchain Security: Allows Cosmos Hub validators to produce blocks for consumer chains.
  • Polkadot Parachains: Secured by the collective validator set of the Polkadot Relay Chain.
security-considerations
SHARED SECURITY

Security Considerations & Trade-offs

Shared security is a model where a blockchain (the provider) leases its economic security and consensus to other chains or applications (the consumers). This section details its core mechanisms, trade-offs, and real-world implementations.

01

Core Mechanism: Economic Bonding

The foundational security guarantee in shared security models is the economic stake of validators on the provider chain. This stake is slashable if the validators misbehave on the consumer chain. This creates a direct financial disincentive for attacks, as compromising a consumer chain risks losing value on the more valuable provider chain. For example, a validator on the Cosmos Hub securing a consumer chain can have its staked ATOM tokens slashed for double-signing on that consumer chain.

02

Key Trade-off: Sovereignty vs. Security

The primary trade-off in shared security is the balance between sovereignty and security strength. A sovereign chain has full control over its validator set and upgrade process but must bootstrap its own economic security from scratch. A chain using shared security gains immediate, robust security from day one but cedes some sovereignty, as its security is ultimately governed by the provider chain's validator set and governance. This is a fundamental architectural choice for blockchain developers.

03

Implementation: Interchain Security (Cosmos)

Interchain Security is a canonical implementation on the Cosmos network. A provider chain (e.g., Cosmos Hub) allows its validators to run nodes for a consumer chain. Key characteristics include:

  • Replicated Security: The exact validator set of the provider chain secures the consumer chain.
  • Cross-Chain Slashing: Malicious actions on the consumer chain lead to slashing on the provider chain.
  • Revenue Sharing: Consumer chains can share transaction fees and inflation rewards with the provider chain's validators and stakers.
04

Implementation: Parachains & Parathreads (Polkadot)

Polkadot's shared security model secures parachains and parathreads via the Relay Chain. All parachains share the same validator pool, which randomly and frequently assigns validators to different chains. This provides:

  • Strong, pooled security where an attack on one parachain requires compromising a large portion of the entire Relay Chain's stake.
  • Scalability through parallel transaction processing.
  • Flexible access with parachains (dedicated slot) vs. parathreads (pay-as-you-go).
05

Consideration: Provider Chain Centralization Risk

Shared security consolidates trust in the provider chain's validator set. This introduces a centralization of security risk. If the provider chain's validator set becomes overly centralized or is compromised, all consumer chains inheriting its security are simultaneously jeopardized. The security of the entire ecosystem is now a function of the provider chain's social consensus and governance resilience. This makes the provider chain a high-value target and a potential single point of failure.

06

Consideration: Alignment of Incentives

For shared security to be sustainable, incentives must be correctly aligned between the provider chain's validators and the consumer chains. Validators must be sufficiently compensated (via fees, tokens, or other rewards) for the extra operational cost and risk of validating additional chains. If rewards are too low, validator participation drops, weakening security. Models like Opt-in Interchain Security allow validators to choose which consumer chains to secure, creating a market for security.

evolution
FROM MONOLITHIC TO MODULAR

Evolution of the Concept

The concept of shared security has evolved from a theoretical model for securing independent blockchains to a foundational architectural principle for modular networks.

The genesis of shared security lies in the fundamental challenge of bootstrapping security for new, independent blockchains (Layer 1s). A new chain must attract its own validators and stake—a classic "cold start" problem that often results in low security and high centralization risk. The initial concept, often called security-as-a-service, proposed that a smaller chain could lease security from a larger, more established network like Ethereum, treating its robust validator set and economic security as a reusable resource. This model was first formally explored in research on merged mining and later in proposals for proof-of-stake sidechains.

The evolution accelerated with the rise of app-specific blockchains (appchains) and modular architecture. Platforms like Cosmos, with its Inter-Blockchain Communication (IBC) protocol, initially championed a model of sovereign security, where each chain maintained its own validator set. However, the complexity and cost of recruiting and incentivizing a dedicated validator set for every new appchain highlighted the practical appeal of a shared security model. This led to the development of Cosmos Hub's Interchain Security (ICS), a landmark implementation where consumer chains can lease validators from the Hub's set, creating a security marketplace.

The concept reached a new paradigm with Ethereum's rollup-centric roadmap. Here, Layer 2 rollups (Optimistic and ZK) inherently inherit the security of Ethereum's Layer 1 by posting transaction data and proofs to it. This is not a lease but a structural inheritance: the security of the Ethereum Virtual Machine (EVM) and its consensus mechanism is automatically extended to the rollup. This has established shared security as the default for Ethereum's scaling ecosystem, blurring the line between a standalone chain and a secured execution layer.

Today, the evolution continues towards universal shared security layers. Projects like EigenLayer on Ethereum introduce restaking, a mechanism that allows ETH stakers to opt-in to secure additional services—like Actively Validated Services (AVSs) including new blockchains, oracles, and bridges—without allocating new capital. This transforms the monolithic security of a base layer into a reusable, composable good that can be programmatically allocated across a diverse "ecosystem of trust," representing the most abstract and market-driven iteration of the concept to date.

SHARED SECURITY

Frequently Asked Questions (FAQ)

Shared security is a foundational concept in modular blockchain architecture, where a central chain provides security guarantees to multiple independent chains. This section answers common questions about its mechanisms, benefits, and leading implementations.

Shared security is a model where a primary, highly secure blockchain (the settlement layer) provides cryptoeconomic security to a network of secondary chains, allowing them to inherit the consensus and data availability guarantees of the parent chain without having to bootstrap their own validator set. This is achieved by having validators from the main chain also validate the state transitions or data commitments of the connected chains, often through mechanisms like fraud proofs or validity proofs. The most prominent example is the Ethereum ecosystem, where rollups (like Optimism and Arbitrum) leverage Ethereum's validators for security while executing transactions off-chain. This model enables sovereignty for application-specific chains while dramatically lowering the capital and coordination costs required to achieve robust security.

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
Shared Security: Blockchain Security Model Explained | ChainScore Glossary