Darkbloom earnings calculator vs. what Macs actually earn
Updated
Darkbloom’s calculator answers “what if my Mac were busy this much of the time?”, not “what will my Mac earn?”. Most of the gap between the two comes from how busy Macs really are. Details below come from the calculator’s open-source code and Darkbloom’s public stats.
How the calculator works
- It estimates your Mac’s generation speed from its memory bandwidth: 65% of bandwidth, divided by the model’s active weights per token.
- It multiplies that by the duty cycle, the share of the month it assumes your Mac spends producing output, and by the model’s output price.
- It counts output tokens only and leaves out base rewards; the code says so.
- The console calculator’s default duty cycle is 5%. The example on darkbloom.ai assumes 60% and shows $204.89 a month for an M4 Max 128 GB MacBook Pro running Qwen3.6 35B.
Why real earnings differ
- Utilization. On September 29, 2026, 5–7% of the network’s capacity was in use, with nothing queued. An average duty cycle near 5% is realistic; 60% is not.
- Routing. Requests go to the Mac expected to answer fastest, so the work is uneven. Large, fast Macs get much more than the average and small Macs often get none.
- Demand per model. The calculator ranks models by price, but a well-paid model can have little demand. On September 29, gpt-oss-20b had about 225 requests in flight across 323 warm Macs, while Nemotron 3.5 Lightning had 2 across 70.
- Input tokens. Real requests are mostly input: in the last 24 hours, 10.6 billion prompt tokens against 1.4 billion output tokens. Input pays much less per token but isn’t in the estimate, and processing long prompts takes time the estimate doesn’t count.
- Base rewards. They aren’t in the estimate, and they come from a fixed $9,000-a-month pool, so the tier amounts are targets, not a guarantee.
- Uptime. Sleep, restarts, drains, pending verification and routing stalls all cut hours the calculator assumes you are serving.
What providers report
- One provider in the Darkbloom Slack reported $210 a month against a calculator projection of $341, about 61%, and that was a good result.
- A public Reddit report from a 96 GB Mac found 99.8% of a 100-entry earnings sample was base reward.
- A Reddit analysis in August 2026 found the calculator’s default had been cut from 80% to 5%. A pull request to base the calculator on real market demand (#697) was still open on September 29.
Measure your own real earnings per hour
- Keep the same model loaded for at least a few days, including nights and a weekend if you can.
- Take confirmed credits from your Darkbloom account’s earnings for that period. Separate base_reward rows from token earnings, and don’t use the job count: it includes base-reward rows.
- Divide by the hours in the period, including hours the Mac was offline. That is your real rate.
- Compare it with the base reward alone. For a 64 GB Mac that is $18 a month, about $0.025 an hour. Anything above that is what paid requests add.
- Repeat for another model before switching for good. Demand moves through the day and the week.
- Save your history as you go. Darkbloom’s earnings API returns only recent entries, so older detail drops off.
Using the calculator sensibly
Leave the duty cycle at 5% or below for most Macs, add the base reward for your memory tier, and treat the result as a ceiling rather than a forecast. Then replace it with your own measured numbers.
Sources
- Calculator code: github.com/Layr-Labs/d-inference/blob/master/console-ui/src/app/earn/calc.ts
- Calculator fix pull request: github.com/Layr-Labs/d-inference/pull/697
- Darkbloom pricing model (base rewards): github.com/Layr-Labs/d-inference/blob/master/docs/reference/pricing-model.md
- Darkbloom routing architecture: github.com/Layr-Labs/d-inference/blob/master/docs/architecture/routing.md
- Job count includes base rewards: github.com/Layr-Labs/d-inference/issues/1244
- Network and model figures: Darkbloom’s public /v1/stats and /v1/models/capacity endpoints, September 29, 2026.
- darkbloom.ai/about (60% example) and reddit.com/r/MacStudio/comments/1vykzbh (August 2026 calculator analysis).
How BloomGauge helps
BloomGauge does this measurement for you: it keeps a local history of confirmed credits per model and hour, shows base rewards separately from token earnings, and its Pulse meter compares the live pay rate with your Mac’s usual rate for the model it serves.
Questions
Is the Darkbloom earnings calculator accurate?
It is accurate about speed and prices but assumes how busy your Mac will be. Its website example assumes 60% of the time producing output, while about 5–7% of network capacity was in use in late September 2026, and most of it went to the fastest Macs. Treat it as a ceiling.
What duty cycle does the Darkbloom calculator use?
The console calculator defaults to 5%, and you can change it. The example on darkbloom.ai uses 60%. Duty cycle is the share of the month the calculator assumes your Mac spends producing output tokens.
How do I work out my real Darkbloom earnings per hour?
Take confirmed credits for a period of a few days, split base rewards from token earnings, and divide by all the hours in the period, including offline hours. Compare models the same way before settling on one.
Related
- Is Darkbloom worth it on a Mac?
- How Darkbloom pays Mac providers: token earnings and base rewards
- How much can a Mac earn on Darkbloom?
- How to maximize Darkbloom earnings on a Mac
Updated 2026-09-29. Still stuck? Ask in #bloomgauge on the Darkbloom Slack or contact us. BloomGauge is independent and not affiliated with Darkbloom.