Curriculum·J312 Insurance, Hedging, and On-Chain Risk Transfer·about 43 min
Building a coverage decision
By the end of this lesson you can
- →Run the five-step decision that ends in buy, reduce, or retain
- →Compute the effective payout probability rather than the sum insured
- →Derive the break-even loss probability that a quoted premium implies
- →Explain why a break-even high enough to justify cover is usually an argument against the position
Junior · enrolled learners
This lesson opens with Cover Protocol, 28 December 2020.
- What happened
- Cover Protocol sold cover against smart contract failure. On 28 December 2020 a bug in its own Blacksmith liquidity mining contract allowed effectively unlimited minting of the COVER token. The contract cached pool data in memory to save gas, updated the pool data in storage, and then reused the stale cached value in a later calculation. Attackers minted enormous quantities and sold them, CipherTrace reporting more than $4.4M drained and the token's value down by nearly 99 percent. The largest of them, a party operating as Grap Finance, burned most of what it had minted and returned 4,350 ETH; CipherTrace describes what Grap took as roughly $4M worth of COVER.
- The decision point
- The product was protection against a smart contract failing. The failure was a smart contract in the protocol selling the protection. Per J312-01 the fourth condition of insurability is a solvent payer, and an on-chain payer is itself a contract with the property it is insuring against. Any coverage decision has to price that, which means the payout you are buying is never the sum insured.
- Recorded loss
- $4,400,000
What you will be able to answer
- →What are the five steps?
- →What is the effective payout?
- →How do you derive the break-even?
- →What does a high break-even tell you?
Orientation and Year One are open: anyone can read them without an account. From Year Two onward the lessons are for enrolled learners, because progress through the later years only means anything if it is tracked against a record.
It is free. We do not sell the list and there is nothing to buy at the end of it.
Sources and review
- https://mudit.blog/cover-protocol-hack-analysis-tokens-minted-exploit/
- https://peckshield.medium.com/cover-incident-the-unlimited-token-minting-vulnerability-f3afd9d2405c
- https://web.archive.org/web/20231204004707/https://ciphertrace.com/infinite-minting-exploit-nets-attacker-4-4m/
- https://docs.nexusmutual.io/overview/claims-history/ftx/
- https://cointelegraph.com/news/cover-protocol-suffers-infinite-minting-attack-price-tanks-97
Confidence high·Volatility medium·Reviewed 2026-08-06·Owner unassigned
Contested
The three probabilities in part two, being 0.90 that a claim is admitted, 0.95 that the pool is solvent and 0.98 that the cover contract holds, are illustrative inputs shown on the page so the calculation can be re-run with your own. They are loosely anchored to the published FTX claim outcome of 24 approvals from 27 filings and to the pool capacity derived in J312-02, and they are not estimates. The method is the transferable part.
Reported figures for the Cover Protocol incident vary. CipherTrace reports more than $4.4M drained and describes the party operating as Grap Finance as minting roughly $4M worth of COVER and returning it, while Mudit Gupta's analysis gives the largest attacker returning 4,350 ETH. The accounts describe the same returned proceeds in different units, and how much of the total was returned is not precisely established. The mechanism is well documented and the totals are not precise. The size of the token's fall is reported differently too: CipherTrace says nearly 99 percent, Cointelegraph's same-day report says more than 97 percent, and a later Cointelegraph explainer gives over $700 to less than $5 in hours without a source for the prices. The lesson uses CipherTrace's figure.