Bitcoin Mining Business Interruption Insurance: Protecting Hash Rate Revenue

Here’s how most miners find out their BI policy doesn’t work: a fire takes down 40% of their facility, the claim goes in, and three months later the adjuster’s number is 60 cents on the dollar. The price methodology is wrong. The ERCOT curtailment credits got netted against the loss. The indemnity period is already half gone and the replacement ASICs haven’t shipped.

Business interruption insurance should be simple — you stop producing, it pays what you lost. For mining, it isn’t. The revenue calculation alone requires methodology decisions that standard BI language never contemplates. And in Texas, the ERCOT curtailment economics create disputes that are genuinely novel. We’ve structured enough mining programs to know where the problems show up, and they almost always show up in the same places.

Why Standard BI Breaks for Mining Operations

Standard commercial BI was built for businesses with stable, documented revenue. A restaurant burns down — the adjuster pulls two years of sales records, projects forward, and calculates the loss. Clean. Bitcoin mining breaks this in three separate ways, and each one creates its own dispute.

Business interruption coverage depends heavily on how the underlying property policy is structured — particularly around equipment replacement valuation. Our breakdown of ASIC miner insurance and replacement cost vs. actual cash value explains why the valuation method you choose directly affects how much business interruption coverage you can actually collect.

Price volatility comes first. BTC can move 50%+ within a single indemnity period. Operators want the high price; insurers want the low one. Without a pre-agreed methodology, this fight happens after your facility is already dark. Network difficulty adjustment creates a subtler problem — when significant mining capacity goes offline simultaneously (a Texas winter storm, an ERCOT emergency), network difficulty drops and remaining miners earn more per TH/s. That affects what your “lost revenue” actually was, and adjusters will argue about it. The curtailment revenue interaction is the most contested issue specific to Texas: if you earn ERCOT demand response credits during the same period your facility is partially offline, the insurer’s position is that those credits offset your loss. That’s wrong — but you need policy language to prove it.

How the Hash Rate Calculation Actually Works

Specialty insurers and mining operators have landed on a methodology that works. It has three steps.

First, document your hash rate capacity. Use actual sustained TH/s from pool mining records and operational logs — typically 85–95% of theoretical maximum. Not nameplate. If you overstate capacity, you’re overstating your claim and creating disputes. The insurer will pull pool data during adjustment anyway.

Second, nail down the BTC price methodology in the policy itself. Most programs use a 90-day trailing average prior to the loss date. This kills the price dispute at inception because neither side can cherry-pick. Some Relm Insurance programs settle in BTC rather than dollars — that eliminates the conversion argument entirely, which is elegant if your operation runs BTC-denominated.

Third, deduct the variable costs that stop when you stop mining. Pool fees disappear. Power costs disappear. Fixed costs that keep running — facility rent, loan payments, key staff — those are what BI actually replaces. Your forensic accountant will reconstruct this; your job is having the documentation ready before the loss.

The ERCOT Curtailment Problem — And the Fix

This is the most Texas-specific issue in mining BI, and it’s the one we see operators miss most often.

Riot Platforms earned $30.6 million in curtailment credits in Q3 2025 alone — they get paid by ERCOT for the power they contracted but aren’t consuming during grid stress. Now run this scenario: a fire damages 30% of their Rockdale facility and reduces hash rate by 30% for four months. During those four months, ERCOT curtailment events occur. The BI claim is for lost mining revenue from damaged capacity. But Riot also received curtailment credits during the same period, because their demand response contracts are based on total contracted capacity.

The adjuster’s argument: curtailment credits represent income from the same operational capacity during the loss period. Under standard BI “net revenue” calculations, that’s a positive offset against your loss. The operator’s argument: mining revenue and curtailment revenue are completely different — one requires ASICs running, the other requires them stopped. They’re not interchangeable. Current standard policy language doesn’t resolve this clearly. You need a manuscript endorsement at inception that states ERCOT demand response credits, curtailment payments, and ancillary services revenue are not “other income” or “salvage” for BI purposes. Specialty markets — Evertas, Relm, Lloyd’s syndicates — will accept this language. If you’re earning more than 10% of gross revenue from curtailment contracts, this endorsement isn’t optional.

Waiting Periods and Indemnity Periods

The Events That Generate Zero Recovery

Most mining BI activates after a 24–72 hour waiting period. Any outage that restores before the waiting period expires produces no recovery at all. Winter Storm Fernan in January 2026 took roughly 200 EH/s offline globally — some Texas facilities came back up in 6–18 hours and got nothing. For facilities with ERCOT demand response contracts, think about this carefully: if you regularly curtail for 4–12 hours and earn more from curtailment payments than you’d earn from mining during those periods anyway, a 72-hour waiting period costs less in premium and rarely costs you in claims. For facilities without curtailment contracts, shorter waiting periods are worth the extra cost — Texas weather can cause 6–48 hour outages without physical damage.

Why Six Months Isn’t Enough

Bitmain Antminer S21 and MicroBT Whatsminer M60 lead times run 5–7 months under normal conditions — and longer after industry-wide events that drive simultaneous replacement demand. Add 2–4 months for facility reconstruction, 4–8 weeks for decontamination processing on partial losses, and ERCOT’s interconnection processes for restored large loads. A major fire in January realistically means full capacity isn’t back until September or October at the earliest.

Our recommended minimums: partial loss (20–40% capacity) — 12 months. Major loss (40–80%) — 18 months. Total loss — 24 months. The premium difference between a 12-month and 24-month indemnity period is typically 20–35% of the BI component. If BI is 20% of your total program premium, that’s roughly a 6% total cost increase. Against the risk of running out of coverage at month 13 of an 18-month recovery, the math is obvious.

Non-Physical Damage Triggers

Standard property BI requires direct physical damage to your insured property. Three common mining downtime causes don’t qualify — and operators frequently discover this at the worst possible moment.

Ransomware encrypting your ASIC management systems is not physical damage. Without a dedicated cyber BI policy, that downtime produces zero recovery. The cyber BI component needs to cover operational technology network failures and ASIC management platform compromises — not just traditional IT breaches. ERCOT curtailment orders under SB 6 are civil authority actions. Civil authority BI coverage is required, and it applies directly to Texas facilities facing mandatory curtailment. Grid-level power failures without physical equipment damage are excluded from most property BI — standalone service interruption coverage must be added separately. Each of these requires a separate coverage decision at placement. None of them appear in a standard commercial package.