Nexus Mutual, InsurAce, Neptune Mutual and Sherlock-style protocol cover is priced as an annual percentage of your deposit. This tool runs the expected-value math against your own assumed exploit probability, so you can see exactly where buying cover beats self-insuring — and where it doesn't.
✓ No signup✓ Editable premium presets✓ Breakeven probability shown✓ Sensitivity table✓ Honest about uncertainty
Net expected value of buying cover
—
Sensitivity: does the verdict flip?
Same deposit, premium and loss-given-exploit assumptions, swept across a range of exploit probabilities you might believe. Your breakeven row is highlighted — above it, cover wins in expected-value terms; below it, self-insuring wins.
Assumed exploit probability
Expected loss
Premium cost (fixed)
Net expected value
How it works
Cover pools price premiums by assessing the aggregate risk of a protocol — audit history, TVL, code complexity, time in production, and how similar contracts have fared elsewhere — and setting a rate that (in theory) covers expected claims across everyone buying cover on that protocol plus a margin for the pool's capital providers. That rate is the pool's collective bet on exploit probability, expressed as a price. Your side of the trade is different: you're not pricing a whole pool, you're deciding whether to transfer your own risk for a fee, and that decision necessarily runs through your personal belief about how likely an exploit actually is this year — a number nobody can give you with certainty, because past exploit rates are a thin, noisy sample and the next exploit doesn't care what happened last year. The expected-value math this calculator runs (premium cost vs. probability-weighted expected loss) tells you whether cover is a good bet on average, over many repeated years at your stated probability. It does not tell you what to do. A risk-averse person can rationally buy cover even when the expected value is negative — that's the same logic behind why people buy home and car insurance despite insurers being profitable on average, because a single large loss (losing the whole deposit) can matter more than the expected-value math suggests if you can't easily absorb it. This tool models the arithmetic honestly; it is not investment advice and does not know your risk tolerance, your protocol's actual risk, or the future.
Reading the numbers
At the defaults — a $100,000 deposit, a 6% APY premium, an 80% loss-given-exploit assumption, a 5% assumed annual exploit probability, and a full 365-day cover period — the premium cost is $100,000 × 6% × (365/365) = $6,000. The expected loss for the period is $100,000 × 5% × 80% × (365/365) = $4,000. Net expected value is $4,000 − $6,000 = −$2,000: at a 5% assumed exploit probability, cover costs $2,000 more than the expected loss it protects against, so self-insuring has the better expected value here. The breakeven probability — where premium cost exactly equals expected loss — is premiumRate ÷ lossGivenExploit × 100 = 6 ÷ 80 × 100 = 7.5%. Only if you believe the real annual odds of an exploit hitting this specific protocol exceed 7.5% does buying cover flip to positive expected value at this premium and loss assumption. Shorten the cover period and both the premium cost and the expected loss scale down proportionally together, so the breakeven probability itself doesn't move — it only depends on the premium rate and loss-given-exploit ratio, not on how many days you're covering.
Cover premiums on protocols like Nexus Mutual, InsurAce, Neptune Mutual and Sherlock are quoted as an annualized percentage of the amount you want covered, and that rate moves with how the pool assesses the underlying protocol's risk. Battle-tested, heavily audited blue-chip protocols such as Aave or Compound have historically priced in the 2-3% APY range because claims assessors and staked capital providers see a long track record and formally verified or repeatedly audited code. Mid-tier protocols with shorter histories or more complex mechanisms often land closer to 5-8% APY. Newer or unaudited protocols, or ones running novel mechanisms nobody has stress-tested in production, can be quoted well into the 10-15%+ range if a pool is willing to underwrite them at all — some protocols simply aren't coverable at any price because underwriters won't take the risk. Rates also fluctuate with capacity: if a lot of capital is staked against a given protocol's risk, premiums tend to fall, and they spike after a nearby exploit shakes confidence in a whole category of contracts. Always check the live quote on the cover marketplace itself; this calculator uses illustrative presets, not a real-time feed.
Is buying cover worth it mathematically?
Only if you believe the annual probability of an exploit is higher than the breakeven probability this calculator computes as premiumRate divided by lossGivenExploit. At a 6% premium and an assumed 80% loss in a worst case exploit, the breakeven sits at 7.5% — meaning if you genuinely think there's better than a 7.5% chance of a covered exploit hitting your deposit this year, buying cover has positive expected value, and below that threshold self-insuring (pocketing the premium and eating losses if they occur) wins on average. The catch is that nobody has a reliable number for 'true' annual exploit probability — it's a judgment call informed by audit history, TVL, protocol age, and how novel the code is, not a quoted statistic. That's exactly why this tool asks you to input your own assumption rather than pretending to know it for you. Treat the output as a sensitivity check on your belief, not a verdict.
What percentage of a deposit is usually lost in an exploit?
It varies enormously and full 100% loss is actually less common than people assume. Flash-loan and oracle-manipulation exploits often drain a specific pool or market within a protocol rather than every vault, so a user with exposure spread across several markets might lose only the affected slice of their deposit. Reentrancy bugs and access-control failures, by contrast, have produced near-total drains of affected contracts in incidents like the 2022 Wormhole and Nomad bridge exploits. Governance attacks and admin-key compromises tend to be close to total loss for anyone with funds in the compromised contract at the time. Because of this spread, defaulting to 100% loss-given-exploit overstates your expected loss and understates how attractive self-insuring looks; defaulting to something very low understates real risk. This calculator defaults to 80% as a conservative-but-not-worst-case estimate, and you should adjust it based on how concentrated your deposit is and how the specific protocol's contracts are architected — a single-vault deposit in an unaudited contract deserves a higher assumption than a diversified position across a mature multi-market protocol.
What's the difference between cover and insurance?
DeFi 'cover' products are deliberately not called insurance in most jurisdictions because they don't work like regulated insurance and the industry avoids the legal and regulatory obligations that word carries. Traditional insurance is underwritten by a licensed carrier, backed by regulatory capital requirements, and a denied claim can be escalated through a legal or regulatory complaints process. DeFi cover pools like Nexus Mutual instead pool staked capital from members, and claims are typically assessed and voted on by other stakers or a designated assessment process defined in the protocol's rules — there's no guarantee of payout, no regulator forcing the pool to hold reserves against a bad quarter, and a claim can be rejected by the assessment mechanism even when you believe you clearly qualify. Payouts are also usually capped by how much capital the pool has staked against that specific protocol, so in a mass-exploit scenario where many members claim simultaneously, payouts could theoretically be pro-rated or delayed. It functions like insurance in that you pay a premium to transfer risk, but the legal protections, guarantees, and recourse mechanisms of regulated insurance are largely absent — you're relying on a smart contract and a community process, not a licensed insurer's balance sheet.