In the world of blockchains that secure themselves through staking, a powerful and deeply controversial idea has taken firm hold, the seductive idea that the very same staked assets used to secure one network could simultaneously be put to work securing many others at the same time. This concept, known as restaking, promises to make capital that is already locked up doing one job do several different jobs at once, earning additional rewards for its owners and helping new projects bootstrap the economic security they need to operate from the very beginning. In a remarkably short span of time, restaking grew from a novel and untested proposal into one of the largest and fastest-growing sectors of all decentralized finance, attracting tens of billions of dollars in committed value as users sought aggressively to maximize the returns on their staked assets and as a wave of ambitious new projects looked to it as a ready source of economic security they could rent rather than laboriously build from scratch.
The appeal of restaking is easy enough to understand at first glance, since it offers more reward from the same fixed capital and a much faster path to security for new and unproven networks, but it rests on a foundation that is far more precarious and far more interconnected than it first appears to be. When a single pool of staked assets is used to secure many different things at once, the risks of all those many things become deeply entangled, so that a single failure in one place can ripple outward to affect all of the others that share the same underlying security. The careful systems of penalties that keep stakers honest, in which their assets can be confiscated for misbehavior, multiply rapidly as the same assets become subject to the differing rules of many separate services, and the layering of restaking on top of staking, and then of further products on top of restaking, builds precarious towers of stacked dependencies in which risk compounds in ways that can be difficult to see clearly and dangerous to bear. This simultaneous compounding of both security and of risk is the central defining feature of the entire restaking model.
This article examines restaking protocols and the compound security models they create, written for a reader with no background in blockchain or staking. It explains what staking and restaking are and how compound security works, the mechanisms by which restaking layers risk through securing multiple services and through liquid and leveraged products built on top, and the architecture that determines how that risk is structured. It weighs the genuine rewards and the serious risks for stakers, new networks, and the broader ecosystem, and it grounds the discussion in documented protocols, growth figures, and a real incident in which the layered risks of restaking materialized. The aim is to convey both why restaking has grown so explosively and why its compounding of risk demands careful and genuinely sober attention.
Understanding Staking, Restaking, and Compound Security
To understand restaking, one must first understand staking, the mechanism by which many modern blockchains secure themselves. Networks that use a system called proof of stake rely on participants, called validators, who lock up a quantity of the network’s cryptocurrency as a stake, a financial commitment that they will behave honestly in validating transactions and maintaining the network. This staked capital serves as security because it is at risk, since validators who behave correctly earn rewards, while those who misbehave, by trying to cheat the system or by failing to do their job properly, can have a portion of their stake confiscated through a penalty known as slashing. The threat of losing their staked assets is what keeps validators honest, aligning their financial interest with the correct functioning of the network, and the total amount staked represents the economic security backing the blockchain, since attacking it would require putting an enormous amount of capital at risk.
Restaking builds on this foundation with a simple but consequential insight, that the staked capital securing one network is, in a sense, sitting there as a pool of security that could potentially back other things as well. Normally, assets staked to secure a blockchain do only that one job, but restaking allows those same staked assets, or claims on them, to be committed simultaneously to securing additional services, so that the capital is reused to provide security in more than one place at once. A new project that needs economic security to operate, but that cannot easily attract its own large pool of staked capital, can instead tap into the security of an established network’s stakers through restaking, renting security rather than building it from nothing. The staker, in turn, earns additional rewards for committing their assets to secure these extra services, on top of the rewards they already earn for securing the base network, making their capital more productive.
This reuse of staked capital is what creates the compound security model, in which the same assets simultaneously back multiple networks or services and are subject to the rules and penalties of each. Where a normal staker faces the slashing conditions of a single network, a restaker faces the slashing conditions of every service their assets help secure, so that their capital can be penalized for misbehavior or failure across any of the multiple things it is committed to. This is the heart of the compound security model, the layering of multiple security commitments, and therefore multiple risks, onto a single base of staked capital. The security each service receives is real, drawn from the genuine economic value of the staked assets, but it is shared rather than dedicated, and the risks borne by the staker are compounded rather than singular, which is the fundamental trade-off that restaking embodies.
The significance and the danger of this model both flow from the same source, the entanglement of risks that comes from sharing security. On one hand, compound security is enormously efficient, allowing capital to provide security in many places at once and giving new projects access to security they could not otherwise afford, which is why restaking grew so rapidly and attracted such enthusiasm. On the other hand, the entanglement means that the failure of any one service, or the misbehavior or error of the operators managing the shared stake, can result in slashing that affects the shared capital, and that problems can cascade across the many services and participants that depend on the same pool of security. The careful isolation that keeps the failure of one network from affecting another is sacrificed in the name of efficiency, creating interconnections through which trouble can spread. Understanding both the efficiency that makes restaking attractive and the entanglement that makes it dangerous is the foundation for grasping how the model works and why it has provoked both rapid adoption and serious concern, including warnings from prominent figures that overloading the security of a base network in this way could introduce systemic risks to the entire ecosystem.
A helpful way to appreciate the trade-off is to compare it with the principle of compartmentalization that engineers apply in other domains where failures are dangerous. A ship is divided into watertight compartments so that a breach in one does not flood the entire vessel, and an electrical grid is built with circuit breakers and isolation so that a fault in one section does not cascade across the whole network. These designs deliberately sacrifice some efficiency, since fully integrated systems can be cheaper and simpler, in exchange for the safety that isolation provides, containing failures rather than allowing them to spread. Restaking moves in the opposite direction, deliberately removing the compartmentalization that keeps the security of one network separate from another, in order to gain the efficiency of using the same capital everywhere. The result is a system that is more efficient precisely because it is less compartmentalized, and therefore more vulnerable to cascading failure, since the very connections that allow security to be shared also allow a breach in one place to flood outward. This analogy clarifies why the same property that makes restaking attractive makes it dangerous, and why thoughtful observers have urged caution about removing the isolation that, in safety-critical systems, is usually regarded as a virtue rather than an inefficiency to be eliminated.
How Restaking Works and Layers Risk
Restaking layers risk through two related mechanisms, the commitment of staked capital to secure multiple additional services each with its own slashing rules, and the construction of further financial products on top of restaked positions that add still more layers of dependency and leverage. The first mechanism is the core of restaking itself, in which a base of staked assets is extended to secure a growing number of additional services, accumulating the risks of each. The second mechanism arises from the financial engineering built around restaking, particularly the creation of liquid and leveraged products that allow restaked positions to be traded, reused, and amplified, stacking additional risks on top of the already compounded base. Together these mechanisms produce the towering structures of stacked dependencies that characterize the restaking ecosystem.
The two subsections that follow examine each mechanism in turn. The first concerns the foundational act of restaking, the commitment of staked capital to secure additional services and the accumulation of their slashing conditions, which is where the basic compounding of risk originates. The second concerns the layering of liquid restaking and leverage on top, the financial products that take restaked positions and build further structures upon them, multiplying the dependencies and amplifying both rewards and risks. Understanding both the base compounding and the additional layering is necessary to grasp the full extent of how restaking stacks risk, and why the resulting structures can be so fragile.
Restaking and Actively Validated Services
The foundational mechanism of restaking is the commitment of staked capital to secure additional services, each of which imposes its own conditions and risks on the shared stake. In the leading model, stakers or the operators who manage their stake can opt in to securing additional services, sometimes called actively validated services, which are new networks, applications, or protocols that need economic security to function but that use the restaked capital of an established network rather than their own dedicated stake. By committing their staked assets to secure such a service, restakers extend the security of the base network to it, and in return they earn additional rewards from that service, making their capital productive across multiple uses simultaneously. This allows a new service to launch with substantial economic security from day one, borrowing the credibility and the financial backing of the established network’s stakers rather than spending years and enormous resources building its own.
The crucial consequence is that each additional service a restaker commits to brings with it additional slashing conditions, the rules under which the shared stake can be penalized, so that the restaker’s risk accumulates with each commitment. A normal staker faces only the slashing rules of the base network, but a restaker faces the slashing rules of every service they help secure, meaning their capital can be confiscated for misbehavior or failure according to the conditions of any of those services. If an operator managing the stake misbehaves with respect to one service, or if a service’s rules are poorly designed or maliciously crafted, the shared capital can be slashed, and the more services a restaker commits to, the more sources of potential penalty they accumulate. This is the basic compounding of risk in restaking, the accumulation of multiple, independent slashing conditions onto a single pool of capital, so that the staker’s exposure grows with each additional service even as their rewards do.
The danger is heightened by the reliance on operators and on the correct design and behavior of the many services involved, which introduces points of failure beyond the staker’s direct control. Restakers often delegate the operation of their stake to operators who actually run the validation work for the various services, which means the staker’s capital depends on the honesty and competence of these operators across all the services they secure, and an operator’s mistake or misbehavior can result in the slashing of the delegated capital. The services themselves vary in quality, maturity, and trustworthiness, and a poorly designed or malicious service could define slashing conditions that endanger the capital securing it, or its governance could be corrupted in ways that put the shared stake at risk. The restaker, in committing to secure multiple services, is therefore trusting the correct functioning of many components, operators and services alike, any of which could cause loss, and this multiplication of dependencies and trust requirements is what makes the foundational mechanism of restaking inherently riskier than simple staking, accumulating exposures that compound with the scale of participation.
Liquid Restaking and the Layering of Leverage
On top of the base compounding of restaking, a further layer of financial products has emerged that stacks additional risk through liquidity and leverage, most notably liquid restaking tokens. When a user restakes their assets, those assets become locked and illiquid, unable to be used elsewhere, and liquid restaking protocols address this by giving the user a tradeable token representing their restaked position, which they can use, trade, or deploy in other applications while their underlying assets remain restaked. This liquid restaking token, such as the tokens issued by major liquid restaking protocols, allows the restaked value to be put to additional use, which is convenient and capital-efficient, but it also adds a layer of abstraction and dependency on top of the already compounded restaking position, since the token’s value depends on the underlying restaked assets and on the protocol that issued it remaining sound.
The layering becomes especially dangerous when these liquid restaking tokens are used as collateral for borrowing and leverage, which multiplies both rewards and risks and creates the potential for cascading liquidations. Users seeking higher returns can use their liquid restaking tokens as collateral to borrow more assets, which they then restake again, amplifying their exposure and their potential rewards through leverage, building a tower in which staking supports restaking, which supports a liquid token, which supports borrowing, which supports more restaking. This leveraged structure is fragile, because if the value of the liquid restaking token falls even slightly relative to its expected peg, the loans collateralized by it can be liquidated, forcing the sale of the token, which pushes its value down further and triggers more liquidations in a cascade. The leverage that amplifies returns in good times amplifies losses in bad times, and the dependency of the whole structure on the liquid token maintaining its value makes it vulnerable to rapid unwinding.
A critical vulnerability in this layered structure is the difficulty of redeeming the underlying assets quickly, which can prevent the mechanisms that would normally keep a liquid restaking token at its proper value from working. A liquid restaking token is supposed to be worth the value of the assets it represents, and normally arbitrageurs would buy it if it traded below that value and redeem it for the underlying assets to profit, keeping its price in line, but if redemption is slow or not yet possible, this corrective mechanism is disabled, allowing the token’s price to fall far below its proper value during a panic. Because unwinding the underlying staking and restaking operations takes time, and some protocols have not even enabled withdrawals, a liquid restaking token can detach from its expected value with no easy way to restore it, and the resulting depeg can trigger the liquidation cascades described above, inflicting losses across all the lending and leverage built on the token. This combination of layered leverage and impaired redemption is what makes the liquid restaking layer particularly hazardous, stacking on top of the compounded base of restaking a further set of risks that can unwind violently, as a real incident in the restaking ecosystem demonstrated, transforming a small loss of peg into a wave of forced liquidations and losses across the interconnected structure.
The Technology and Risk Architecture
The restaking ecosystem rests on a specific technical architecture whose structure determines how risk is distributed and compounded, and understanding this architecture clarifies both how restaking functions and where its dangers lie. At the base are the staked assets themselves, the capital locked to secure a proof-of-stake network, which restaking protocols make available to secure additional services. The restaking protocol provides the smart contracts and mechanisms that allow this staked capital, or representations of it, to be committed to additional services, to track those commitments, and to enforce the slashing conditions of each service against the shared stake. This protocol layer is the foundation of the system, and its security and correct functioning are critical, since it holds and manages the commitments of enormous amounts of capital, and a flaw in it could endanger the entire structure built upon it.
A central element of the architecture is the role of operators and the services they secure, which together define the web of dependencies that restaked capital is exposed to. Operators are the parties who actually run the validation work for the various services, and restakers typically delegate their stake to operators they choose, trusting them to perform correctly across all the services they secure. The services, the additional networks and applications that the restaked capital secures, each define their own slashing conditions and rely on the operators to validate them honestly, and the relationships among stakers, operators, and services form a complex web in which the risk to any pool of staked capital depends on the behavior of its operators and the design of every service it secures. This architecture concentrates risk in ways that matter, since a single operator may secure many services with a large amount of delegated stake, making that operator a critical point whose failure could affect many services and stakers at once.
The structure of slashing conditions and their enforcement is a particularly important and delicate part of the architecture, because it determines how and when the shared capital can be penalized. Each service defines the conditions under which the stake securing it can be slashed, and the restaking protocol must enforce these conditions, confiscating capital when the rules are violated, which is essential to the security the system provides but also the source of its most direct risk to stakers. The design of these slashing conditions matters enormously, since poorly designed conditions could penalize honest behavior or be exploited, and malicious conditions could be crafted to steal the shared capital, so the integrity of the slashing architecture across all the services is crucial to the safety of restakers. The challenge of ensuring that slashing across many independent services is correct, fair, and resistant to abuse is one of the central technical difficulties of the model, and it is compounded by the sheer number and variety of services that may impose conditions on the shared stake.
The layers built on top, particularly liquid restaking and the leverage stacked upon it, complete the risk architecture and represent its most fragile elements. Liquid restaking protocols add their own smart contracts and tokens on top of the base restaking, and the use of these tokens in lending and leverage protocols adds further layers of interconnected contracts and dependencies, creating the towering structures of stacked risk described earlier. Each layer depends on those beneath it, so that the liquid restaking token depends on the restaking, which depends on the staking, which depends on the base network, and the leverage depends on the liquid token maintaining its value, creating a chain of dependencies in which a failure at any level can propagate upward and outward. The transparency of the whole structure also diminishes as the layers accumulate, making it harder for participants to understand the full extent of the risk they bear, which is itself a danger. Taken together, the architecture of staked capital, restaking protocols, operators, services, slashing conditions, and the layers of liquid and leveraged products built on top constitutes a complex and interconnected structure in which security is shared and risk is compounded, and the way this architecture distributes and concentrates risk is what determines the stability or fragility of the entire restaking ecosystem.
The emergence of competing restaking protocols with differing designs has added both choice and further complexity to this architecture. Where the model was initially pioneered by a single dominant protocol focused on the staked assets of one major network, newer entrants have pursued alternative approaches, some accepting a wider range of assets as collateral beyond a single network’s staking tokens, and some emphasizing more permissionless or customizable designs that let networks define their own security arrangements. This diversification expands the possibilities of restaking and introduces competition that may improve the model over time, but it also multiplies the variety of designs, risk profiles, and collateral types that participants must evaluate, and it raises the prospect of capital being restaked across not just many services within one protocol but across many protocols, deepening the interconnection further. The proliferation of approaches means that restaking is not a single, uniform system whose risks can be assessed once, but an evolving and varied landscape in which different protocols make different trade-offs between flexibility, security, and the breadth of assets and services involved, and the differences among them matter greatly for the risks that participants in each actually bear. This growing diversity, while a sign of the model’s vitality, also makes the overall risk landscape harder to comprehend, since the entangled exposures now span an expanding set of protocols with distinct and sometimes opaque designs.
Benefits and Challenges Across Stakeholders
Restaking produces distinct effects for the various parties involved, and a balanced assessment requires weighing its genuine rewards against its serious risks across stakers, new networks, and the broader ecosystem. Stakers gain additional yield on their capital, new networks gain access to security they could not otherwise afford, and the ecosystem gains capital efficiency and a flourishing of new services, yet these benefits come with compounded slashing risk, the fragility of layered leverage, the danger of systemic contagion, and concerns about the overloading of base-network security. The model is genuinely innovative and has grown enormously, but its risks are equally real and have already materialized in losses, so a clear-eyed view must hold the rewards and the dangers firmly together.
The analysis below organizes these considerations by stakeholder and by category, first examining the benefits that accrue to stakers, new networks, and the ecosystem when restaking works, then turning to the risks, compound slashing, and systemic dangers that determine whether those benefits are enjoyed safely or undone by losses. Keeping these perspectives distinct helps move past both the enthusiasm that emphasizes yield while downplaying risk and the dismissal that treats restaking as reckless, arriving at a grounded understanding of what the model offers and the substantial caution it demands.
Benefits for Stakers, New Networks, and the Ecosystem
For stakers, the central benefit is additional yield on capital that would otherwise earn only the rewards of securing a single network, making their staked assets substantially more productive. By committing their staked capital to secure additional services through restaking, stakers earn extra rewards on top of their base staking rewards, increasing the return on capital that is already locked up, and the layering of liquid restaking and other products can further enhance these returns. For holders of staked assets seeking to maximize their returns, restaking offers a way to do so without acquiring additional capital, simply by putting their existing stake to additional use, which is a powerful attraction in a competitive environment where yield is highly sought after. This pursuit of enhanced yield is much of what drove the explosive growth of restaking, as stakers flocked to the opportunity to earn more from the same assets, though the additional yield comes inseparably bound to additional risk.
For new networks and services, the central benefit is access to economic security that they could not feasibly build on their own, dramatically lowering the barrier to launching a secure protocol. A new service that requires economic security to function would traditionally need to attract its own large pool of staked capital, a slow and difficult process that requires convincing many people to stake a new and unproven token, but restaking allows the service to tap into the established security of a major network’s stakers instead, renting security rather than building it. This enables new projects to launch with substantial security from the outset, accelerating innovation by removing one of the major obstacles to creating new secured services and allowing a flourishing of applications that need security but could not easily bootstrap it. The ability to access shared security is a genuine enabler of new development, and it is much of why restaking attracted not just stakers seeking yield but a wave of new projects seeking the security that restaking could provide.
For the broader ecosystem, the benefits lie in capital efficiency and the innovation that shared security enables, making the entire system more productive. By allowing the same staked capital to secure many things at once, restaking uses the ecosystem’s security capital more efficiently than dedicating separate capital to each service would, and this efficiency, combined with the lowered barrier to launching secured services, can spur a proliferation of new applications and infrastructure that enrich the ecosystem. The model can also strengthen the value and utility of the base network’s token, since restaking creates additional demand and uses for staked assets, and it represents a genuine innovation in how blockchain security can be provisioned and shared. These ecosystem-level benefits, the efficient use of security capital and the enabling of new development, are real and significant, and they explain why restaking, despite its risks, came to be seen as an important advance, even as the same shared security that creates these benefits also creates the interconnections through which risk can spread, making the ecosystem-level effects a double-edged matter of both enhanced productivity and increased systemic fragility.
Risks, Compound Slashing, and Systemic Contagion
The most direct risk is compound slashing, the accumulation of multiple, independent conditions under which a staker’s capital can be confiscated, which makes restaking inherently riskier than simple staking. A restaker’s capital is exposed to the slashing rules of every service it helps secure, so that misbehavior or failure with respect to any of them, whether caused by the staker’s chosen operator, by a flaw or attack in a service, or by a poorly designed slashing condition, can result in the loss of the shared stake. The more services a restaker commits to in pursuit of higher rewards, the more sources of potential slashing they accumulate, and the reliance on operators and on the correct design of many services means that much of this risk is beyond the staker’s direct control. This compounding of slashing risk is the fundamental danger of the restaking model, transforming the single, well-understood risk of staking into a multiplicity of risks that are harder to assess and that grow with the pursuit of yield.
The fragility of layered leverage and the danger of cascading liquidations form a second serious risk, demonstrated vividly in real incidents. The towers of staking, restaking, liquid tokens, and leverage built in the ecosystem are fragile, because they depend on liquid restaking tokens maintaining their value, and a small loss of peg can trigger forced liquidations that drive the value down further in a cascade, inflicting losses across all the leverage and lending built on the token. The difficulty of quickly redeeming the underlying assets, especially when protocols have not enabled withdrawals, disables the arbitrage that would normally keep a liquid token at its proper value, allowing depegs to occur and persist, and such an event in the restaking ecosystem caused a liquid restaking token to fall far below its expected value and triggered tens of millions of dollars in liquidations across decentralized finance. This fragility means that the layered structures of restaking can unwind violently, and that participants in the upper layers, particularly those using leverage, face the risk of sudden and severe losses from dynamics they may not fully understand.
The deepest concern is systemic contagion and the overloading of base-network security, the risk that restaking concentrates and entangles risk in ways that could threaten not just individual participants but the broader ecosystem and even the base network itself. Because vast amounts of capital are committed through restaking and the same stake secures many services, the system has been described as potentially too interconnected to fail safely, with the worry that the failure of a large operator or service, or a cascade through the layered structures, could degrade many services at once and spread losses widely. There is also the more fundamental concern, voiced by prominent figures in the ecosystem, that using the security of a base network for many additional purposes overloads its consensus and social trust, potentially introducing systemic risks to the foundational network that everything depends on, and that this overloading should be resisted. The concentration of capital, the entanglement of risks, the fragility of the layered structures, and the potential threat to the base network combine to make systemic risk the gravest danger of restaking, one that extends beyond the individual staker to the stability of the entire ecosystem. None of these risks negates the genuine innovation and benefits of restaking, but together they make clear that the compound security model trades isolation for efficiency in a way that creates serious and interconnected dangers, demanding caution, careful design, and a sober recognition that the pursuit of yield through stacked risk can end in compounded loss.
Real-World Implementations and Measured Outcomes
The restaking model and its risks are embodied in real protocols and have produced documented outcomes, and three examples illustrate both the explosive growth of restaking and the materialization of its dangers. These cases span the protocol that pioneered and dominates restaking, a real incident in which the layered risks of liquid restaking produced a cascade of losses, and the prominent warnings that have accompanied the model’s rise, together demonstrating that restaking is both a genuine and rapidly adopted innovation and a source of real, realized risk. Each is grounded in documented developments and figures, showing the model functioning at scale and its dangers proving concrete rather than hypothetical.
EigenLayer exemplifies the restaking model and its remarkable growth, having pioneered and come to dominate the sector. The protocol allows assets staked to secure a major proof-of-stake network to be restaked to secure additional services, which it calls actively validated services, extending the network’s economic security to new networks and applications while earning stakers additional rewards. Its growth was extraordinary, expanding from around a billion dollars in total value locked to well over eighteen billion through 2024, and the broader restaking ecosystem it anchors grew to tens of billions of dollars, with EigenLayer representing the large majority of the restaking market. This explosive growth demonstrated the powerful appeal of the model, as enormous amounts of capital flowed in to pursue the additional yield and as new services adopted restaking to bootstrap their security. The speed of this accumulation was itself a source of concern to careful observers, because tens of billions of dollars committed to an unproven and complex mechanism in a matter of months left little time for the risks to be understood or for the systems to be battle-tested before they reached a scale at which their failure could have significant consequences. Much of the early inflow was also driven by the expectation of token rewards, with participants restaking partly in anticipation of receiving valuable new tokens, which meant that a substantial portion of the capital was motivated by speculation about future airdrops rather than by considered judgments about the soundness of the underlying services. This dynamic, in which yield-seeking and reward speculation drove rapid growth ahead of a mature understanding of the risks, is a recurring pattern in decentralized finance, and it helped create exactly the conditions, large amounts of leveraged and layered capital in a young system, that make a sudden unwinding both more likely and more damaging when sentiment shifts or an incident occurs. At the same time, EigenLayer embodies the compound security model and its risks, since restakers using it inherit the slashing conditions of every service they secure, accumulating the compounded exposure that defines the model, and its scale makes it the central example of both the promise and the systemic significance of restaking, the protocol whose dominance means that the soundness of the entire sector substantially depends on its design and stability.
The depeg of a major liquid restaking token in April 2024 exemplifies the materialization of the layered risks of restaking, providing a concrete demonstration of how the compounded structure can unwind. A leading liquid restaking protocol issued a token representing restaked positions, which was used widely as collateral for borrowing and leverage across decentralized finance, building the kind of layered structure described in this article. Following an announcement related to the protocol’s token, the liquid restaking token lost its peg, falling sharply on decentralized exchanges to a fraction of its expected value, with reports of it dropping to as low as several hundred dollars against an expected value in the thousands. Crucially, because the protocol had not enabled withdrawals, the arbitrage that would normally restore the peg by redeeming the token for its underlying assets was not possible, allowing the depeg to deepen, and the falling value triggered the liquidation of loans collateralized by the token, causing a cascade of forced selling and resulting in tens of millions of dollars in liquidations across lending protocols. This incident vividly demonstrated the fragility of the layered leverage built on restaking, showing how a loss of peg, amplified by leverage and unmitigated by impaired redemption, could rapidly inflict significant losses, a real-world confirmation of the compound risk that the model carries.
The prominent warnings about restaking, including those from Ethereum’s co-founder, exemplify the serious concern that the model has provoked even amid its growth, providing authoritative caution about its systemic dangers. In a notable essay, Ethereum co-founder Vitalik Buterin warned against overloading the base network’s consensus, specifically in the context of restaking, arguing that using the network’s core security mechanism for additional purposes could bring high systemic risks to the ecosystem and should be discouraged and resisted. This warning, from one of the most influential figures in the ecosystem, reflected the deep concern that restaking, by extending and overloading the foundational security of the base network and by concentrating and entangling risk, could endanger not just individual participants but the stability of the broader system and the base network itself. The seriousness with which such warnings were voiced, even as restaking grew explosively, underscores the genuine and recognized nature of its systemic risks, and it represents an important counterweight to the enthusiasm that drove the model’s adoption. Taken together, these three examples, the dominant protocol’s explosive growth, the real incident of layered risk producing a cascade of losses, and the authoritative warnings about systemic danger, demonstrate that restaking is simultaneously a powerful and rapidly adopted innovation and a source of serious, realized, and recognized risk, embodying the dual nature of the compound security model in concrete and documented form.
Final Thoughts
Restaking and the compound security models it creates represent one of the more striking innovations and one of the more serious risk concentrations to emerge in decentralized finance, capturing in a single mechanism both the creativity and the hazard of the field. The core idea, that staked capital securing one network could simultaneously secure others, is genuinely clever and addresses a real need, allowing capital to be used more efficiently and giving new projects access to security they could not otherwise afford. The explosive growth of restaking, attracting tens of billions of dollars in a short time, demonstrated the powerful appeal of earning more from the same capital and renting rather than building security. Yet this same efficiency is achieved by sharing security, and shared security means entangled risk, so that the model’s central virtue and its central danger spring from the identical source, the reuse of one pool of capital to back many things at once.
The broader significance of restaking lies in what it reveals about the trade-off between efficiency and safety in interconnected financial systems. The careful isolation that keeps the failure of one component from spreading to others is a form of safety, and restaking deliberately sacrifices that isolation in pursuit of the efficiency of shared security, creating interconnections through which trouble can propagate. The layering of liquid restaking and leverage on top compounds this, building fragile towers of stacked dependencies in which risk multiplies and transparency diminishes, as the real incident of a depegging token and cascading liquidations showed. The systemic dimension, the concern that restaking could overload the base network’s security and concentrate risk in ways that threaten the whole ecosystem, raises the stakes beyond individual participants to the stability of the foundational systems everything depends on, which is why prominent figures warned so seriously against overloading consensus even as the model grew.
The responsibility that this situation demands falls on protocol designers, participants, and the ecosystem to manage the compounded risks with the seriousness they require. Designers bear a duty to build restaking systems with careful attention to slashing conditions, operator quality, redemption mechanisms, and the limits of safe layering, and to communicate the risks honestly rather than emphasizing yield alone. Participants bear a responsibility to understand the compounded and layered nature of the risks they take, to be especially wary of leverage built on liquid restaking tokens, and to commit only what they can afford to lose. The ecosystem as a whole bears a responsibility to attend to the systemic dangers and to avoid allowing the pursuit of yield to build interconnections so dense and fragile that a failure in one place could threaten the stability of the whole.
The most balanced understanding is that restaking is a powerful and genuinely innovative mechanism whose compound security model creates efficiency and enables new development while concentrating and entangling risk in ways that demand great care. As the model matures and its risks become better understood through both analysis and painful experience, the hope is that restaking can deliver its benefits while containing its dangers, retaining the efficiency of shared security without succumbing to the fragility of overloaded and over-leveraged structures. That outcome depends on taking the systemic risks as seriously as the rewards and on remembering that in interconnected systems, the same connections that distribute security also distribute risk. The enduring lesson of restaking is that efficiency and safety stand in tension, that shared security is entangled security, and that the responsible pursuit of the model’s genuine benefits requires a sober and constant respect for the compounded dangers that are inseparable from them.
FAQs
- What is staking?
Staking is the mechanism by which many modern blockchains secure themselves under a system called proof of stake. Participants called validators lock up a quantity of the network’s cryptocurrency as a stake, a financial commitment to behave honestly. Validators who behave correctly earn rewards, while those who misbehave can have part of their stake confiscated through a penalty called slashing. The threat of losing staked assets keeps validators honest, and the total amount staked represents the economic security backing the network, since attacking it would require risking enormous capital. - What is restaking?
Restaking is the practice of using staked capital that already secures one network to simultaneously secure additional services. Normally, staked assets do only one job, but restaking allows those same assets, or claims on them, to be committed to securing other networks or applications at the same time, so the capital is reused to provide security in multiple places. The staker earns additional rewards for this, and new services gain access to economic security they could not easily build on their own, but the staker’s risk accumulates across everything their capital secures. - What is a compound security model?
A compound security model is one in which the same staked capital simultaneously backs multiple networks or services and is subject to the rules and penalties of each. Where a normal staker faces the slashing conditions of a single network, a restaker faces the slashing conditions of every service their assets help secure, so their capital can be penalized for failures across any of them. The security each service receives is real but shared rather than dedicated, and the risks the staker bears are compounded rather than singular, which is the fundamental trade-off restaking embodies. - What are actively validated services?
Actively validated services are the additional networks, applications, or protocols that restaked capital secures in the leading restaking model. These are new services that need economic security to function but use the restaked capital of an established network rather than building their own dedicated stake. By committing their assets to secure such a service, restakers extend the base network’s security to it and earn additional rewards, while the service launches with substantial security from the outset. Each such service imposes its own slashing conditions on the shared stake, accumulating the restaker’s risk. - What is a liquid restaking token?
A liquid restaking token is a tradeable token representing a restaked position, issued by liquid restaking protocols to address the illiquidity of restaked assets. When a user restakes, their assets become locked, but a liquid restaking protocol gives them a token representing that position which they can trade or use elsewhere while the underlying assets remain restaked. This adds capital efficiency but also a layer of abstraction and dependency, since the token’s value depends on the underlying assets and the issuing protocol remaining sound, and using it for leverage stacks further risk. - Why is restaking riskier than normal staking?
Because risk compounds. A normal staker faces only the slashing rules of a single network, but a restaker faces the slashing conditions of every service their capital helps secure, accumulating multiple independent sources of potential loss. Their capital also depends on the operators who manage the stake and on the correct design of many services, much of which is beyond their direct control. The layering of liquid restaking and leverage on top adds still more risk, building fragile structures in which a problem at any level can cascade, making restaking substantially more dangerous than simple staking. - What happened in the liquid restaking token depeg of April 2024?
A major liquid restaking token, widely used as collateral for borrowing and leverage, lost its peg following an announcement related to its protocol, falling sharply on decentralized exchanges to a fraction of its expected value. Because the protocol had not enabled withdrawals, the arbitrage that would normally restore the peg by redeeming the token was not possible, so the depeg deepened. The falling value triggered the liquidation of loans collateralized by the token, causing a cascade of forced selling and tens of millions of dollars in liquidations, vividly demonstrating the fragility of layered leverage built on restaking. - Why did Vitalik Buterin warn about restaking?
In a notable essay, Ethereum’s co-founder warned against overloading the base network’s consensus, specifically in the context of restaking, arguing that using the network’s core security mechanism for additional purposes could bring high systemic risks to the ecosystem and should be discouraged and resisted. The concern was that restaking, by extending and overloading the foundational security of the base network and by concentrating and entangling risk, could endanger not just individual participants but the stability of the broader system and the base network itself, on which everything depends. - What is systemic contagion in restaking?
Systemic contagion is the risk that problems spread through the interconnected restaking ecosystem to harm many participants and services at once. Because vast capital is committed through restaking and the same stake secures many services, the failure of a large operator or service, or a cascade through the layered structures of liquid tokens and leverage, could degrade many services simultaneously and spread losses widely. The concentration of capital and entanglement of risk have led to concerns that the system is too interconnected to fail safely, making contagion one of the gravest dangers of the compound security model. - How can participants reduce their restaking risk?
Participants cannot eliminate the compounded risks but can reduce their exposure. Prudent steps include understanding the layered and compounded nature of the risks rather than focusing only on yield, being especially cautious about leverage built on liquid restaking tokens, which can unwind violently, choosing reputable operators and well-designed services, limiting the number of services and the amount of leverage they take on, and committing only capital they can afford to lose. Recognizing that the pursuit of higher yield through stacked risk increases the chance of compounded loss, and that redemption may be slow or impaired, is essential to using restaking responsibly.