Hedera completed its mainnet upgrade to consensus-node version 0.79.2 on November 18, moving the network’s canonical output from several legacy data feeds to one block stream designed for independent verification.
The change matters mainly to the infrastructure that reads and preserves Hedera data. It does not change HBAR balances, create a new token or alter the public interfaces most applications use. Instead, it reorganizes how consensus results, transaction outcomes and state changes leave consensus nodes and reach mirror nodes and other data consumers.
Hedera’s status record says maintenance began at 18:00 UTC. The network was available again at 18:07 while verification continued, and the maintenance event was marked complete at 18:40. Those timestamps establish the operator’s reported upgrade sequence; they do not measure how many requests failed or whether every individual node completed the transition simultaneously.
One signed stream replaces several outputs
Before the cutover, consensus nodes produced separate record streams, event streams, signature files and sidecars. Hedera’s June operator advisory says version 0.79 makes the block stream the canonical output and adds network-aggregated threshold signatures.
The approved technical specification describes the transition boundary more precisely. Consensus nodes finish the last legacy record, wrap it into the new block format, stop producing record and event streams, and then link the first native block to the final record’s running hash. That design is intended to preserve cryptographic continuity across the change rather than begin an unrelated history.
Each new block can include transactions and their results, consensus events and the state changes applied during the block. A single aggregated signature is intended to let downstream software verify the output without collecting separate signature files from multiple consensus nodes.
The architecture also adds block nodes as a distribution and storage layer. Consensus nodes send blocks to block nodes; mirror nodes can read from those services, with recent-history cloud buckets available as a fallback. The migration therefore changes data plumbing and verification, not Hedera’s consensus algorithm or the application-facing transaction format.
Operator impact is narrower than user impact
Hedera warned mirror-node operators and direct consumers of record files to deploy a cutover-compatible mirror-node release and authorize access to the new storage buckets before the transition. Its advisory identified version 0.163.0 as the minimum supporting release at the time it was published.
Standard application routes were not supposed to require changes. Hedera listed its application programming interface, official software development kits, mirror-node explorer, mirror-node REST interface and JSON-RPC relay as unaffected. Historical record files also remain available; the cutover ends new legacy output rather than deleting the earlier archive.
That distinction limits the claim. Completion of the maintenance event establishes that Hedera deployed version 0.79.2 and declared the scheduled work finished. It does not independently prove that every third-party data provider upgraded correctly, that all block proofs have been verified by external operators or that the new architecture improved performance.
What the live status does and does not show
At Coinburn’s research cutoff, Hedera’s status page listed mainnet network uptime as operational on version 0.79.2. The same page showed a partial outage for the individual-node component, with several named nodes marked partial outage.
Hedera’s upgrade incident did not attribute those node conditions to version 0.79.2. Coinburn therefore cannot connect them to the cutover or describe the deployment as trouble-free. The status page also supplies no before-and-after measurements for latency, storage cost, data availability or verification speed.
The defensible result is narrower: Hedera completed a planned mainnet migration to a unified, verifiable block-output format on November 18. The next useful evidence will come from mirror-node ingestion records, third-party block-proof checks, any post-upgrade incident report and performance measurements collected under comparable conditions.
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.

