Market cap $2.18 T −2.74 % over 24 hours24h volume $75.31 BBTC dominance 59.1 %ETH 10.1 %Fear & Greed 12 Extreme fearCoins 21,839

Protocol upgrades

Hedera v0.79 upgrade: mainnet switches to block streams on 18 November 2026 at 18:00 UTC

→ (UTC)

Scheduled Online

Starts in

Isometric blocks linked to network nodes, a server rack, an hourglass and a calendar

About the event

The Hedera v0.79 upgrade of the mainnet is scheduled for Wednesday 18 November 2026 at 18:00 UTC. Hedera’s status page plans a window that runs to 18:40 UTC, says the work should take “approximately 40 minutes to complete” and warns users to expect some disruption to network services during that time. The notice was posted on 11 November 2026.

What the release does is narrow and technical. It finishes the move from record streams to block streams, the format in which the network publishes its history. It changes the data layer. It does not change how transactions reach consensus, and it does not touch the supply of HBAR.

Hedera mainnet upgrade on 18 November: the hour where you live

The freeze is set by the clock, not by a block number. 18:00 UTC is 18:00 in London, 19:00 in Paris, Rome and Lagos, 20:00 in Johannesburg, 21:00 in Nairobi and 13:00 in New York. For European users it falls in the early evening of a working day.

Forty minutes is a plan, and Hedera does not present it as a promise. The testnet gives one point of comparison: its v0.79 maintenance began on 6 November 2026 at 18:00 UTC and the status page marked it as completed successfully at 18:07 UTC, seven minutes later. A testnet run says little about how long the mainnet will take.

That testnet step did not go to plan at first. It was announced for 4 November, then cancelled in a status entry dated 2 November, and a new notice on 4 November moved it to 6 November. Hedera gave no reason for the cancellation.

Record stream and block stream: one signed feed replaces four kinds of file

Until this release, each consensus node wrote several separate files to cloud storage: the record stream (transactions and their results), event streams, signature files and sidecars. Anyone who wanted to check the history had to handle those four kinds of file separately.

A block stream is a single signed feed cut into numbered blocks. Each block holds the transactions and results, the consensus events and the state changes. With v0.79 it also carries one aggregated threshold signature, proof that a majority of the network by consensus weight signed it. Picture a bank statement with one stamped page per period, in place of four loose papers.

A document beside stacked blocks, chain links and a magnifying glass
With v0.79 the block stream replaces the separate record, event and signature files as Hedera's reference data.

Hedera set out the schedule in a blog post of 5 June 2026 addressed to mirror node operators. Stage one came in July 2026 with v0.75, which streamed “Wrapped Record Blocks” through block nodes without affecting anyone who read record files. Stage two is v0.79, in November 2026: the threshold-signature cutover, after which the block stream is the canonical source.

The same post ties the change to several Hedera Improvement Proposals: HIP-1056 for the block stream format, HIP-1081 for block nodes (a new tier of infrastructure that receives the stream from consensus nodes), HIP-1193 for the cutover itself and HIP-1427 for wrapped record blocks. Those numbers and titles come from Hedera’s blog.

Who has to act before the cutover

Mirror nodes keep the network’s history and serve it to explorers and applications. Their operators, commercial or self-hosted, are the people with work to do, along with anyone who reads record files directly. The blog is blunt about the version: “Releases earlier than v0.163.0 stop ingesting new data at the cutover.”

Hedera’s post lists four things for them.

  • Run mirror node software v0.163.0 or later.
  • Give read access on the new storage bucket, hedera-mainnet-recent-block-streams, to the same account that reads the existing streams bucket.
  • Leave the importer setting hiero.mirror.importer.block.sourceType on its default, AUTO, so that the node detects the cutover by itself.
  • After the cutover, query the REST address /api/v1/blocks?order=desc&limit=1 and check that the latest block is about five seconds old.

Application developers have nothing to change, according to the same post. The Hedera API, the SDKs in Java, Go, JavaScript and Rust, the mirror node REST API, the mirror node explorer and the JSON-RPC relay are all listed as unaffected. The Hiero local node keeps using record streams during the cutover period and is covered by a separate advisory.

A server rack with a gear, a cloud storage icon and a laptop showing data
Mirror node operators must update their software and grant access to the new storage bucket before the cutover.

Old data stays where it is. Historical record files remain in the legacy bucket, which simply stops receiving new ones. Removing that bucket would take a separate proposal, the blog says, and no date is attached to it.

What HBAR holders will notice

For someone who holds, sends or stakes HBAR, nothing changes after the upgrade: Coinranking reported on 12 November that sending, receiving and staking work the same way. The practical point is the window itself, and it is not the only maintenance that day: the status page also lists a separate two-hour maintenance on one node, node30, from 14:00 to 16:00 UTC. Because Hedera warns of disruption between 18:00 and 18:40 UTC on 18 November, a transfer that has to arrive at a precise minute is better made before or after.

Exchanges can pause HBAR deposits and withdrawals during a network upgrade, according to CryptoTicker, and each one posts its own notice. Whether any will do so on 18 November is not known, so the place to look is your exchange’s announcements page. Afterwards, a block explorer shows whether new transactions are being recorded again.

HBAR traded at $0.05642 on 17 November 2026 at 08:46 UTC, down 15.91% over seven days in a market where the Fear and Greed index stood at 12. Nothing in the sources links that fall to the upgrade.

What Hedera has not published

On 17 November 2026, Hedera’s release notes for consensus node services stop at v0.78, which reached the mainnet on 16 October 2026. There is no v0.79 section, so the only official description of the release is the June blog post and the status notice. Hedera has not listed any other feature for v0.79.

Several dates are missing too. Hedera has announced no day for retiring the record stream format for good, none for removing the legacy bucket, and no following core upgrade appears on the status page. The Hiero local node advisory ends in November 2026, without a day. For what comes next, the blog points operators to the mirror node release notes and to Hedera’s Discord; for the upgrade itself, the status page is where a delay, an extension or the completion notice will appear.

Related