There are no paid plans to choose here
SiliconMining.com provides public learning material and static sample data. It does not sell hosted API tiers, mining contracts, or hardware through this website. There are no checkout, subscription, or account functions.
This page is a planning framework for understanding a project's costs. It is not a quotation, a recommendation to invest, or a claim that a particular mining setup will be profitable.
Separate initial and recurring expenses
An initial project scope may include equipment, compatible infrastructure, installation, configuration, and professional review. Recurring scope may include energy, networking, maintenance, replacement parts, and other expenses relevant to the actual site.
List only items that apply, mark unknowns clearly, and attach evidence to each estimate. A model is more useful when it exposes unanswered questions than when it fills every cell with an invented number.
Use three distinct records
Keep an equipment and installation budget, an observed operating ledger, and hypothetical future scenarios as separate records. Do not allow a changed revenue assumption to rewrite a measured energy cost.
A potential resale value belongs in a scenario until it is realized. Likewise, possible revenue from switching GPU workloads should not be treated as certain without a real use case and the work required to support it.
Start with a transparent energy example
The electricity-cost page shows the arithmetic behind constant power, operating hours, and a hypothetical flat energy rate. It also explains why that result is not a complete bill.
For hardware comparisons, use J/TH with a defined boundary. Compare the same workload and include relevant auxiliary loads rather than ranking incompatible numbers.
Write a decision memo
Document the objective, constraints, evidence, alternatives, unknowns, and conditions that would make you reconsider. Include an appropriate professional review for installation and location-specific requirements. A short memo makes the logic easier to revisit when circumstances change.
The ASIC versus GPU guide demonstrates a workload-first comparison. It avoids a universal winner because a suitable choice depends on the actual job and operating environment.