SSV Restaking Explained: SSV 2.0 and Based Applications
SSV is Ethereum's largest distributed validator layer, and SSV 2.0 casts 'based applications' as a safer answer to restaking. Here is how bApps work and where the risks lie.
“SSV restaking” is a phrase that points at two related ideas at once. SSV Network is the largest distributed validator technology (DVT) layer on Ethereum, the plumbing that lets one validator run across several independent machines at the same time. Restaking, the concept popularized by EigenLayer, is the idea that already staked ETH can be reused to secure extra services. Combine the two and you arrive at the question this explainer answers: what does SSV add to the restaking debate, and how does its SSV 2.0 upgrade, branded the “based applications” protocol, change the trade-offs for validators?
The short version is that SSV wants the upside of restaking, validators earning more by securing more, without the part that keeps Ethereum researchers up at night: slashable capital stacked across many services, with contagion risk flowing back to the base layer. At roughly $2 per token in late June 2026, down more than 95% from a 2024 peak above $65 according to CoinGecko, the market has not priced in much of that ambition. Here is how the system works and where the risks sit.
What “SSV restaking” really refers to
SSV Network is not a restaking protocol in the EigenLayer sense. At its core it is DVT infrastructure: software that splits the job of running an Ethereum validator across multiple operators so no single machine, and no single company, holds the keys. The restaking label attaches to SSV through its 2.0 upgrade, which introduces “based applications” and positions the project as a direct alternative to the restaking model rather than a participant in it.
That distinction matters because the two designs solve the same business problem in opposite ways. Restaking reuses staked capital. SSV 2.0 reuses the validator itself, the duties and signing power that a validator already provides to Ethereum, while leaving the staked 32 ETH untouched. Understanding why that difference exists means starting with how SSV’s validator technology works in the first place.
SSV’s foundation: distributed validator technology
A standard Ethereum validator is a single point of failure. If the machine goes offline it misses duties, and if its key leaks the stake is at risk. DVT breaks that fragility. SSV splits a validator key into several KeyShares using threshold cryptography, then hands those shares to a set of non-trusting operators. No operator can sign on its own; the group produces a valid signature only once a quorum agrees, coordinated through an Istanbul Byzantine Fault Tolerance (IBFT) consensus process. The full key is never reassembled in one place, as the SSV documentation describes.
In practice operators run validators in clusters of four, seven, ten, or thirteen, which means a validator can keep performing even if some nodes fail or drop offline. That active-active redundancy is why large staking operations lean on SSV. Liquid staking and staking-service providers including Lido, Ether.fi, StakeWise, and P2P.org have used SSV to distribute their validators rather than trust a single operator. It is staking infrastructure first, and the restaking story is built on top of it.
How restaking works, and its hidden risks
EigenLayer turned restaking into a category. The model is straightforward: users deposit ETH or liquid staking tokens, opt that capital into Actively Validated Services (AVSs) such as data availability layers or oracles, and operators run the AVS software. In return restakers earn extra rewards, and the AVSs borrow Ethereum-grade economic security instead of bootstrapping their own. EigenLayer and its EigenDA data availability layer went live on mainnet in 2024, as The Block reported, and at its peak the protocol held well over $15 billion in deposits, per DefiLlama.
The risk arrived with enforcement. EigenLayer switched on slashing on April 17, 2025, giving AVSs the power to penalize misbehaving operators, as Cointelegraph covered. Slashing is what makes restaking credible, but it also makes the risks concrete. When the same capital backs many services, a fault in one can trigger losses that ripple outward, and critics have long warned that this cascading or contagion risk could reach back to Ethereum’s base layer. Bootstrapping is costly too, since every new service still has to attract its own pool of restaked capital. SSV 2.0 is a bet that those problems are baked into the capital-reuse approach itself.
SSV 2.0: based applications, a different path
SSV 2.0, unveiled as “the Based Applications Protocol,” reframes the validator as a reusable security asset. Based applications, or bApps, are services that borrow Ethereum’s existing validator set for security, decentralization, and Sybil resistance without standing up a separate validator network and without locking slashable capital. The SSV team lists rollups, co-processors, oracles, bridges, pre-confirmations, and sequencing services as candidate bApps, according to the project’s own write-up.
The pitch, echoed in Cointelegraph’s coverage, is an “infinite-sum” security model. Because a validator commits its duties rather than redeployed principal, it can serve many bApps at once without splitting a fixed pot of collateral. More validators strengthen every bApp, and more bApps create more ways for validators to earn, so participation is meant to compound value rather than divide it. Slashable exposure is optional: holders can stake a committed form of the token, cSSV, to add slashable economic security where a bApp needs it, but the underlying 32 ETH stays put. SSV Labs opened the SSV 2.0 testnet on Ethereum’s Hoodi test network in 2025 and has been rolling out the protocol in phases, with a dedicated bApp chain planned as the first live based application and cross-chain coordination with networks like Solana and Cosmos on the roadmap.
bApps vs restaking: a side-by-side look
| Dimension | Restaking (EigenLayer model) | SSV based applications (bApps) |
|---|---|---|
| What gets reused | Staked ETH or LST capital, redeployed as slashable collateral | The validator’s duties and signing power; the 32 ETH principal stays put |
| Slashing exposure | Restaked capital is slashable by each service, so risk stacks | Core duties stay non-slashable; only optional cSSV or delegated tokens are slashable |
| Security math | Closer to zero-sum: one pool of capital split across services | Framed as infinite-sum: more validators and more bApps both add value |
| Bootstrapping cost | Each new service must attract its own restaked capital | bApps borrow Ethereum’s existing validator set from day one |
| Main risk | Cascading slashing and possible contagion to Ethereum | Smart contract and adoption risk; a lighter contagion path |
| Status in 2026 | Slashing live since April 2025; multi-billion-dollar TVL | Testnet in 2025; phased mainnet rollout through 2026 |
The SSV token’s expanded role: fees, staking, and burning
SSV 2.0 gives the token more to do than pay for DVT service. The redesigned model layers three kinds of fees. The first is a fixed network fee, set at roughly 1% of Ethereum staking APR, charged on validators using the base DVT layer. The second is variable, paid when a validator or operator opts into a given bApp. The third is a transaction fee on the bApp chain that scales with congestion. Operators secure that chain by staking cSSV, a slashable commitment, which ties the token directly to the network’s security rather than only to its revenue.
The supply side is the headline change. The protocol burns collected fees in proportion to the amount of SSV staked, so heavier participation pulls more tokens out of circulation. SSV’s own materials project that the network could turn deflationary somewhere between 2027 and 2029, depending on adoption, especially after the incentivized mainnet emissions program wound down at the end of 2025. Token holders still steer these levers through the DAO, which votes on minting and parameters through the SSV governance forum and Snapshot. Whether the burn outpaces emissions in practice is the open question for the token’s long-term value.
SSV by the numbers
The infrastructure is real and widely used, whatever the token chart says. SSV crossed one million ETH staked through its operators in mid-2024, a milestone announced via Chainwire. By early 2025, SSV’s reported figures put secured value above $6.8 billion across more than 50,000 validators, and through 2025 those counts kept climbing into six figures, supported by around 80 ecosystem partners.
The token tells a different story. SSV trades near $2, with a circulating supply close to 15 million and a market capitalization around $30 million, per CoinGecko, against an all-time high of $65.82 set in 2024. That leaves the curious situation of a token worth a few tens of millions of dollars sitting underneath infrastructure that secures tens of billions. Bulls read that gap as deep undervaluation; skeptics read it as the market doubting that SSV can convert raw secured value into token cash flow. SSV 2.0 is the attempt to close it.
What the SEC’s 2025 staking guidance means for SSV
For US readers, the regulatory weather improved in 2025. On May 29, the SEC’s Division of Corporation Finance issued a statement concluding that certain protocol staking activities, including self-staking and both custodial and non-custodial staking-as-a-service, are not securities transactions under the federal securities laws. A follow-up statement on August 5 extended similar reasoning to certain liquid staking arrangements and staking receipt tokens.
That backdrop helps the operators, pools, and service providers that sit on top of SSV’s DVT layer, since the staking activity they perform is the kind the SEC staff described. Two cautions belong in the same breath. First, these are staff views, not formal commission rules; they do not change the law, and at least one commissioner dissented, so a future SEC could revisit them. Second, the guidance addresses staking, not the newer questions raised by restaking and shared-security tokens, where an operator stakes a token like cSSV to earn fees from third-party applications. That model sits closer to the line the staff did not draw, and the SSV token’s own status is a separate matter the statements did not resolve.
Risks, timeline, and what to watch
The honest summary is that SSV 2.0 is a promising design still proving itself. Execution risk is front and center: the based-applications protocol has moved through testnet and a phased mainnet rollout, but the bApp chain and full cross-chain coordination are still maturing, and a security model is only as good as the code that enforces it. Adoption is the next hurdle, because an infinite-sum security model means nothing without real bApps choosing to launch on it instead of on EigenLayer, which still dwarfs every rival by deposits, or newer entrants such as Symbiotic and Karak.
Watch three things over the rest of 2026: how many bApps actually go live and generate fees, whether the burn mechanism starts to bite as the DAO winds down emissions, and whether US and global regulators extend their friendlier staking stance to shared-security models or treat them as something riskier. SSV has the strongest validator infrastructure in Ethereum staking and a coherent thesis for what comes next. The open question is no longer whether distributed validators work, but whether “based” security can pull validators away from the restaking model that got there first.
By the HOGE Wire staking desk.