Cloud Mining and Hashrate Rental Calculators: Inputs That Matter

Record the source, unit and meaning of each input

Before calculating, make an input register. For hashrate, specify TH/s and whether it is advertised, allocated or measured as accepted work. For time, use days or convert hours to days. For revenue, record the currency, rate denominator, observation time and whether the source includes pool deductions.

• Hashrate: the rate being modeled and its measurement basis.
• Runtime: the interval and whether downtime is already included.
• Revenue rate: for example, USD per TH/s-day.
• Charges: fixed amounts, recurring amounts and percentages.
• Acquisition: a consumed service fee or a retained token purchase.
• Exit: optional sale proceeds, selling costs and assumed timing.

Use zero only when a charge has been verified as zero or explicitly excluded from the scenario. Use unknown when evidence is missing. A calculator that silently replaces missing costs with zero can produce a precise-looking but incomplete answer.

Reproduce a complete gross-to-net example

All inputs below are illustrative assumptions. Take an advertised 80 TH/s, a 25-day period and a 95% accepted-delivery factor. Assume gross hashprice of $0.05 per TH/s-day, a 2% pool charge, $60 of consumed service fees, $25 of operating charges and $1 of other charges.

If 76 TH/s is already the measured accepted average over all 25 days, use 76 × 25 and omit the additional 95% factor. Those two approaches produce the same work amount. Applying both adjustments would count the delivery reduction twice.

Choose a revenue method and avoid duplicate adjustments

A hashprice method takes a published revenue rate as its starting point. A network method builds an estimate from difficulty, the block subsidy, transaction-fee assumptions and, for a dollar result, a BTC conversion price. The mempool.space API documentation provides public network and pricing endpoints that can support dated inputs.

One commonly used difficulty-based approximation is expected BTC per day = hashes per second × 86,400 ÷ (difficulty × 2^32) × assumed BTC reward per block. TH/s must first be multiplied by 10^12. This is an expected-work model, not a schedule of blocks that a particular miner will find. Braiins worked difficulty-based calculation illustrates the method; its historical prices are not inputs here.

If a hashprice already incorporates current difficulty and block rewards, do not apply a second difficulty or reward multiplier. Likewise, do not deduct a pool charge twice when using a rate already net of that charge. Actual pool accounting can differ from a network estimate, so reconcile the estimate with pool records before calling it earned revenue.

Use the right denominator for S23 deployment

The working S23 deployment calculator obtains active stake from the program and calculates proportional allocation against published pool capacity. Its capacity participation uses a 1 TH/s baseline: active S23 divided by the number of 1 TH/s capacity units. It does not use total minted supply.

Using an illustrative 1,000 TH/s pool and 156 active tokens, participation is 156 ÷ 1,000 = 15.6%. Calculated allocation is 1,000 ÷ 156 = approximately 6.4103 TH/s per active token. At the $27 reference acquisition price, effective acquisition cost is $27 × 15.6% = $4.212 per TH/s. That calculation does not change the purchase or resale price of a token.

A new deployment must add its tokens to the denominator. Adding 100 to 156 gives 256 active tokens. The new position's share is 100 ÷ 256 × 1,000 = 390.625 TH/s. Its $2,700 reference acquisition outlay divided by 390.625 equals $6.912 per TH/s. Use the existing-position mode only when the position is already included in active stake.

Compare 30-day mining income with token cost

The S23 calculator shows 30-day gross mining income and that income as a percentage of the token purchase cost. It multiplies the current daily estimate by 30, then divides by the entered acquisition cost. The stake ratio and network rate are held constant for this scenario.

For illustration, 10 already-staked tokens within a total of 156 share 1,000 TH/s, giving about 64.1026 TH/s. At an assumed $0.04 per TH/s-day, 30-day gross income is about $76.92. Against a $270 purchase cost, that is 28.49%. The assumed revenue rate is an example, not a live quote. Costs and future token sale proceeds are separate.

The position maximum follows published pool capacity divided by the baseline TH/s per token: currently 1,000 S23. Existing positions also cannot exceed the observed active total. Entering a new stake adds it to the denominator before calculating income.

Check what the result can actually tell you

The S23 page separates published capacity, an observed stake count and a calculated pool share. Its current gross mining run rate uses network inputs; it does not verify that every calculated TH/s was accepted at a customer's pool. Use the staking application and pool records for actual allocation status, delivered work and payouts.

Before using any calculator output, check the data timestamp, change the revenue and delivery assumptions, and inspect what costs are absent. Treat a missing or stale input as a reason to withhold the result, rather than as evidence of zero activity. Keep any future token sale value explicit and separate from mining proceeds.

The hashrate unit guide helps catch conversion errors. Use the profitability scenarios to test sensitivity and the cloud mining overview to select a matching model.