What is Shared Security?

Shared Security is a blockchain security model in which multiple networks, applications, or decentralised services rely on a common pool of validators, staked assets, or other security infrastructure instead of building completely independent security systems. The model allows economic or validator resources established by one ecosystem to protect additional protocols.

The central problem Shared Security addresses is security fragmentation. A new blockchain or decentralised service may require validators, staking capital, incentive mechanisms, monitoring infrastructure, and penalties for malicious behaviour before it can operate safely. Establishing all of these components independently can be expensive, particularly when a project has a new token with limited market value.

Shared Security provides an alternative. Several protocols can draw security from an existing validator or staking system, allowing them to launch without creating an entirely separate security market. Depending on the architecture, this can involve the validator set of a base blockchain, a dedicated provider chain, or a marketplace where protocols obtain economic security from participating operators and stakers.

The concept is broader than restaking. Restaking is one mechanism for allocating already committed assets to additional services, while Shared Security describes the larger security model in which several systems depend on common resources. Models such as Polkadot’s pooled security, Cosmos Hub’s replicated security, and Ethereum-based restaking illustrate different ways of implementing this principle.

The Security Bootstrapping Problem

A Proof of Stake network cannot be evaluated only by its software. Its economic security also depends on the value committed by validators and the incentives governing their behaviour.

Consider a new blockchain with a native token worth $50 million in total. Even if a large percentage of the supply is staked, the economic cost of attacking the network may remain relatively low compared with an established ecosystem secured by billions of dollars in assets.

Token distribution creates another problem. A young network may have a limited number of professional validators and highly concentrated ownership. Increasing the number of nodes does not automatically create strong economic security if most of the stake remains controlled by a few participants.

Bootstrapping an independent validator set also requires continuous incentives. Networks often distribute newly issued tokens to validators and delegators. High initial rewards can attract participants, but they dilute token supply and may not represent sustainable security expenditure if the network generates little fee revenue.

Shared Security changes this equation by allowing a new system to use security resources that already exist elsewhere. The consumer protocol can concentrate on its own execution logic or application while relying on another system for some or all validator-related functions.

The important point is that security is not literally copied. A shared-security architecture defines additional responsibilities for existing validators or operators and establishes economic consequences for failing those responsibilities.

How Shared Security Can Be Structured

There is no universal Shared Security protocol. Different blockchain ecosystems implement the idea at different architectural layers.

In one model, validators of a central blockchain are directly responsible for validating additional chains. The same validator set therefore participates in consensus for several networks. Cosmos Hub’s replicated security has used this general approach for consumer chains.

Polkadot uses another model. Its Relay Chain provides pooled security to connected parachains. Parachains can maintain their own state-transition logic while relying on the Relay Chain validator system for shared consensus security.

Restaking systems introduce a more market-oriented structure. Instead of every validator automatically securing every connected service, operators can opt into additional services and capital can be allocated according to specific security requirements. The underlying principle remains shared economic resources, but participation and risk can be more granular.

A simplified Shared Security relationship typically involves:

1. A provider system establishes a validator set, staking pool, or other source of economic security.
2. A consumer network or service defines the tasks that must be performed for it.
3. Validators or operators become responsible for those additional tasks according to the architecture.
4. Economic collateral is associated with correct performance.
5. Consumer protocols pay fees, rewards, or other incentives for the security they receive.
6. Misbehaviour can trigger penalties where the shared-security system provides enforceable conditions.

This structure can create a security marketplace. Instead of every network issuing inflationary rewards to attract its own validator set, protocols can pay for access to existing security.

The exact guarantees depend heavily on implementation. A protocol secured directly by the full validator set of another blockchain has a different security profile from a service supported by an optional subset of operators.

Shared Security Models in Crypto

Several prominent blockchain architectures use the Shared Security principle, but the way security is allocated differs considerably.

The final row illustrates why terminology requires care. Ethereum rollups are often described as inheriting or sharing Ethereum security, but their relationship with Ethereum differs from explicit Shared Security systems. A rollup uses Ethereum for settlement and data availability, while its sequencer, proof system, bridge contracts, and upgrade mechanisms can introduce additional assumptions.

Similarly, not every blockchain connected through interoperability shares security. Two networks can exchange messages through a bridge while retaining completely independent validator sets. Interoperability allows communication, whereas Shared Security concerns the mechanisms responsible for protecting state and enforcing correct behaviour.

This distinction becomes important when evaluating claims that a new network “inherits” the security of a larger blockchain. The relevant question is which failures the provider system can actually prevent or punish.

Economic Security Is Not the Same as Technical Security

Shared Security can provide access to a large amount of staked capital, but economic value alone does not determine whether a network is secure.

Suppose a service has $1 billion of collateral nominally associated with its security. That number is meaningful only if malicious behaviour can be detected and the collateral can actually be penalised. If the protocol cannot objectively identify a violation, the economic stake may provide limited protection against that particular failure.

Validator concentration also matters. A large total stake controlled by a small number of operators can create operational and governance dependencies. If the same operators participate across many consumer networks, an infrastructure failure can affect several systems simultaneously.

The security of a shared model therefore depends on multiple factors beyond the headline value of collateral:

• the amount of economic capital genuinely exposed to penalties;
• the number and independence of participating validators or operators;
• whether protocol violations can be detected reliably;
• the effectiveness and enforceability of slashing or other penalties;
• software diversity and operational independence;
• governance powers over security parameters and protocol upgrades;
• the ability of consumer networks to recover from failures.

This is one reason Shared Security should not be described simply as “borrowing security”. Consumer protocols still have their own code, governance, smart contracts, bridges, and application logic. A shared validator system cannot automatically protect users from vulnerabilities in all of these components.

Capital Efficiency and Security Fragmentation

One of the strongest arguments for Shared Security is capital efficiency.

Imagine ten independent Proof of Stake networks that each require $100 million of staked value to reach their desired economic security level. In a fully independent model, the ecosystem may need $1 billion distributed across ten separate staking systems.

A shared model can potentially use the same underlying security infrastructure across several networks. This does not necessarily mean $100 million can safely provide the equivalent of $1 billion of independent security. Simultaneous obligations and correlated failures must still be considered. However, the system can avoid duplicating some validator infrastructure and idle economic commitments.

Shared Security can also reduce fragmentation among validators. Instead of persuading professional operators to run separate infrastructure for numerous small networks with uncertain economics, projects can connect to an established operator ecosystem.

For developers, this can shorten the path from protocol design to a functioning decentralised network. Security becomes more like infrastructure that can be accessed under defined economic conditions rather than something every project must construct from zero.

This idea is particularly relevant as blockchain architecture becomes increasingly modular. Execution, consensus, settlement and data availability do not necessarily have to be provided by the same network. Shared Security fits this modular model by allowing security resources to become another component that protocols can obtain from external infrastructure.

The Risks of Sharing Security

Sharing infrastructure also means sharing some failures. This is the fundamental trade-off behind the model.

If one validator set secures many networks, a serious validator outage can affect multiple consumer systems simultaneously. An independent validator set might isolate the failure to one blockchain, while a shared model can create a larger failure domain.

Conflicting incentives are another concern. Validators may have responsibilities across several networks, each offering different rewards and imposing different technical requirements. As the number of obligations increases, operators need more infrastructure and more complicated risk management.

Important Shared Security risks include:

• correlated outages affecting several networks at the same time;
• concentration of security among a limited number of major validators;
• cascading penalties when operators perform duties for multiple systems;
• consumer protocols becoming economically dependent on the provider network;
• governance changes at the security provider affecting connected networks;
• security demand exceeding the amount of capital or infrastructure realistically available;
• complexity in determining which system bears losses after a cross-protocol failure.

The economic relationship between providers and consumers must also be sustainable. Validators need compensation for additional infrastructure and risk. If consumer networks cannot generate enough revenue, they may depend on token subsidies rather than genuine demand for security.

Shared Security therefore reduces some bootstrapping costs but does not make security free.

Shared Security in a Modular Blockchain Ecosystem

Shared Security is becoming more relevant as blockchain systems specialise. A single network no longer needs to provide execution, settlement, consensus, interoperability, and data availability entirely by itself.

A project can use one system for settlement, another for data availability, and specialised operators for additional verification. This modular approach can improve flexibility, but it also creates questions about which component is ultimately responsible when something fails.

Shared Security attempts to make one part of that stack reusable. An established validator or staking ecosystem can support multiple consumer networks instead of limiting its economic security to one protocol.

This can make smaller networks economically viable without forcing each one to create a valuable staking token and independent validator community. It can also allow security providers to generate additional economic activity from infrastructure that already exists.

The model is not automatically superior to sovereign security. An independent blockchain controls its own validator incentives and does not inherit the same cross-network dependencies. Shared systems trade some of that independence for access to established capital and infrastructure.

For this reason, the most important question is not simply how much security is “shared”. It is what security guarantees are actually shared, which participants enforce them, what capital is genuinely at risk, and what happens when one of the connected systems fails. Those details determine whether Shared Security provides meaningful protection or merely creates additional dependencies between protocols.