Hedera completed its testnet upgrade to consensus-node software v0.79.0 on November 6, 2026, two days after the maintenance window it had canceled. The official status report recorded completion at 18:07 UTC. Developers waiting for a replacement date can now test against the upgraded network.
The distinction matters because the cancellation notice remains in the maintenance history. It describes an abandoned appointment, while the later entry records a completed deployment. At the November 11 check, Hedera's dashboard listed testnet on v0.79.0 and mainnet on v0.78.2. It did not list a scheduled v0.79 mainnet upgrade.
From cancellation to a completed testnet upgrade
Hedera announced the original maintenance window on October 28, setting November 4 at 18:00 UTC for the testnet upgrade. On November 2 at 20:02 UTC, it canceled that appointment without explaining why.
The replacement notice arrived on November 4 at 18:45 UTC and scheduled the work for November 6. Maintenance began at 18:00 UTC that day. Three minutes later, Hedera said the upgraded network was available while verification continued; four minutes after that, it marked the work complete. The advance notice had allowed approximately 40 minutes for the operation and warned of service disruption.
Neither maintenance record supplies a reason for the original cancellation. The later completion settles whether the testnet rollout happened, but does not establish what caused the schedule to change. It would be unsupported to attach a particular software defect or security problem to that decision.
What testnet completion means for mainnet
Hedera separates its production network from two environments used to develop and test changes. In its published release-cycle explanation, previewnet provides early access to development builds. Testnet offers a more stable setting where applications can be checked against software intended for a subsequent mainnet release.
That sequence gives developers time to discover compatibility problems before a production deployment. Testnet uses free test HBAR rather than assets with real value. Hedera describes the usual testnet lead time as at least two weeks, but that is a description of its normal process, not a confirmed mainnet date for v0.79.
There is another distinction between a version and a feature. Hedera's release-cadence guidance says deployment settings can keep particular capabilities disabled on one network while testing them on another. A version number alone therefore does not establish that every proposed capability is available to production applications.
The feature list needs release-specific confirmation
The maintenance report links to Hedera's consensus-node release notes. However, the page available at the November 11 check still led with v0.78, and the public GitHub release listing reviewed did not supply a v0.79.0 feature summary. The deployed testnet version is confirmed; a complete account of its new features could not be established from those release-specific materials.
An earlier Hedera blog post associated the block-stream migration with v0.79 in November. The official Hiero mirror-node migration guide now gives a different timetable and tells operators to treat its latest version as authoritative. It currently places the switch to a canonical block stream at consensus-node v0.80: November 25 on testnet and December 9 on mainnet. Those are planned dates that the guide says may change, rather than evidence that the November 6 upgrade completed that switch.
The guide tells mirror-node operators to run at least v0.164.0 before their network's cutover. It warns that older versions will stop ingesting new data at that point. This is a distinct operator deadline and should not be collapsed into the v0.79 cancellation or completion story.
What developers should check now
The useful next step is application testing. Hedera's published testing approach includes account creation, transfers, token operations and smart-contract calls, as well as checking how components work together. Developers can use those categories to organize their own checks against the upgraded testnet.
- Run representative application flows and compare outcomes with the behavior the application expects.
- Check error handling and transaction-fee handling as part of compatibility testing, without assuming v0.79 changed a particular fee.
- Confirm the versions of dependent services separately. Hedera explains that mirror nodes and JSON-RPC relays have their own release cycles.
- Use an explicit mainnet maintenance announcement for production scheduling, and review any newly published release notes before relying on a feature.
For ordinary application users, the completed maintenance concerns the test environment. The production version and its own maintenance notices remain the relevant operational reference. For builders, the waiting period has ended: the testnet is available, while the mainnet date, release-specific feature detail and reason for the initial cancellation remain separate questions.