Scope, disclosure, and commercial conflict
Bitcoin mining companies combine a proof-of-work operation with corporate finance, energy contracts, equipment procurement, treasury policy, and accounting choices. A single ratio cannot collapse those layers into a reliable decision. The useful task is narrower: define each measure, align its period and scope, trace it to primary disclosures, and state what it does not show.
This guide uses no issuer ranking or model portfolio. Examples are methodological and contain no current security price, market capitalization, network telemetry, or return forecast.
Start with filings, not a dashboard
Begin with the latest audited annual financial statements and notes, then read the annual management discussion, risk factors, subsequent interim filing, material-event filings, and any production release covering the same period. A release can add operational detail, but it should not replace audited statements or the notes.
For United States filings, use SEC EDGAR and the SEC’s guide to reading a Form 10-K. For Canadian filings, use SEDAR+. Save the filing URL, accession or filing date, reporting period, presentation currency, and accounting framework with every extracted value.
Required provenance record
- Document type, filing date, fiscal period, page and note.
- Issuer-reported label and exact definition.
- Unit scale: H/s, TH/s, PH/s, EH/s, watts, MW, BTC, shares, or currency.
- Point-in-time, period average, year-to-date, or trailing-period basis.
- Self-mining, hosting, power sales, or consolidated business scope.
- Any analyst adjustment, conversion, estimate, or exclusion.
Normalize period, currency, units, and business scope
Do not divide a period-average production figure by month-end capacity without labeling the mismatch. Do not compare a fiscal quarter with a calendar month. Use exact UTC boundaries for network-derived calculations and the issuer’s stated reporting boundary for financial statements.
Every monetary figure needs an explicit currency. If conversion is necessary, state the foreign-exchange source and whether the rate is transaction-date, period average, or period end. Preserve the reported currency alongside the converted value. Do not combine a USD market value, CAD electricity tariff, and unstated hardware price in one ratio.
One exahash per second equals one million terahashes per second; one petahash per second equals one thousand terahashes per second. Record the original scale before conversion to avoid million-fold errors.
Hashrate: nameplate, energized, operating, and implied
Keep capacity labels separate
Installed or nameplate hashrate is rated equipment capacity. Energized hashrate should refer to capacity connected to power. Average operating hashrate should reflect the period rather than a month-end target. Implied or realized hashrate is often an analyst estimate derived from production and network conditions. None is automatically physical uptime.
Definitions can exclude commissioning, repairs, curtailed machines, hosted customers, joint ventures, or sites awaiting interconnection. Quote the issuer’s definition before calculating a trend.
Derive implied hashrate only on a matched basis
A defensible starting form is:
implied network share = self-mining BTC earned ÷ total BTC paid to miners over the same UTC interval
implied hashrate = implied network share × period-average network hashrate estimate
Actual network miner compensation includes subsidy and transaction fees, and actual block count varies. A pool payout can also differ from direct block ownership because of its payout method, fees, and luck smoothing. Disclose those limitations instead of treating an expected 144 blocks per day as observed production.
Bitcoin Core estimates network hashrate from accumulated proof of work and elapsed block time; the protocol does not directly measure active machines. See the revision-pinned Bitcoin Core estimator and subsidy calculation. Use network vitals and the difficulty-history dataset only with a visible snapshot time and methodology.
Fleet efficiency and facility overhead
Weighted nameplate efficiency
Calculate fleet nameplate efficiency as total rated miner watts divided by total rated TH/s. Do not take an unweighted average of model J/TH values. Match exact models, modes, and manufacturer revisions and identify equipment not yet operating. The ASIC efficiency frontier can provide hardware context, but an issuer filing remains the source for its fleet composition.
Measured site efficiency
Where metered data are disclosed, calculate total facility watts divided by measured operating TH/s. State whether the numerator includes PSU losses, fans, pumps, cooling, transformers, networking, and other facility load. If only miner power is reported, do not label the result site efficiency or assume a power-usage-effectiveness factor.
Overclocking, underclocking, temperature, maintenance, and partially energized capacity can separate measured performance from nameplate ratings. Preserve both rather than choosing whichever creates the preferred narrative.
Production, pool terms, and realized hashprice
Start with self-mined BTC produced, not BTC purchased, sold, or merely held. Identify whether the production figure is gross or net of pool fees and whether a payout scheme smooths fee or luck variance.
A fiat realized-hashprice calculation can be expressed as:
self-mining revenue for the period ÷ average realized PH/s ÷ calendar days
Label currency and revenue-recognition basis. State whether mining revenue includes transaction fees and whether curtailment credits, hosting revenue, fair-value changes, or asset sales are excluded. BTC/PH/day and fiat/PH/day answer different questions and should be shown separately.
Curtailment, uptime, hosting, and energy contracts
A production shortfall can arise from downtime, commissioning, pool variance, maintenance, weather, network connectivity, or curtailment. Curtailment can be mandatory, voluntary, compensated, or economically selected during high power prices. A realized-to-nameplate ratio cannot identify the cause.
For each material site or agreement, extract:
- Self-owned, leased, hosted, or joint-venture status.
- Contracted, energized, and self-mining MW.
- Fixed, indexed, or pass-through energy pricing and demand charges.
- Take-or-pay terms, deposits, letters of credit, and termination rights.
- Curtailment authority, MWh curtailed, credits, and stated BTC-foregone method.
- Counterparty, expiry, renewal, jurisdiction, collateral, and force majeure.
Do not mix hosted-customer hashrate with self-mining production or treat a curtailment credit as mining revenue unless the issuer’s accounting policy does so and the classification is disclosed.
Cost per bitcoin: build a reconciliation
“Cost per bitcoin,” “cash cost,” and “all-in cost” do not have one universal composition. Build separate bridges rather than one persuasive number:
- Electricity and hosting cash cost per BTC.
- Cash cost of revenue per BTC, after defining included labour, repairs, pool charges, and site expenses.
- Accounting cost of revenue per BTC, including disclosed depreciation where applicable.
- Corporate expenditure bridge, separately showing SG&A, stock compensation, interest, capital spending, deposits, and working capital.
Capital expenditures are not automatically current-period expenses. Stock compensation is noncash in a cash-flow presentation but may dilute ownership. Curtailment credits and power sales need consistent classification. Reconcile the numerator to financial-statement lines and use self-mined BTC produced over the same period as denominator.
For operating scenarios, the electricity-cost guide, cost-to-mine methodology, and mining profitability calculator model hardware operations; they are not security-valuation tools or recommendations.
Debt, liquidity, covenants, and equipment commitments
Start with gross borrowings by instrument, current portion, maturity schedule, effective interest rate, collateral, covenants, and cross-default terms. Add leases and other contractual obligations according to the stated definition. Show unrestricted cash separately from restricted cash.
“Net debt” is definition-dependent. State whether bitcoin, restricted funds, convertibles, leases, or other items are included and do not silently treat volatile digital assets as cash. Review equipment deposits, purchase commitments, construction obligations, letters of credit, and subsequent financing after the reporting date.
Debt per unit of hash can be a contextual ratio only if the debt date and operational-hash date align. It does not measure covenant headroom, liquidity, asset quality, or refinancing risk by itself.
Dilution and stock-based compensation
Track split-adjusted period-end common shares and weighted-average basic and diluted shares separately. Then reconcile at-the-market issuance, other offerings, acquisition consideration, stock compensation, restricted units, options, warrants, and convertibles. Review subsequent events for issuance after period end.
Weighted-average diluted shares used for earnings per share are not the same as period-end ownership dilution. A “fully diluted” count depends on exercise, conversion, vesting, and market assumptions and must be defined. Record proceeds and use of funds alongside share growth rather than labelling every issuance identically.
Accounting framework, digital assets, and non-GAAP measures
Identify whether the issuer reports under US GAAP or IFRS before comparing revenue, digital assets, depreciation, impairment, leases, or non-GAAP adjustments. Read the accounting policies and adoption dates. The IFRS Interpretations Committee’s June 2019 cryptocurrency-holdings decision discusses IAS 2 and IAS 38 classification but is not a complete mining-revenue policy. US GAAP readers should verify adoption of the current crypto-asset standard at the FASB crypto-assets project.
Review mining and pool revenue recognition, gross-versus-net presentation, realized and unrealized digital-asset changes, equipment useful lives, depreciation, impairment, segments, related parties, stock compensation, leases, and debt classification.
The SEC’s KPI guidance calls for a clear definition, calculation, usefulness, management’s use, material assumptions, and disclosure of calculation changes. For US filers, consult the SEC Non-GAAP C&DIs. For Canadian reporting, consult NI 52-112 and its companion policy. A reconciliation and unchanged label do not automatically make a measure economically comparable.
Optional valuation ratios and their limitations
Market capitalization per hash compares equity value with one operational measure; enterprise value per hash attempts to incorporate debt and cash. Neither is analogous to the purchase price of a mining machine. Corporate value can include bitcoin, cash, debt, tax attributes, contracts, non-mining segments, deposits, construction, liabilities, and expected future capacity.
If such a ratio is shown, disclose the security-price timestamp, shares used, enterprise-value bridge, currency, business scope, and whether the denominator is nameplate, energized, operating, or implied hashrate. Present it as context only—never a fair-value target, ranking, or signal.
Metric reconciliation table
| Metric | Numerator | Denominator | Primary source | Timing and limitation |
|---|---|---|---|---|
| Self-mined BTC | Issuer-defined self-mining production | None | Filing and production reconciliation | Exclude purchases and define pool-fee basis |
| Average operating hashrate | Operating hash over period | Elapsed time | Issuer KPI definition | Do not substitute month-end nameplate |
| Implied hashrate | Issuer share of network miner BTC | Total matched-period network miner BTC | Issuer data plus chain-derived source | Analyst estimate; pool and fee assumptions |
| Realized/nameplate ratio | Period-average implied or operating hash | Time-weighted nameplate hash | Derived with issuer fleet changes | Not equivalent to physical uptime |
| Fleet J/TH | Total rated miner watts | Total rated TH/s | Fleet table and exact manufacturer modes | Hashrate-weighted; facility load excluded |
| Facility W/TH | Total metered site watts | Measured operating TH/s | Issuer site disclosure | List included overhead |
| BTC/PH/day | Self-mined BTC | Average PH/s × days | Issuer production and KPI basis | Pool method and period must match |
| Fiat hashprice | Self-mining revenue in stated currency | Average PH/s × days | Financial statements plus KPI | Exclude unrelated revenue and fair-value effects |
| Cash power cost/BTC | Defined power and hosting cash cost | Self-mined BTC produced | Cost note and reconciliation | State credit and allocation treatment |
| Accounting cost/BTC | Defined cost of revenue | Self-mined BTC produced | Statements and notes | Show depreciation and segment scope |
| Gross and net debt | Defined obligations less stated offsets | None or same-date operating hash | Debt, lease, and liquidity notes | Net debt is definition-dependent |
| Share dilution | Split-adjusted share change | Prior comparable share count | Equity statement and notes | Show period-end and weighted averages |
| Curtailment | MWh, credits, and estimated BTC foregone | Exact period | Site disclosure and financial classification | Keep physical and financial effects separate |
| Power capacity | Contracted, energized, or self-owned MW | None | Contracts and site disclosures | Never merge unlike capacity labels |
A filing-based research worksheet
A neutral worksheet should begin blank. It should require filing URL, filing date, period start and end, currency, accounting framework, unit scale, and self-mining or hosting scope before calculating anything.
- Reject mixed periods and currencies unless the user records an FX method.
- Show formulas, intermediate values, and the original reported value.
- Never replace an undisclosed value with zero.
- Label issuer-reported, analyst-derived, estimated, and not-disclosed fields.
- Export every input with its document, page, note, and retrieval date.
- Produce no score, ranking, target value, expected return, or transaction signal.
Glossary
- EH/s, PH/s, TH/s
- Exahashes, petahashes, and terahashes per second; each scale differs by factors of one thousand.
- J/TH
- Joules per terahash; lower equipment-level values indicate less rated energy per unit of hash.
- MW
- Megawatts of power capacity or load; contracted, energized, and consumed MW are different.
- PUE
- Total facility energy divided by IT-equipment energy over a stated boundary and period.
- ATM
- At-the-market equity issuance program.
- SBC
- Stock-based compensation.
- MD&A
- Management’s discussion and analysis accompanying financial disclosure.
Frequently asked questions
Is owning mining-company stock the same as owning bitcoin or hashrate?
No. A share represents equity rights defined by corporate and securities documents. It is not direct title to a particular bitcoin balance or mining machine. Direct bitcoin ownership and operating mining equipment are also distinct exposures with different custody, liquidity, operating, tax, and legal risks.
What is the difference between installed, energized, and operating hashrate?
Installed or nameplate hashrate describes rated equipment capacity. Energized hashrate narrows that figure to powered equipment. Average operating hashrate should reflect actual operation over the stated period. These measures cannot be substituted for one another without the issuer’s definition, timing basis, and scope.
How should realized or implied hashrate be calculated?
Treat it as an analyst-derived estimate unless the filing defines it otherwise. Use issuer self-mining BTC earned and total network miner BTC rewards over the same exact UTC interval, multiply that share by a period-average network hashrate estimate, and disclose pool fees, payout method, fee treatment, source, and averaging method.
Why are cost-per-bitcoin figures difficult to compare?
Issuers may include different combinations of power, hosting, payroll, depreciation, maintenance, stock compensation, SG&A, interest, and curtailment credits. The denominator may also differ. Compare only after reconciling the numerator to filing lines and confirming that the denominator is self-mined BTC produced for the same period.
How should fleet efficiency and facility power be compared?
Hashrate-weight model ratings to calculate nameplate J/TH. Separately calculate metered facility watts per operating TH/s when disclosed. State whether PSU losses, fans, pumps, cooling, transformers, overclocking, partial deployment, and other facility overhead are included.
How do dilution, debt, and equipment commitments affect the analysis?
Track split-adjusted period-end shares, weighted-average diluted shares, issuance, stock compensation, warrants, convertibles, gross debt, leases, maturities, covenants, collateral, deposits, and purchase commitments. Net debt and fully diluted shares are definition-dependent and require a bridge.
Are adjusted EBITDA, hashprice, and all-in cost standardized measures?
Not necessarily. Definitions and classifications can vary by issuer and period. Read the reconciliation, reason management uses the measure, calculation method, assumptions, exclusions, comparative periods, and any change in methodology. Never treat the label alone as comparable.
Does this framework recommend a security or mining equipment?
No. It is an educational research method, not investment, legal, tax, or accounting advice. D-Central sells mining hardware, repair, hosting, and related services and may benefit commercially from interest in direct mining. Verify filings and consult appropriately qualified advisers for decisions specific to you.
Sources and revision record
- SEC Release 33-10751, KPI and metric disclosure guidance.
- SEC Non-GAAP Financial Measures C&DIs.
- National Instrument 52-112, non-GAAP and other financial measures disclosure.
- IFRIC June 2019 cryptocurrency-holdings agenda decision.
- FASB accounting for and disclosure of crypto assets project.
- Bitcoin Core network-hash estimator and subsidy calculation, commit
ca7162cde58e69214a3309c17fac6d666b5f055a.
Editorial verification: August 29, 2026. Accounting standards, securities rules, issuer facts, and network conditions can change. Use the rule and filing version effective for the period being analyzed.



