Categories
Mining Business

Most bitcoin miners never think about EIA-860M. Run your own generation above the threshold and you may already be required to file – here is where the line is.

Almost everything written about regulatory compliance for bitcoin mining covers the parts that touch the business directly: zoning, licensing, taxes, money transmission. One obligation gets skipped almost entirely, because it does not apply to most miners at all – and when it does apply, it rarely shows up on anyone’s radar until a lawyer or a financing partner asks about it. That obligation is federal energy reporting, and for a specific slice of mining operators, it is already a live requirement.

The short version: if your site draws power from the grid and nothing else, this almost certainly does not apply to you. If your site runs its own generation – gas gensets, flare-gas capture, landfill methane, anything behind the meter – at meaningful scale, it might already apply, and the reporting is monthly, not annual.

What EIA-860M Actually Is

The U.S. Energy Information Administration runs two related surveys of electric generating capacity: the annual EIA-860 census and its monthly companion, EIA-860M, which tracks status changes between annual cycles – new generators coming online, units moving from planned to under construction to operating, retirements and mothballing. Both surveys are built around a long-standing capacity threshold of 1 megawatt. An owner or operator of qualifying generating capacity is expected to report, and EIA-860M exists specifically so that capacity changes do not wait a full year to show up in federal data.

The part worth sitting with: this is a reporting obligation on generation, not on electricity consumption. A mining site that buys every kilowatt-hour from a utility is not a generator in the EIA’s eyes no matter how much power it draws. That single distinction is why this topic barely comes up in mining circles – the majority of hosted and colocated miners are pure consumers, and the obligation genuinely does not reach them.

Where Mining Sites Cross the Line

The sites that do cross into generator-reporting territory are the ones covered elsewhere on this site under a different lens: behind-the-meter operations that co-locate ASICs directly with on-site power generation, and facilities running dedicated gas supply into their own gensets rather than buying from the grid. A single backup generator sized for outage coverage is a different animal from a primary generation fleet sized to run the facility continuously – the former is a resilience asset rarely approaching reporting thresholds on its own, the latter is, functionally, a small power plant that happens to feed mining containers instead of a transmission line.

Flare-gas capture and landfill-gas sites sit squarely in this category almost by design – they exist specifically because there is stranded fuel to burn, and the generating capacity built to use it is usually sized well past the point where it stays invisible to federal reporting. If that describes a site’s power architecture, the question is not whether to check EIA-860M applicability, it is confirming the capacity math and getting it documented.

What Actually Gets Reported

EIA-860M filings identify the generating unit and its owner/operator, nameplate capacity, primary fuel type, and – the part that makes it monthly rather than annual – operating status: planned, under construction, operating, out of service, retired, or canceled. A site standing up a new gas-fired generation fleet moves through several of those statuses in sequence, and each transition is a reporting event rather than a one-time filing. That cadence is exactly why this gets missed: a one-time annual form is easy to put on a calendar, a status that changes as construction progresses is easy to lose track of.

None of this requires disclosing anything about the mining operation itself – hashrate, fleet composition, hosting customers and revenue are outside the survey’s scope entirely. The EIA’s interest stops at the generating asset: what it is, how big it is, and whether it is actually running.

Why the Monthly Cadence Matters More Than It Looks

An annual form is easy to plan around: one deadline, one filing, done for the year. A status that changes as a project moves forward is a different kind of obligation, and it is worth walking through concretely. A site that decides to add on-site generation typically moves through several distinct phases over a build cycle – the capacity is announced and planned, then under construction once equipment is on order and site work begins, then operating once it is commissioned and running, and eventually retired or mothballed if it is ever decommissioned or replaced. Each of those transitions is, in principle, its own reporting event under EIA-860M, not a single filing made once and forgotten.

That is exactly the kind of obligation that survives a single compliance review and then quietly lapses. A site might correctly identify and report its generation capacity the month it comes online, then never update the filing when a second phase of generation is added eighteen months later, or when a unit originally built for primary generation is downgraded to backup-only status. Each of those is a real change in what the EIA record shows versus what is actually running at the site, and the gap tends to go unnoticed for the same reason most of these obligations get missed in the first place: nobody is specifically tasked with checking it on a recurring basis.

Beyond EIA: State and Grid-Operator Reporting

Federal generator reporting is one layer. Large electric loads – which most mining sites are, whether or not they generate their own power – increasingly face a second layer at the state and grid-operator level. State public utility commissions in several jurisdictions now require large-load interconnection filings before a site of meaningful size can even draw service, independent of anything related to generation. Grid operators managing constrained territory have introduced large flexible load registration processes aimed specifically at data centers and mining facilities, driven by exactly the kind of grid-stability concerns that also show up in curtailment and force majeure provisions in hosting contracts. These requirements vary significantly by state and by grid operator, and change faster than federal rules do, which makes a blanket summary unreliable – site selection work covered in power costs by state should include a check of what the specific utility and grid operator currently require, not an assumption based on what a neighboring state does.

State-level reporting also overlaps with the siting and permitting work covered in zoning and regulatory compliance – a jurisdiction that requires environmental or air-quality permitting for on-site generation very often layers a reporting requirement on top of the permit itself, so the two obligations tend to travel together rather than arrive separately.

Why This Falls Through the Cracks

Energy reporting does not belong cleanly to any one role at a typical mining operation. It is not quite an IT function, not quite a legal function, and not quite an operations function – it sits in the gap between the team that sized the generators and the team that handles corporate compliance, and in a lean operation, nobody owns that gap by default. The failure mode is rarely a decision to skip filing; it is simply that nobody was assigned the obligation in the first place.

The consequences scale with how the oversight is discovered. A missed filing caught and corrected proactively is typically a straightforward fix. A gap surfaced during financing due diligence, an acquisition, or a regulator’s own cross-reference against utility interconnection data is a worse conversation to have, because at that point it reads as an unmanaged compliance program rather than an oversight – and large-load energy infrastructure is exactly the kind of asset that draws that scrutiny during a capital raise or sale.

This is also where energy reporting starts to resemble the other paper-trail obligations already covered on this site. A lender or acquirer evaluating a mining operation with on-site generation will, at some point, ask for proof that the facility’s generating capacity is accurately reflected in federal and state records – the same way they will ask about permit status, tax compliance, and whether the facility’s decommissioning and financial assurance obligations are current. A clean, up-to-date filing history answers that question in minutes. A gap that has to be investigated and corrected mid-diligence slows the deal down and raises exactly the kind of question a buyer or lender did not need to be asking.

Building This Into Site Operations

The practical fix does not require a dedicated compliance hire at most sites. It requires three things: confirming, in writing, whether the site’s on-site generating capacity crosses the reporting threshold; assigning a specific person or outside counsel ownership of the filing calendar, the same way tax incentive agreements and financial assurance obligations get an owner rather than floating between departments; and re-checking that determination every time generating capacity is added, retired, or repowered, since a status change is precisely the event EIA-860M exists to capture.

None of this is a substitute for current guidance from the EIA itself or from counsel familiar with a site’s specific jurisdiction – reporting instructions, thresholds and state-level large-load rules are all subject to change, and a mining operator’s actual filing obligation should be confirmed against current EIA instructions and local requirements rather than against a summary like this one. What is worth taking away is simpler: the question “does our site generate enough of its own power to be a reportable generator” is one every operator running meaningful on-site generation should be able to answer with confidence, in writing, today.

If your site runs on-site generation and you are not certain where it sits against federal and state reporting thresholds, get in touch.

Explore Rax Mining

Categories