Cloud Mining Contracts: A Buyer's Checklist Before You Pay

Write down exactly what the purchase provides

Begin with a one-sentence description in your own words: for example, a stated amount of SHA-256 hashrate delivered to an eligible pool for a specified period. Then check that the contract supports every part of that description. A photograph of a miner does not establish that the customer owns the machine.

Record the named contracting entity, product, order identifier, algorithm, amount and unit. Note the activation trigger: payment, a future start date, hardware commissioning or a separate customer action. Identify the end condition and any extension rule. If the service uses an open-ended term, write down the events that can end it rather than assuming it lasts indefinitely.

Keep ownership and service access separate. S23's model is holding a token that represents hashrate ownership, with staking activating deployment. A fixed-term service checklist remains useful, but token custody, unstaking and sale mechanics require additional entries. See the comparison of rental, cloud mining and token ownership.

Use an evidence worksheet rather than a yes/no impression

For each row, store the exact page or document, the relevant section, the date checked and the unanswered question. Mark conflicting order-page and general-term wording as unresolved. This worksheet records what you found; it does not establish legal enforceability.

For a business purchase, attach the completed sheet to the internal approval record. A blank answer should stay visible until someone can supply the source.

Read price and interruption clauses together

A recurring charge can change the economics after payment. Ask which tariff applies, how increases are communicated, when payment is due and whether unpaid fees can stop delivery. If revenue becomes lower than operating charges, find out who decides whether the service continues.

As a concrete example, Bitdeer's public agreement describes suspension under certain unfavorable mining economics and says that such suspension does not extend the service duration. Its agreement also has distinct cancellation and refund provisions. This illustrates why a headline duration does not answer every delivery question. Consult the actual agreement and order that apply to your purchase. Bitdeer service agreement, sections VI and VII.

Run a simple stress question: if a 30-day service stops for ten days, do you receive 20 days of work, an extended end date, a credit or another remedy? Do not insert a favorable assumption because the marketing page is silent. Compare the full bill with the mining cost worksheet.

Identify who measures work and who pays

Ask for the measurement location and interval used to assess delivery. Provider allocation, a worker's reported rate and accepted work at the mining pool are different records. Preserve matching timestamps and units when comparing them. A five-minute screenshot and a daily average do not establish the same thing.

Separate mined revenue, an internal credited balance and an on-chain wallet payment. Record the payout method, pool charge, threshold, schedule and any identity-verification requirement. Check how a small residual balance is treated when the contract ends. Also ask whether earnings are paid directly by the pool or first held by the service.

An operational evidence package can contain the order, a redacted pool report for the service interval, a fee breakdown and a confirmed payout transaction. It should not contain private keys, seed phrases or reusable pool credentials. Those are unnecessary for comparing contractual delivery with payment.

Document the exit before activating

Record whether cancellation is available, what notice is required, which prepaid amounts are refundable and whether any administrative charge applies. For a token-based arrangement, separately record the steps for ending active deployment, releasing the token and selling it. An unstake request is not a completed token sale.

S23 holders retain their tokens while mining, but that fact alone does not determine a future sale price, market depth or release timing. Use the current staking application for applicable operational conditions and the holding, unstaking and selling guide to keep those stages distinct.

Apply the same worksheet to Segments and any other provider. This article provides a practical comparison process, not a finding that any operator is solvent or that a clause is enforceable in your jurisdiction. Keep the final order and applicable terms with the evidence sheet, then revisit unresolved questions before making the purchase. The cloud mining guide explains the broader service models.