Home » Uncategorized » Hedera Schedules v0.79 Mainnet Upgrade, Retiring the Record Stream

Hedera Schedules v0.79 Mainnet Upgrade, Retiring the Record Stream

Hedera scheduled its mainnet to swap in a single signed Block Stream on November 18, but hours after the window closed, the company’s own status page still hadn’t confirmed it…

Teal and dark green wavy data streams converging into one line, symbolizing Hedera's Block Stream upgrade

How do you prove a blockchain told the truth about its own history? Hedera has spent months building toward an answer: one cryptographically signed data stream in place of four separate ones. Hedera scheduled the mainnet half of that switch for Wednesday, November 18, 2026, setting a maintenance window from 18:00 to roughly 18:40 UTC, after finishing a successful test run on its testnet on November 6.

Hedera’s own blog explains exactly what Hedera’s Block Stream replaces and who has to act on it. Hedera’s status page confirms the mainnet maintenance window itself. As of this writing, though, that same status page still listed the mainnet cutover under “Scheduled Maintenance” rather than “Completed,” and the live network status still showed version 0.78.2 running.

What Detail
Date Wednesday, November 18, 2026
Scheduled window 18:00 to roughly 18:40 UTC (about 40 minutes)
What changes Record Stream replaced by a single, TSS-signed Block Stream
Who must act Mirror node operators and direct consumers of record files
Not affected HAPI, the Hedera SDKs, the mirror node REST API, the JSON-RPC Relay, and sending, receiving or staking HBAR

Source: Hedera Status page and Hedera blog, November 2026.

For comparison, the testnet version of this same upgrade moved fast. Hedera’s status page logged it as “in progress” at 18:00 UTC on November 6 and “completed” by 18:07, seven minutes later. Whether the mainnet cutover ran on a similar clock isn’t something Hedera’s status page had confirmed as of publication.

What the Block Stream Actually Replaces

Under the old system, each Hedera consensus node produced four separate outputs, record streams, event streams, signature files and sidecars, then uploaded them to cloud storage on its own. Anyone who wanted to independently check Hedera’s history had to pull those pieces back together and verify signatures from individual nodes rather than from the network as a whole.

The Block Stream, specified in HIP-1056, folds all of that into one signed format. Each block now carries every transaction and its result, every consensus event, the state changes applied in that block, and a single aggregated signature built from a majority of the network’s weight through a Threshold Signature Scheme, or TSS. Consensus nodes push that stream to a new infrastructure layer called Block Nodes, defined in HIP-1081, and mirror nodes read from Block Nodes instead of cloud storage, which stays on only as a fallback.

In practice, one signature check now stands in for reconciling four separate files from individual operators. That’s a narrower, more verifiable record than the old setup, and it’s designed to need no action from anyone except the operators reading those streams directly.

The Timeline Behind the Cutover

Hedera staged this rollout in pieces. The first piece arrived quietly in July 2026 with consensus node v0.75: nodes began wrapping record data for the new Block Nodes without touching anyone still reading the old record files directly. The part that actually changes what a block proves, the TSS signature, didn’t arrive until v0.79.

Getting there took two tries. Hedera originally scheduled the testnet switch to v0.79 for November 4, then canceled it on November 2 without giving a reason on its status page. It rescheduled for November 6, ran the upgrade that morning, and confirmed the testnet was stable within minutes. The mainnet announcement followed five days later, on November 11, setting up today’s window.

What’s Still Unclear

  • Hedera’s status page hadn’t marked the mainnet cutover complete as of publication, even though the scheduled window had closed. Whether it finished on time, ran long, or slipped to a later date isn’t confirmed yet.
  • As of Wednesday evening, Hedera hadn’t published detailed release notes for version 0.79 in its documentation; the status page linked to a placeholder section instead, according to CryptoTicker’s reporting.
  • Hedera never explained why it pulled the original November 4 testnet attempt.
  • Old record files aren’t disappearing immediately, but they’re not permanent either. Hedera’s blog says fully retiring the legacy storage bucket “would require a separate HIP,” with no such proposal attached yet.
  • Hedera names mirror node operators and direct record-file consumers as needing to act, but hasn’t published how many of its third-party mirror node providers, beyond its own, have actually deployed a compatible release.

Who Benefits and How

This is an infrastructure change, not a feature anyone opens an app to use, so the people who feel it first aren’t retail HBAR holders.

Mirror node operators, the companies and self-hosted teams that read Hedera’s raw output and serve it to everyone else, had one job going into today: get onto a compatible release before the cutover. Hedera says operators who kept current through normal upgrades needed no manual configuration at all; the switch to reading Block Streams happens automatically once it takes effect.

Developers, auditors and exchanges that pull Hedera data through a mirror node don’t have to touch their code. HAPI, the SDKs, the mirror node REST API and the JSON-RPC Relay all keep working exactly as before, according to Hedera’s own guidance. What they stand to gain, once the cutover is confirmed, is a data feed that’s simpler to independently check: one TSS signature backed by a majority of the network’s stake, instead of trusting that whichever provider assembled the four old streams did it correctly.

Everyday HBAR holders won’t notice anything different sending, receiving or staking HBAR. If this upgrade pays off for them, it shows up indirectly, in institutions and tokenization projects treating Hedera’s data as easier to audit independently. Hedera hasn’t published numbers on how much cheaper or faster that verification becomes in practice, so for now the benefit is a structural bet rather than something measured.

The real test isn’t today’s scheduled window. It’s the confirmation that follows it: whether Hedera’s status page logs a clean mainnet move to v0.79, and whether every mirror node operator serving exchanges and apps has actually made the jump before the old record stream stops being the network’s canonical record.

Sources

Related Reading