Hedera moves mainnet to v0.77.5 before patch notes appear

Hedera moved its mainnet to consensus-node version 0.77.5 on October 4, completing a scheduled maintenance window in 20 minutes. The fresh deployment is verifiable on the network’s official status page, but the public release trail did not yet explain what changed between the previously documented 0.77.2 build and the newly deployed patch.

That gap matters to node operators and application teams. A version shown as live in production normally gives integrators a precise artifact and change log to review for compatibility, security and operational risk. As of Coinburn’s publication cutoff, Hedera’s release-notes page and the Hiero consensus-node repository both still presented 0.77.2 as the latest public build in the 0.77 line.

What the status record establishes

Hedera scheduled the work for 02:00 UTC on October 4 and warned that users should expect some disruption during an estimated 40-minute window. The status record marked maintenance in progress at 02:00, said the network was available while verification continued at 02:07, and declared the 0.77.5 upgrade complete at 02:20.

Those entries establish deployment timing and Hedera’s own completion assessment. They do not, on their own, identify the code commit, binaries, checksums or patch-specific fixes included in 0.77.5. The same status page identified overall mainnet uptime as operational at the publication cutoff, while its individual-node view showed a partial outage involving the IBM-hosted node. The page did not attribute that node condition to the upgrade, so no causal connection can be drawn.

The documented 0.77 baseline

The public documentation does describe the broader 0.77 release line. Its listed features include support for Ethereum’s Pectra release, a fixed 16-slot Merkle tree for block-root hashing, validation of contract initialization-code limits, and changes to simple-fee handling. It also records multiple fixes affecting scheduled transactions, batch calls, fee conversion, staking metadata and vote replay.

Those are release-line changes, not evidence that every item was newly introduced by the October 4 patch. Hedera’s own status history says mainnet had already moved to 0.77.2 on September 29. The repository’s 0.77.2 notes identify one bug fix: enforcing file-update authorization at ingest and charging failed attempts. Consequently, the defensible conclusion is that October 4 advanced the production patch level within an already deployed minor release; the public material reviewed here does not establish the delta from 0.77.2 to 0.77.5.

The 0.77 transition also carries an application-facing deprecation. Hedera’s maintenance notice says AccountBalanceQuery is deprecated with consensus-node 0.77 and directs developers to the Mirror Node REST API for account balances. That change belongs to the wider 0.77 rollout and should not be represented as a new 0.77.5 behavior without patch-specific documentation.

What remains unresolved

No independent performance measurement, transaction-failure sample or on-chain code fingerprint was available in the opened records. The 20-minute maintenance duration is calculated from Hedera’s 02:00 start and 02:20 completion timestamps; it is not a measurement of user-visible downtime. The network was described as available after seven minutes, but the status updates do not quantify how many requests failed, which services were interrupted or whether every node changed versions simultaneously.

For users, the immediate fact is narrow: Hedera says mainnet is running 0.77.5 and the network-level service is operational. For operators, the missing link is equally important. Until Hedera or Hiero publishes the corresponding release artifact and patch notes, readers cannot verify which code changes distinguish the live build from 0.77.2.