How GoMining profitability is calculated
The whole model, with the formulas, the constants and their verification date. Including the list of places where it can be wrong.
Almost every mining calculator shows you a result and hides how it got there. That forces you to take the number on faith, with no way to tell whether it is inflated. This page is the opposite: here is the entire chain of calculation, so you can redo it by hand and find out exactly where we disagree.
Everything below is what the calculator literally runs, not a simplified version of it. If you find an error, write to [email protected].
The whole thing, in one line
A GoMining digital miner earns bitcoin every day and pays maintenance every day. What is left is yours:
| Net / day = Gross reward − Maintenance |
| Maintenance = (Electricity + Service fee) × (1 − Discount ÷ 100) |
Everything else on this page is unpacking those two lines.
The engine that runs these sums is open source: the code, its 70 tests and this same explanation are on GitHub, so anyone can check the formula line by line.
1. Income: what the network issues per TH
The reward is not set by GoMining, it is set by the Bitcoin network. It is shared across all the hashrate that is mining, so your slice comes from dividing what the network issues by the total hashrate:
| theoretical sat/TH/day = 144 × (subsidy_sats + average_fees_sats) ÷ network_hashrate_TH |
| network_hashrate_TH = difficulty × 232 ÷ 600 ÷ 1012 |
The 144 is how many blocks Bitcoin produces per day by design, one every ten minutes. The subsidy is not hard-coded: it is derived from the current block height, because it halves every 210,000 blocks.
| subsidy = 50 ÷ 2⌊height ÷ 210,000⌋ |
Deriving the subsidy from the height rather than from a constant is what lets the projections apply the halving on their own when they cross the date, without anyone having to remember.
The hashrate comes from the difficulty, not from the estimate. mempool.space publishes an estimate of the network hashrate, but it is noisy and can run 5–7% ahead or behind. What each TH earns depends on the difficulty in force, so the calculator uses the hashrate that difficulty implies.
The same sum with real data, verified on 11 October 2026:
| Item | Value | Source |
|---|---|---|
| Block height | 970,957 | mempool.space |
| Subsidy | 3.125 BTC | derived from the height |
| Average fees per block | 1,361,490 sats | mempool.space, average of 144 blocks |
| Total per block | 313,861,490 sats | 3.125 × 10⁸ + 1,361,490 |
| Difficulty | 132.72 T | mempool.space |
| Network hashrate | 950.02 EH/s | implied by the difficulty |
| Theoretical sat/TH/day | 47.57 | 144 × 313,861,490 ÷ 950,018,149 |
2. The pool factor: how much of that 47.57 reaches you
GoMining does not have to pay exactly the network's theoretical reward: in between there is the pool fee, mining luck and platform overhead. GoMining does not publish it, so it is measured by comparing the theoretical value with what actually gets paid.
| pool factor = paid sat/TH/day ÷ theoretical sat/TH/day |
| 48.18 ÷ 48.35 = 0.996 → the calculator uses 0.995 |
| sat/TH/day the calculator uses today = 47.57 × 0.995 = 47.34 |
Measured on 10 October 2026 with 30 days of real payouts (10 September to 10 October) from a 96 TH miner, exported from GoMining, against each day's difficulty and block reward on mempool.space. Days with Reward Protection active are excluded.
GoMining pays practically 100% of the theoretical reward. Day by day the factor moves between 0.99 and 1.01, and the 30-day average is 0.996. The calculator uses 0.995, rounding down.
We used to use 0.952, and it was wrong. Until 11 October 2026 the calculator applied a factor of 0.952, taken from two measurements in July. Rechecked against the difficulty, they do not hold up:
| Measurement | Factor we gave | With the difficulty | What went wrong |
|---|---|---|---|
| 24 Jul 2026 · one dashboard reading | 0.952 | 0.947 | a single reading at a single moment, which the payout history does not back up |
| 27 Jul 2026 · 13 days of payouts | 0.948 | 0.99–1.00 | the theoretical value (52.24) came from a hashrate estimate of 867 EH/s, below what the difficulty implied |
| 10 Oct 2026 · 30 days of payouts | — | 0.996 | — |
The effect of the mistake: the calculator showed income lower than the real figure. 4–5% from the factor, and a little more or less depending on the day from using the hashrate estimate instead of the difficulty: on 11 October the two together came to 11%. On a miner with a thin margin that moves the net quite a lot, so the site's numbers went up when it was fixed.
Even so, it is still our own measurement, not an official figure. It can change if the pool fee changes, and a run of luck moves it in the short term. That is why the fleet dashboard has a calibrator: enter the sat/TH you are really being paid and it tells you your real factor. If it comes out far from 1, either something has changed or the number you read is not per TH per day.
3. Costs: the only two there are
GoMining charges maintenance as two separate things, and it is worth not confusing them because they behave differently:
| Electricity ($/day) = $/kWh × 24 ÷ 1000 × W/TH × TH |
| Service fee ($/day) = 0.0089 × TH |
Electricity depends on efficiency; the service fee does not. That is why efficiency matters so much: it is the only one of the two you can change by buying better.
The kWh price is not yours to choose: it is set by the data centre your miner sits in, and GoMining documents a range of $0.05 to $0.07/kWh. Total cost per TH per day, at $0.05/kWh:
| Efficiency | Electricity | Service | Total |
|---|---|---|---|
| 12 W/TH | $0.0144 | $0.0089 | $0.0233 |
| 15 W/TH | $0.0180 | $0.0089 | $0.0269 |
| 28 W/TH | $0.0336 | $0.0089 | $0.0425 |
Against that, gross income per TH per day was $0.0304 with bitcoin at $64,509 (27 July 2026). That one line shows why a 28 W/TH miner loses money and a 12 W/TH one does not: income is identical for all three, only the bill changes.
4. Maintenance discounts
They apply to maintenance, never to income. There are four and they stack:
| Discount | How it works | Maximum |
|---|---|---|
| GOMINING token | 1% for every 18 days of maintenance your balance covers | 20% (360 days) |
| VIP tier | Automatic, based on your account level | 6% (Elite) |
| Service button | +0.3% for each consecutive day you press it | 3% (10 days) |
| Solo mining | Variable, set by the weekly veGOMINING vote | no official figure |
The token one has two details that change the result and that almost nobody models properly.
The first is that it moves in steps, not continuously: whole 18-day brackets. Coverage is worked out like this:
| days of coverage = (GOMINING_balance × GOMINING_price) ÷ gross_daily_fee_of_the_fleet |
| discount % = min( ⌊days ÷ 18⌋ , 20 ) |
That floor function means that near a bracket edge, another hundred dollars of balance can be worth a whole point of discount, and a thousand badly placed can be worth nothing.
The second is that coverage is computed against the gross fee of the whole fleet, not the already-discounted one. That is deliberate: using the discounted figure would make the discount depend on itself, and the sum would go circular.
All four are added, and then the cap is applied:
| total discount = min( token + VIP + button + solo mining , cap ) |
And a warning about that cap, because it is one of the things most often repeated wrongly: the 29% is not an official GoMining limit. It is the arithmetic sum of the three discounts that are documented (20 + 6 + 3). GoMining publishes no combined cap. If your dashboard shows a different number, yours is the right one and you can change it in the settings.
Solo mining, on top of that, does not apply to miners you have entered into Miner Wars.
5. From daily net to the metrics
| Break-even (days) = total_investment ÷ net_day |
| Annual ROI (%) = net_day × 365 ÷ total_investment × 100 |
With a negative daily net there is no break-even, and the calculator says exactly that instead of returning a huge number that looks like an answer.
One GoMining feature is worth understanding here: Reward Protection. When the day's reward does not cover maintenance, the difference is not charged to you. That stops you paying out of pocket, but you earn nothing that day either. The engine keeps the real negative value separately, so you can see how much you are actually losing rather than a reassuring zero.
6. Projections: why they come out lower than other tools'
A two-year projection that draws a straight line is a projection assuming the network stands still. It does not. This model applies two things almost nobody applies:
- Difficulty rises. More machines arrive every month and your slice shrinks. The model grows the network hashrate by a configurable monthly percentage (1.5% by default; historically it runs between 1% and 3%).
- The halving arrives. On crossing block 1,050,000 — around April 2028 — the subsidy drops from 3.125 to 1.5625 BTC. Because the subsidy is derived from the height, the projection applies it on its own the day it lands.
The loop is daily and recomputes the network state for each day: growing hashrate, block height advancing by 144 per day. Even in manual mode — where you type your own sat/TH — the projection degrades that value with difficulty and the halving, because otherwise it would lie just the same.
What it does not do is predict the bitcoin price. You pick that as a scenario, which is why the results come out as "if the price does this, that is what you would get".
Where this model can be wrong
No calculator publishes this section, and it is the one most worth your time.
- The pool factor is a measurement, not an official figure. 0.995 comes from 30 days of payouts from a single miner, and we have already got it wrong once. It is the most fragile number on this page. Calibrate it with your own.
- The 29% cap is not documented. It is the sum of three discounts, not a limit published by GoMining.
- The solo mining discount has no known maximum. It is set by a weekly vote. The limit the form uses is our estimate, not a source.
- Per-block fees are a moving average of the last 144 blocks. In a network congestion spike, real income on those days is higher than what comes out here; in a lull, lower.
- Your electricity price depends on your data centre and you do not choose it. If your miner sits in a $0.07/kWh one and you calculate with $0.05, your real result is worse than the screen's.
- GoMining changes its terms whenever it wants. Every constant here carries a date for exactly that reason. If you are reading this much later, check them against the official documentation before trusting them.
- And none of this predicts the bitcoin price, which is what dominates the final result.
The sources, one by one
All verified on 24 July 2026, except the example figures in section 3, which are from the 27th.
| Item | Source |
|---|---|
| Service fee $0.0089/TH/day | Official mining FAQ |
| Electricity $0.05–0.07/kWh | Official mining FAQ |
| Token: 18 days = 1%, 360 = 20% | Fees and discounts FAQ |
| VIP 0.3% – 6% | Fees and discounts FAQ |
| Service button 0.3%/day, 3% cap | Fees and discounts FAQ |
| Solo mining variable by vote | Voting FAQ |
| BTC and token prices | CoinGecko, live |
| Difficulty, height and per-block fees | mempool.space, live |
| Pool factor 0.995 | our own measurement: 30 days of payouts against mempool.space difficulty |
Every constant lives in a single block at the top of motor.js, each with its source and date beside it. There is not one economic number scattered through the HTML.