Bitcoin raised its proof-of-work mining difficulty to approximately 148.258 trillion at block 929,376 on December 25, 2025. The increase was only about 0.0426%, but it was the network’s final scheduled retarget of 2025 and the first positive adjustment after three consecutive declines.
The block’s header records a difficulty of approximately 148,258,433,855,481 and a timestamp corresponding to December 25, 2025 at 03:48:06 UTC. That timestamp identifies the event date, although Bitcoin block times are supplied by miners and operate within protocol constraints rather than serving as exact independent wall-clock measurements.
The narrow conclusion is that computational work during the preceding adjustment period arrived almost exactly on the protocol’s intended schedule. The result did not establish a new mining boom, prove that every operator was profitable or reveal which machines supplied the work.
What changed at block 929,376
Bitcoin reassesses its proof-of-work target every 2,016 blocks. The protocol compares the elapsed timestamps for the prior adjustment interval with its target pace of roughly one block every ten minutes. When blocks arrive too quickly, difficulty rises; when they arrive too slowly, it falls. Bitcoin’s implementation also contains a documented off-by-one characteristic: the calculation uses a timestamp span covering 2,015 block intervals.
The previous difficulty was approximately 148,195,306,640,204. Dividing the new figure by the previous one and subtracting one produces an increase of about 0.042597%, conventionally rounded to 0.04%. Because difficulty remains constant throughout an epoch, the change applied from height 929,376 until the next valid retarget.
That tiny increase followed reductions of about 2.37% at height 923,328 on November 12, 1.95% at height 925,344 on November 27 and 0.74% at height 927,360 on December 11. The December 25 result therefore ended a three-adjustment declining sequence, but its magnitude was too small to support a strong claim that the underlying mining trend had reversed.
Why a nearly flat retarget mattered
Difficulty is a protocol variable, not a direct meter of electricity use or a census of active mining machines. It nevertheless summarizes the amount of hash computation competing to produce blocks over an adjustment window. A nearly unchanged result indicated that aggregate work remained broadly aligned with the network’s target despite the earlier sequence of downward adjustments.
For miners, the retarget preserved rather than transformed the competitive setting. With the block subsidy fixed at 3.125 BTC during this period, an operator’s bitcoin-denominated production depended on its share of total effective hash power, uptime, pool performance and transaction fees. Profitability additionally depended on energy prices, equipment efficiency, financing and bitcoin’s exchange value. The protocol record alone cannot measure any individual company’s margins.
Market data also require a defined observation method. CoinMarketCap’s December 25 historical aggregate snapshot listed bitcoin at $87,234.74, down 0.43% over its displayed 24-hour window, with reported 24-hour volume of approximately $19.95 billion. Those figures are an aggregated snapshot across CoinMarketCap’s methodology, not a regulated closing auction or a single-exchange settlement price. They provide market context but do not demonstrate that the retarget caused the price movement.
What the record establishes—and does not
The central fact is reproducible from Bitcoin’s public block record: height 929,376 introduced the new encoded target corresponding to approximately 148.258 trillion difficulty. Independent historical tables report the same height, date, prior value, new value and rounded percentage change.
Interpretation should remain proportionate. A difficulty increase can be consistent with more hash power, improved uptime or ordinary variance in block discovery. A single 0.04% adjustment cannot distinguish among those explanations. It also says nothing by itself about geographic mining distribution, network energy consumption, miner solvency or future bitcoin prices. Those questions require separate company disclosures, pool-level measurements and carefully defined datasets.
The complete source packet and revision history are retained with the newsroom record.
Automated systems may have assisted with source organization and drafting. Coinburn is accountable for the published text and maintains a revision record.
This article provides news and analysis, not investment, legal or tax advice. Digital assets are volatile and may result in total loss.

