Cloud Mining Contract Due Diligence: 12-Point Risk Checklist

We Get Pitched These Contracts Every Week

We run a hosting farm, not a cloud mining desk, but we still get cloud mining contracts forwarded to us at least once a week — usually from a customer asking "is this legit?" Most of the time the headline ROI looks fine. The problem is never the headline. It's buried three paragraphs into the terms, in a clause about "maintenance fees" or "force majeure" that quietly resets the whole deal.

Before anyone here signs — or tells a customer to sign — we run the contract through the same twelve checks every time. None of them are exotic. Most of them just take longer than five minutes, which is exactly why people skip them.

The 12 Things We Actually Check

• Can you verify the counterparty's legal registration, or is it just a logo and a Telegram handle?
• Does the contract spell out duration, renewal, and how you get out early — not just how you get in?
• Is the fee model fixed, variable, or blended, and does the math still work if BTC price drops 40%?
• Are maintenance, power, and "service" charges itemized, or lumped into one vague monthly deduction?
• Is the payout schedule and settlement method (on-chain, custodial wallet, exchange credit) written down?
• What happens to your payout during downtime — do you get compensated, or just... nothing?
• Does the hashrate delivery commitment have a measurable SLA with a number attached, not just "best effort"?
• Which jurisdiction governs disputes, and is that somewhere you could realistically pursue a claim?
• Who actually controls the wallet and payout address — you, or them?
• Is the force majeure clause reasonable, or broad enough to excuse almost anything?
• Can you independently check this operator's uptime history, or are you only trusting their own dashboard?
• Is the support response time realistic and actually enforceable, or just a line in the marketing deck?

Run the Downside Case Before You Run the Best Case

We model three scenarios on every contract we look at: base case, downside, and stress. Downside usually means BTC price down 30-40% from today and network difficulty up another 8-10% at the next retarget — Bitcoin difficulty adjusts roughly every two weeks, and it's trended upward for most of the last two years. If the contract only breaks even in the best-case column, that's not a marginal deal. It's a bet dressed up as a hosting product.

If you can't model fees and downtime clearly from the contract text alone, treat it as high risk no matter what the headline ROI says.

Honest caveat: even a contract that checks every box above can still go sideways. Paper terms don't stop an operator from having a bad month, a power curtailment, or a wallet migration that delays payouts by a week. Due diligence lowers your odds of getting burned by something avoidable — it doesn't remove operational risk from mining itself.

Red Flags That Should Stop You Cold

A few patterns come up often enough that we've stopped giving them the benefit of the doubt. If the support team only communicates through a group chat and never a ticket system with a timestamp, that's not a channel, that's a way to lose a paper trail. If the payout wallet is described as managed for your convenience with no address you control, you don't actually have a payout, you have a promise. And if the sales page emphasizes historical returns more than current fee structure, ask why — historical returns from a bull run tell you nothing about a contract signed today at today's difficulty.

Where This Fits If You're Comparing Options

If you're weighing a cloud contract against buying and hosting your own hardware, run both models through our profitability calculator with the same downside assumptions. It won't tell you which operator is honest, but it'll show you fast whether the numbers even survive a bad quarter. We'd rather a customer walk away from a contract after twenty minutes of checking than sign something they never actually understood.