Skip to main content
Visit the Hedera status page for the latest versions supported on each network.

​
Release v0.68

MAINNET UPDATE SCHEDULED: DECEMBER 10, 2025
TESTNET UPDATE: NOVEMBER 13, 2025

​
Build 0.68.0

  • ci: Update SDPT and SDLT workflow to only tag when build ID is present by @andrewb1269hg in #20984
  • fix: Add scheduling.maxExpirySecsToCheckPerUserTxn by @tinker-michaelj in #20987
  • chore: Update incident_types by @rbarker-dev in #21055
  • chore: replace input.ref with github.ref in single day controllers by @andrewb1269hg in #20988
  • chore: Minor Version Roll to 0.67.0-SNAPSHOT by @andrewb1269hg in #21072
  • feat: 17002: A concept of default MerkleDb instance seems redundant by @artemananiev in #19700
  • chore: state validator rehash is too slow by @OlegMazurov in #21013
  • chore(20698): Invert PlatformWiring and PlatformCoordinator relationship by @mxtartaglia-sl in #20758
  • ci: Automatically generate the GH release by @rbarker-dev in #20970
  • chore: Rework block node communication metrics by @timfn-hg in #20885
Full Changelog: v0.66.0…v0.68.0

​
Release v0.67

MAINNET UPDATE: NOVEMBER 12, 2025
TESTNET UPDATE: OCTOBER 29, 2025

​
Release Highlights

Release v0.67 enhances the stability and performance of the Hiero Consensus Node and updates. Continued progress was made on HIP-1081 Block Nodes, adding features to improve connectivity and metrics.
Updates:
  • Improved Block Streaming Metrics: Metrics for communication between consensus and block nodes have been reworked for clarity and utility. Metric names no longer include the self-node ID, as this is now automatically added as a label
  • Block Streaming Service Lifecycle: The startup and shutdown procedures for the BlockBufferService and BlockNodeConnectionManager have been improved to ensure more reliable initialization and termination.
  • Enhanced Testing and CI: A large effort was invested in improving the test infrastructure, including adding test container support for block nodes, increasing test coverage for block node communication, and parallelizing test suite runs to accelerate the development cycle.
  • Besu Upgrade: Upgraded Besu EVM to 25.2.2. The update introduces Besu Native Libraries Verification, which ensures that required native libraries are available on the host operating system. When these libraries are missing, Besu falls back to non-native implementations, which can reduce performance. This verification helps maintain optimal execution efficiency and consistency across nodes.
Summary:Steady strides were also made in Block Node stability and manageability, including optimizations for error handling, and operational monitoring. The new Besu upgrade brings EVM to v.25.2.2 with Besu Native Libraries Verification enhancements.For developers, no breaking changes or immediate actions required. Existing contracts and integrations remain fully compatible.

​
Build 0.67.2

  • feat: Block Node communication cherry-picks by @derektriley in #21742
  • fix(bug): (cherry-pick) Fix typo in GitHub release step (#21563) by @andrewb1269hg in #21760
  • fix: Disable RPC sync by @abies in #21841
  • fix: Re-enable gas throttle; disable ops duration throttle by @lukasz-hashgraph in #21845
Full Changelog: v0.67.1…v0.67.2

​
Build 0.67.1

Full Changelog: v0.67.0…v0.67.1

​
Build 0.67.0

Full Changelog: v0.66.0…v0.67.0

​
Release v0.66

MAINNET UPDATE: OCTOBER 9, 2025
TESTNET UPDATE: SEPTEMBER 25, 2025

​
Release Highlights

With the introduction of batch transactions, Release v0.66 marks a key milestone in enhancing flexibility and certainty when executing complex use cases.

​
Batch Transaction Processing (HIP-551)

Historically, Hiero developers have been limited to submitting and processing transactions individually. To create complex flows developers relied on smart contracts to execute the series of transactions and mirror node queries to monitor the status of submitted transactions, leading to increased latency, added code complexity, and greater risk of partial failures or errors.Release v0.66 introduces HIP-551 - Batch Transactions, allowing multiple transactions to be bundled and submitted as a single unit that guarantees ACID properties (atomicity, consistency, isolation, and durability). The network handles the batch atomically, ensuring consistent execution while providing granular receipts for each inner transaction. This new feature unlocks capabilities like streamlined dApp interactions, atomic multi-step operations, and consolidation of multiple transactions into one HAPI call.Key benefits:
  • Efficiency Gains: Increases efficiency by processing multiple transactions in one submission, ideal for high-volume applications like DeFi or NFTs.
  • Developer Flexibility: Enables new use cases, such as batch token minting or multi-account updates, without requiring smart contracts.
  • User Experience Improvements: Simplifies interactions for end-users, e.g., executing a series of approvals and transfers in a single step.
To support this, no major client code changes are needed for basic usage, but developers should update to SDKs that support this feature.SDK Versions Supporting Batch TransactionsBelow are the versions of SDKs that support batch transactions:
SDKVersion
Javav2.55.0+
JavaScriptv2.64.0+
Gov2.61.0+
Rustv0.39.0+
C++v0.40.0+
NOTE: Batches may fail partially if inner transactions violate rules; always check individual receipts. For full details on batch structure and rules, see HIP-551.

​
Advancements in Block Node Communication

The development of Block Nodes (HIP-1081) continues with this release, with the following development being done:State Export Tools: New commands and improvements for exporting states (Issue: #20622). This is a part of enabling block nodes to improve state snapshotting.Block Node Communication: Enhancements to the communication protocol between consensus nodes and block nodes. Provides better recovery and shutdown procedures to minimize downtime during events like freezes. (Issues: #20858, #20874)\

​
Build 0.66.0

Full Changelog: v0.65.1…v0.66.0

​
Performance Results

​
Release v0.65

MAINNET UPDATE: SEPTEMBER 24, 2025
TESTNET UPDATE: SEPTEMBER 4, 2025

​
Release Highlights

Release v0.65 highlights include Virtual Mega Map, enforcement of max_custom_fees for HIP-991 scheduled transactions, and Block Stream improvements including forward-compatibility and unified transaction records. Together, these changes introduce powerful new state management capabilities, scheduled transaction fee controls, and continued advancements toward production-ready Block Streams.

​
Virtual Mega Map

The Virtual Mega Map enhances Hedera’s internal state data structure by consolidating all entities—including singletons, queues, and maps—into a single virtual map. This ensures the entire state rolls up to one root hash.Key benefit:
  • Enhanced Verifiability: A unified root hash simplifies state and block item proofs, used for block streams.

​
HIP-991 Enhancements: max_custom_fees for Scheduled Transactions

Release v0.65 adds support for max_custom_fees in scheduled transactions with HIP-991 topics.Key benefits:
  • Predictable Fees: Ensures maximum custom fee limits are enforced.
  • Alignment with HTS: Extends scheduled transaction functionality to better match Hedera Token Service features.
  • Developer Guardrails: Protects applications and users from unexpected fee outcomes.

​
Advancements in HIP-1056 & HIP-1127: Block Streams

Building on the Block Stream work from v0.64, this release delivers major steps toward a unified, verifiable stream layer.New developments:HIP-1127: Unified Transaction Record in Block Stream: Addresses historical duplication in how transactions are represented and creates a single, unified standard for the block stream. It achieves this while ensuring complete backward compatibility for existing applications, requiring no code changes for developers submitting transactions.Key benefits:
  • Performance & Scalability: Improves throughput and reduces latency when handling accounts, tokens, and other stateful data.
  • Future-Proofing: Provides a foundation for ongoing state service optimization.
  • Reduces State: Reduces the size and cost of the data stream

​
Build 0.65.1

Full Changelog: v0.65.0…v0.65.1

​
Build 0.65.0

Full Changelog: v0.64.2…v0.65.0

​
Performance Results

​
Release v0.64

MAINNET UPDATE: AUGUST 20, 2025
TESTNET UPDATE: AUGUST 7, 2025

​
Release Highlights

Release v0.64 significantly improves the developer experience for frontend applications by introducing dynamic gRPC-Web endpoint discovery. This simplifies development workflows, enhances scalability, and sets the stage for a more decentralized and robust Hedera network. Additionally, this release includes important important block stream feature development, bug fixes, optimizations, and dependency updates that contribute to the overall stability and performance of the Hiero Consensus Node.

​
HIP-1046: gRPC-Web Proxy Endpoint Support To the Address Book

Historically, connecting frontend applications to Hedera using the JavaScript SDK has been challenging due to browser security restrictions. gRPC-Web was used as a workaround, but the necessary endpoints were hardcoded into the SDK. This approach required manual updates and coordination, which could become problematic as Hedera grows and more independent nodes operate.To address this issue, release v0.64.0 introduces dynamic endpoint discovery for gRPC-Web, as described in HIP-1046. The Hedera address book now includes gRPC-Web endpoint information, which the JavaScript SDK uses dynamically. This eliminates the need for hardcoded endpoints and simplifies connecting frontend applications to the Hedera network, even as endpoints change.Key benefits:
  • Simplified Development: Eliminates the need for manual SDK updates to reflect endpoint changes.
  • Enhanced Scalability: Supports the growing number of nodes on the Hedera network.
  • Improved User Experience: Provides a more seamless and robust connection experience for frontend applications.
Client code impact:
  • Update to the latest Hedera JavaScript SDK to leverage this feature. The SDK will now automatically retrieve gRPC-Web endpoints from the address book.
  • Applications or tools that manually maintained lists of gRPC-Web endpoints should now query the mirror node for the latest list.

​
Advancements in HIP-1056: Block Streams

Version 0.64 introduces substantial progress on HIP-1056, which aims to create Block Streams—a unified, verifiable data stream that combines Hedera’s existing event, record, and sidecar streams into a single efficient output. These enhancements focus on making Block Streams production-ready by prioritizing efficiency, cost-effectiveness, and security.Key developments in this release include:
  • Stream Size Optimization: The block stream has been refined to minimize its size, reducing storage and transmission costs while maintaining high performance and scalability. This release represents a partial update, with more enhancements to follow.
  • Batch Transaction Support: Added functionality to include batch transactions into the block stream.
  • Consensus Node-to-Block Node Communication: Established secure and reliable communication channels between consensus nodes and block nodes including features like acknowledgments and resend mechanisms. This release represents a partial update, with more enhancements to follow.

​
Other updates:

In addition to the aforementioned features, release 0.64 introduces other updates:
  • Added TCK tests to the continuous integration pipeline ( #18727 ) to improve testing coverage and software quality.
  • Disallowed setting duplicate rosters ( #19072 ) to optimize storage and CPU usage.
  • Several dependency updates ( #18714, #18841, #19074 ) to leverage the latest improvements and security patches.

​
Build 0.64.2

Full Changelog: v0.64.1…v0.64.2

​
Build 0.64.1

Full Changelog: v0.64.0…v0.64.1

​
Build 0.64.0

Features
  • Make worker loop sleep duration configurable (#20007)
  • Add transaction support for the container environment (#19941)
  • end the stream if block node is too far behind (#19434)
  • replace hashmap with an array to improve performace for ops duration lookups (#19836)
  • Apply EIP-3529 refund limits (#19769) (#19821)

​
Bug Fixes

  • remove workflow dispatch inputs when calling integration workflow (#20046)
  • 18458 Pces file writer rollback (#20038)
  • false positive tests used ‘numeric contract complex’ from numeric validation test (#19954) (#20037)
  • resolve issues with the integration trigger workflow (#20026)
  • Restore missing deps, META-INF files (#20031)
Full changelog can be found in the repo.

​
Performance Results

​
Release v0.63

MAINNET UPDATE: JULY 23, 2025
TESTNET UPDATE: JULY 10, 2025

​
Release Highlights

Release v0.63 introduces three focused improvements: birth-round based ancient event handling, low overhead SDK usage metrics, and full support for non-zero realm IDs.
Birth-Round MigrationToday ancient event pruning correlates with clock time rather than specifically from consensus rounds causing overhead during node updates. In this release birth-rounds are based on consensus time which causes more consistent pruning and smoother node joins, exits, and upgrades.SDK Usage Metrics & gRPC Call insightsRelease .63 introduces a gRPC interceptor that aggregates methods into gRPC_usage metrics every 15m. This will give node and network operators granular visibility with minimal overhead.Non-Zero Realm SupportShard and realm default values on Hiero have previously assumed 0 values, sometimes with hardcoded logic limiting our ability to test future multi value shard and realm network implementations. All APIs and services now accept arbitrary shard and realm IDs. Moving forward we can consistently test future network upgrades in a way that validates non zero realm and shard network configurations.

​
Summary

Release 0.63 aligns ancient event handling with consensus time, adds actionable higher resolution SDK telemetry, and removes limitations to implementing non zero realm and shard value tests. This improves Hiero network operational robustness, and expands test configurations.

​
Build 0.63.9

Full Changelog: v0.63.7…v0.63.9

​
Build 0.63.7

Full Changelog: v0.63.6…v0.63.7

​
Build 0.63.6

Full Changelog: v0.63.5…v0.63.6

​
Build 0.63.0

​
Features

  • remove shard/realm negative check in asTokenId (#19355)
  • 8841: Need a way to change the number of object key buckets in MerkleDb (#18910)
  • Support nonzero shard/realm in yahcli sys commands (#19297)
  • remove genesis freeze time (#19298)
  • Bump PBJ version and use Block Stream Publish Service (#19290)
  • overwrite default config converters (#18617)
  • Support nonzero shard/realm in fee and schedule commands (#19279)
  • add throttle for ops duration (#19053)
  • UnitTest of BirthRound Ancient Mode (#11560) (#19252)
  • Support accepting/declining rewards in yahcli DAB transactions (#19255)
  • Add ops duration (#18921)
  • limit birth round when freezing (#19193)
  • Enable Birth Rounds as Ancient Threshold (#19208)
  • Implement nonzero shard/realm for yahcli DAB transactions (#19166)
  • Migrate logging validation to assertThat for OtterTests (#19159)
  • 18458 Guarantee events are written on pces before handling that round (#18811)
  • stop consensus on freeze (#18937)
  • Yahcli nonzero shard/realm implementations for crypto transfers and sys file updates (#19063)
  • Implement feature flag for gRPC web proxy endpoint (#19051)
  • Implement staking activation with nonzero shard/realm (#19010)
  • Implement fee changes for HIP-991 (#18991)
  • add proper handling for unknown function calls in system contracts (#18733)
  • Capture GRPC/SDK usage metrics (#18469)
  • enable the jumbo transaction feature flag (#18969)
  • enhance logging validation for otter tests (#18897)
  • local deterministic generation (#18930)
  • add debug logs on key places (#18890)
  • Limit the callData field instead of ethereumData (#18647)

​
Bug Fixes

  • Keep node weights in HintsConstruction (#19344)
  • Improve error handling when setting auto renew period (#19303)
  • 19319: Improve MerkleDb reconnect / compaction synchronization (#19321)
  • 19301 Updated StateIdentifier enum (#19302)
  • 19259 Fix race condition when setting freeze round value (#19299)
  • Fix batch transaction fees (#19101)
  • Correct HapiCryptoCreate staked account ID parsing (#19283)
  • ConcurrentModificationException in InMemoryAppender (#19266)
  • Fix the transactionFee in the record for ConsensusSubmitMessage with custom fees (#19201)
  • Move jumbo transaction size check only at ingest (#19118)
  • Remove default shard and realm constants (#19123)
  • Only use inner results for BATCH_INNER dispatches (#19157)
  • Use CompositeFilter for console logging (#19171)
  • 19162 Open clause for JMS runtime for junit-extensions (#19163)
  • Decouple shard/realm from hapiTestMisc (#19083)
  • Inner transaction node setting in test-clients (#19150)
  • asTokenId can generate TokenId with negative shard and realm (#18997)
  • Fix error in TipsetEventCreatorTests (#19120)
  • Decouple hapiTestSmartContracts shard and realm (#19077)
  • Update to respect 0.2.3-SNAPSHOT max CRS parties (#19106)
  • 19054: Need a way to check if a MerkleDb compaction tasks are running (#19069)
  • Change default decline_reward to true for nodes created during genesis (#19086)
  • NoArgsConstructor has duplicated get() method (#19089)
  • Decouple hapiTestToken (#18985)
  • Update Roster Schema isUpgrade check (#19006)
  • add required module to Otter tests test fixtures module info (#19024)
  • Flaky Jumbo transactions tests (#19015)
  • Improve exception handling when payer account is not meeting the specifications (#18995)
  • migrate judge hashes on birth rounds (#19000)
  • Assign nGen for GUI generated events (#18986)

​
Performance Results

​
Release v0.62

MAINNET UPDATE: JUNE 25, 2025
TESTNET UPDATE: JUNE 3, 2025

​
Release Highlights

Release 0.62 delivers substantial improvements in Ethereum compatibility, continuing Hedera’s commitment to providing a seamless and cost-effective experience for developers and ecosystem participants building with Ethereum tools and infrastructure. In addition, this release updates the HIP-991 SubmitMessage fees and lays the groundwork for block streams. What’s new in Release 0.62?

​
Jumbo Ethereum Transaction Support (HIP-1086)

Historically, the Hedera API (HAPI) transaction size has been limited to 6 KB. Many Ethereum smart contracts and certain Ethereum contract calls exceed this limit. To work around this, developers previously had to utilize Hedera’s file service to upload larger contracts or call data in multiple 6 KB chunks — a process that added complexity, cost, and latency. Release 0.62 eliminates this friction by supporting a significantly larger transaction size of almost 128 KB for smart contract transactions, thereby simplifying EVM developer workflows and improving performance. Key benefits:
  • Simplified development: Eliminates the need to write and maintain custom code to handle 6 KB chunking.
  • Reduced cost and latency: Streamlines common operations such as ContractCreate, ContractCall, and EthereumTransaction.
  • Improved cost efficiency for JSON-RPC relays: Lowers operational costs for relay providers.
  • Enhanced Ethereum compatibility: Brings the experience of creating and calling smart contracts on Hedera closer to native Ethereum workflows.
To support this capability, the release also introduces a reworked throttling system that protects against potential denial-of-service (DoS) attacks while maintaining fairness across transaction sizes.

​
Zero-Cost EthereumTransaction on Success (HIP-1084)

A frequently reported pain point from JSON-RPC relay operators has been the cost of submitting wrapper EthereumTransactions. While gas costs for contract execution are typically borne by the calling entity (EOA or contract), relay operators have been required to fund the HBAR-based transaction fee — resulting in reduced adoption and ecosystem participation. Release 0.62 addresses this by eliminating the cover charge for EthereumTransactions where the inner call completes and pays for the gas consumed.

​
Key benefits:

  • Simplified relay operation: Removes the need for relay operators or embedded relays in dApps to maintain funded HBAR accounts for successful calls.
  • Enhanced Ethereum compatibility: Further enhances Hedera’s Ethereum compatibility by charging all costs in gas alone.
  • Better ecosystem support: Encourages greater participation by third-party relay operators and dApp developers.
To maintain network security, malformed, underfunded, or invalid contract calls that fail to cover gas fees through regular mechanisms will still be charged a fee in order to prevent abuse.

​
Other updates:

In addition to the aforementioned features that improve Ethereum compatibility, Release 0.62 introduces two other updates:
  • SubmitMessage API calls for an HCS topic with Custom Fees (HIP-991) have been updated to $0.05 for the Hedera network.
  • Foundational improvements in block stream management and handling workflows that will enable future features in block streaming capabilities and performance in upcoming releases.

​
Summary:

Release 0.62 represents an important milestone toward making Hedera a highly competitive platform for Ethereum-compatible applications, completes the implementation of HIP-991, and sets up the foundation for streaming the network blocks and state information.

​
Build 0.62.6

Full Changelog: v0.62.5…v0.62.6

​
Build 0.62.5

  • chore: Remove the migration code for setting declineReward=true for all nodes on upgrade (#19338)

​
Build 0.62.4

Full Changelog: v0.62.3…v0.62.4

​
Build 0.62.3

Full Changelog: v0.62.2…v0.62.3

​
Build 0.62.2

Full Changelog: v0.62.1…v0.62.2

​
Build 0.62.1

Full Changelog: v0.62.0…v0.62.1

​
Build 0.62.0

Features
  • remove code deposit gas charge waiver (#18797)
  • decouple backend throttle config from front end and add support for burst (#18743)
  • Update consensus to use nGen for determining when to recalculate metadata (#18882)
  • add cGen (#18867)
  • HIP-1046 Extend node address book with gRPC web proxy endpoint (#18766)
  • EventCreator uses nGen instead of generation (#18737)
  • Otter test logging improvements (#18850)
  • Add new v0.62 module and HederaEVM class (#18535)
  • Modifications to EventHeader for Block Stream (#18548)
  • Add otter test module (#18646)
  • handle ResendBlock block node responses (#18747)
  • Handle BlockAcknowledgements received from Block Nodes (#18536)
  • 18593: Need a mechanism to repair key to path mapping from data files at startup (#18625)
  • Jumbo bytes throttle (#18389)
  • Use existing key to create an account (#18611)
  • Remove use of generation from sync (#18590)
  • move parent event descriptors (#18524)
  • Long Term Schedule Transaction Support For DAB transactions (#18539)
  • Implement Non-deterministic Generation (#18506)
  • Stream to Block Node’s immediately without waiting BlockProofs (#18450)
  • Enhance yahcli rekey with ECDSA support (#18515)
  • Implement daily node rewards (#18441)
  • add HAPI verb to override the hederaFunctionality (#18481)
  • Increase the buffer size of ethereumCall gRPC endpoint (#18321)
  • Add ingest workflow jumbo checks (#18312)
  • try using non-zero realm/shard (#18092)
Bug Fixes
  • 18903: Tighten HDHM repair checks (#18906)
  • detach FCQueue copy when serializing (#18863)
  • Fix failing test in crypto-base (#18888)
  • fix copy paste error in TipsetEventCreatorTests (#18876)
  • disable GasCalculationIntegrityTest test suite (#18868)
  • 18844: HDHM repair mechanism should not be enabled for snapshots (#18859)
  • 18856: ReconnectHashLeafFlusher uses a wrong config (#18857)
  • NPE in HalfDiskHashMap (#18854)
  • Remove unused injections and fix tests (#18651)
  • Fix transactionFee in batch transactions (#18835)
  • Correctly populate sysfiles with node info (#18834)
  • Revalidate collector token association on transfer (#18674)
  • Fix the NPE in DefaultIssDetector.handleCatastrophic (#18830)
  • flaky completedHollowAccountOperationsFuzzing test (#18816)
  • Fix flakiness in HIP-1064 tests (#18822)
  • 18813: VirtualMapLargeReconnectTest.multipleAbortedReconnectsCanSucceed is unstable (#18814)
  • Use getIfUsable() in ApproveAllowanceValidator (#18580)
  • add auto-renew check for negative values (#18765)
  • 18795: HDHM repair mechanism can be improved to clean stale buckets (#18796)
  • Only allow creation of accounts that match the configured shard/realm (#18806)
  • Move sort before filterLikelyDuplicates (#18802)
  • adding validation for deleted token on unpause (#18671)
  • Update flow-pull-request-formatting.yaml (#18790)
  • 18658: ReconnectNodeRemover.setPathInformation() may cause OOM (#18708)
  • Remove mono logic returning the wrong response code (#18698)
  • 1280 hip 1056 block item with failed contract create result contains a contract (#18728)
  • Improved error handling for airdrops with multiple senders (#18604)
  • Use getIfUsable() when validate custom fees (#18576)
  • Fix TokenCreateTransaction TCK issues (#18577)
  • Add guard around LATEST_XTS_PASS_TAG (#18687)
  • Also archive config.txt as part of network archiving process (#18427)
  • Add back sorting of sync events (#18657)
  • memory leak in HalfDiskHashMap.endWriting() (#18659)
  • Call endRound after dispatch (#18620)
  • Only “go back” in cons time for post-restart system work (#18654)
  • 18561 Threads outlive the SequentialTaskScheduler created during test (#18391)
  • airdrop TCK issues fixes (#18582)
  • 18571: Current path range should be respected when path to hash and path to KV indices are restored (#18592)
  • contract get bytecode query to return the redirect code for hts token addresses (#18464) (#18563)
  • Fix flaky PcesFile tests (#18474)
  • Utilize more than one thread for SSL accept handling (#18557)
  • Ensure BlockStreamManager#endRound() is called after dispatching system txns (#18554)
  • 17180 EventCreator ignores HealthMonitor update when squelching enabled (#18387)
  • Import sentinel key from hapi utils (#18512)
  • compile fix (#18510)
  • Should reject a FILE_UPDATE to 0.0.123 with an invalid throttle definition (#18417)
  • 18410: Bucket integrity check in HDHM.ReadUpdateBucketTask can be improved (#18411)
  • HIP-1028 cleanup and versioning for GetTokenKey (#18304)
  • update reference to unhex method (#18470)

​
Performance Results

​
Release v0.61

MAINNET UPDATE: MAY 30, 2025
TESTNET UPDATE: MAY 20, 2025

​
Release Highlights

This release focuses on enhancing network incentivization and improving overall system robustness and developer experience.

​
Hiero Improvement Proposals (HIPs)

  • Daily rewards for active nodes HIP-1064: Full implementation of a daily reward mechanism for active consensus nodes, including an option for node operators to decline these rewards. This enhances network health by incentivizing consistent node uptime and participation, while providing operators flexibility in managing their rewards and improving network decentralization. Please note this feature will be disabled until a July 1, 2025 launch date.
  • HIP-551 (Atomic Batch Transactions): HIP-551 This release includes the implementation of Atomic Batch Transactions; however, due to technical challenges identified in testing, this feature has been temporarily disabled. As a result, users attempting to submit Atomic Batch Transactions will receive a status code of BUSY from the network. We are actively working to resolve these issues and plan to enable this feature in a future update.

​
New Features

  • Node Reward Opt-Out (HIP-1064): Node operators can now decline daily node rewards using a new decline_reward boolean flag in NodeCreateTransactionBody and NodeUpdateTransactionBody. This offers greater control and flexibility for node operators based on their specific requirements. The default value for this flag will be set to true to decline rewards by default. 
    • // Example: Opting out of node rewards during node creation
NodeCreateTransactionBody createBody = NodeCreateTransactionBody.newBuilder()
    // ... other fields like accountID, description, etc.
    .setDeclineReward(true) // Set to true to decline node rewards
    .build();

​
Notable Bug Fixes

  • #17478: Corrected Cancun SELFDESTRUCT Semantics: Fixed incorrect SELFDESTRUCT behavior per EIP-6780 post-Cancun, where a contract specifying itself as the beneficiary in a non-creation transaction erroneously triggered a SELF_DESTRUCT_TO_SELF error. The fix ensures compliance with EIP-6780, allowing the operation to proceed without deleting the contract or transferring its balance, including native tokens. Additionally, refactored CustomSelfDestructOperation.execute to streamline validation checks before state changes. Impact: Enhances EVM compatibility and reliability on Hedera for contracts using SELFDESTRUCT, ensuring correct execution under post-Cancun rules.

​
Build 0.61.10

  • chore: (cherry-pick to tag 0.61.10) Disable the defaults for contracts.evm.ethTransaction.zeroHapiFees.enabled and nodes.nodeRewardsEnabled by @Neeharika-Sompalli in #19521
Full Changelog: v0.61.9…v0.61.10

​
Build 0.61.9

Full Changelog: v0.61.8…v0.61.9

​
Build 0.61.8

Full Changelog: v0.61.7…v0.61.8

​
Build 0.61.7

Full Changelog: v0.61.6…v0.61.7

​
Build 0.61.6

Full Changelog: v0.61.5…v0.61.6

​
Build 0.61.5

Full Changelog: v0.61.4…v0.61.5

​
Build 0.61.4

  • fix: 0.61 cherry-pick: Correctly populate sysfiles with node info by @mhess-swl in #18884
  • fix: 18771: Backport fixes for 18593, 18795, 18844, and 18903 to release 0.61 by @artemananiev in #18799
  • chore: (0.61) add fee refund mechanism, use for successful EthereumTransaction by @tinker-michaelj in #18913
Full Changelog: v0.61.3…v0.61.4

​
Build 0.61.3

Full Changelog: v0.61.2…v0.61.3

​
Build 0.61.2

Full Changelog: v0.61.1…v0.61.2

​
Build 0.61.1

​
What’s Changed

Full Changelog: v0.61.0…v0.61.1

​
Build 0.61.0

Features
  • Dynamic peers for the sync network (#18051)
  • Add JumboTransactionsConfig (#18277)
  • implement exponential backoff for connections to Block Nodes (#18055)
  • HIP-1028 Fungible and NFT Token Info versioning (#18013)
  • add SCHEDULE_EXPIRY_NOT_CONFIGURABLE validation (#18239)
  • Add messages for skip and resend block to block service (#18133)
  • Create a HAPI test to validate birth round migration (#18005)
  • Close blocks during fatal ISS (#17942)
  • HIP-1028 apply versioning to Update Token and Update Token Keys System Contracts (#17994)
  • Add feature flag for CRS (#18073)
  • change version to 0.61 (#18088)
  • Support non-zero realms for contracts service (#18010)
  • HIP-551 atomic batch transactions (#17333)
Bug Fixes
  • Detect ISSes when states are not produced for every round (#18399)
  • remove @OrderedInIsolation from contract bdd tests (#18400)
  • HIP-632 fix alias length check (#18385)
  • Extended suite failure during insertRemoveAndModifyOneMillion (#18407)
  • 18393 metrics not updated in PlatformWiring (#18394)
  • Fix candidate roster adoption logic (v61) (#18372)

​
Performance Results

​
Release v0.60

MAINNET UPDATE: APRIL 16, 2025
TESTNET UPDATE: April 9, 2025

​
Release Highlights

This release focuses on significant performance improvements, enhanced developer tooling, and improved error handling.

​
Hiero Improvement Proposals (HIPs)

HIP-1021: Improve Assignment of Auto-Renew Account ID for Topics
  • Full implementation of improved auto-renew account ID assignment for topics, enabling setting autoRenewAccountId during topic creation without an admin key.
  • Developers benefit from simplified topic management and reduced risk of unexpected expirations.

​
Build 0.60.1

Full Changelog: v0.60.0…v0.60.1

​
Build 0.60.0

Full Changelog: v0.59.5…v0.60.0

​
Performance Results

​
Release v0.59

MAINNET UPDATE: MARCH 26, 2025
TESTNET UPDATE: MARCH 18, 2025

​
Release Highlights

​
HIPs:

​
HIP-991: Topic Fees

  • Description: ​HIP-991 introduces an optional fee system for submitting messages to topics on the Hedera network, aiming to enhance economic scalability and simplify operations for topic operators.
  • Benefits: Empowers topic operators with greater control over their topics, offering mechanisms to monetize and manage access. Key features include:
    • Optional Submission Fees: Topic operators can set optional fees for message submissions, payable in HBAR or Hedera Token Service (HTS) fungible tokens.​
    • Fee Schedule Key: A new ‘Fee Schedule Key’ allows operators to manage and update fee structures. This key must be set during topic creation.​
    • Custom Fee Distribution: Collected fees can be distributed to multiple accounts, supporting both HBAR and HTS tokens.​
    • Fee Exemptions: Operators can specify a list of keys that are exempt from fees, allowing certain users to submit messages without incurring charges.​

​
HIP-755: Schedule Service System Contract signSchedule(address, bytes)

  • Description: This HIP introduces a Schedule Service System Contract to enhance the Hedera Smart Contract Service (HSCS) by enabling smart contracts to interact with scheduled transactions. This release includes signSchedule(address, bytes).
  • Benefits: HIP-755 introduces a Schedule Service System Contract to enhance the Hedera Smart Contract Service by enabling smart contracts to interact with scheduled transactions. signSchedule(address, bytes) method, allows smart contracts to pass along the signature from an EOA needed for a scheduled transaction.

​
HIP-756: Scheduled Token Create/Update Transactions via Smart Contract

  • Description: Enables scheduling token create and update operations through smart contracts, with implementation of the scheduleNative system contract function.
  • Benefits: Expands smart contract functionality by allowing developers to schedule token operations directly from smart contracts, providing more flexibility in DApp development.

​
Build 0.59.5

  • fix: Fix candidate roster adoption logic (v59) by @poulok in #18359
Full Changelog: v0.59.4…v0.59.5

​
Build 0.59.4

Full Changelog: v0.59.3…v0.59.4

​
Build 0.59.3

Full Changelog: v0.59.2…v0.59.3

​
Build 0.59.2

Full Changelog: v0.59.1…v0.59.2

​
Build 0.59.0

  • refactor: 16436 Removed MerkleRoot interface. by @imalygin in #17130
  • fix: move and change value of Dockerfile environment variable by @matteriben in #16239
  • build: Roll hiero gradle conventions to version 0.1.4 by @andrewb1269hg in #17149
  • build(deps): bump actions/setup-java from 4.5.0 to 4.6.0 by @dependabot in #17113
  • build(deps): bump gradle/actions from 4.2.1 to 4.2.2 by @dependabot in #17111
  • chore: Update hedera-services to rename develop as main by @rbarker-dev in #17091
  • chore: Update workrflow names to point to main instead of develop by @rbarker-dev in #17158
  • ci: Update Check Integration/XTS Job State to include GH_TOKEN by @rbarker-dev in #17160
  • ci: add id_token write permission to node-flow-deploy-release-artifact.yaml by @rbarker-dev in #17161
  • feat: Support overwrites for interface bindings and endpoints by @timo0 in #17117
  • chore: Refactor hapi tests to use hapiTest(...) instead of defaultHapiSpec(...) (Part 3) by @mhess-swl in #16698
  • feat: consolidate hbar transfer list when decoding cryptoTransfer function by @lukelee-sl in #17165
Full Changelog: v0.58.9…v0.59.0

​
Release v0.58

MAINNET UPDATE: MARCH 12, 2025
TESTNET UPDATE: FEBRUARY 11, 2025

​
Release Highlights

This release introduces several new features, improvements, and bug fixes, including:

​
HIPs

  • HIP-423 Long-Term Scheduled Transactions: Update to ScheduleSign throttles changed: The ScheduleSign transaction is now throttled like other transactions and can now be managed by the default throttling mechanism on the network. (#16958, #16959) This completes HIP-423.
  • HIP-755 authorizeSchedule(address)
    Adds functionality to the Hedera Schedule Service System contract so that a smart contract can sign a referenced scheduled transaction using its contract key, enabling automated execution of scheduled transactions directly from smart contracts. (#16983), the remaining outstanding features to complete HIP-755 will be provisioned in release .59.

​
Other Notable Changes

  • Enabled mirror node to simulate contract calls: The standalone transaction executor now supports custom Operations. Developers can use this feature to create and execute custom operations that are not part of the standard Hedera API. (#17354)
  • Enhancing Dynamic Address Book v2 NodeCreate and NodeDelete transaction signature requirements changed:
    • The NodeCreate transaction now requires the admin key and one of the treasury account key, system admin key, or address book admin key to sign.
      • The NodeDelete transaction is now a non-privileged transaction and requires one of the admin key, treasury account key, system admin key, or address book admin key to sign. (#16900, #17021, #16990, #17029)
  • Ensuring state changes are now in block streams: Refactored out-of-band state modifications: All out-of-band state modifications have been refactored to be done in Schemas. (#16843)
  • Increased CryptoGetAccountBalance throttle: The throttle for the CryptoGetAccountBalance query has been increased to the number of network nodes times 1,000,000 plus a buffer. This change addresses an issue where the throttle was too low, leading to throttling errors. (#16850, #16857)

​
Build 0.58.13

  • Fail NFT airdrops that would trigger royalty fee payments.
Full Changelog: v0.58.11…v0.58.13

​
Build 0.58.11

  • Add safety checks before Besu secp256k1 native library invocations (c.f. here.
  • Ignore approval flag when de-duplicating account ids in a TokenTransferList.
Full Changelog: v0.58.10…v0.58.11

​
Build 0.58.10

Full Changelog: v0.58.9…v0.58.10

​
Build 0.58.9

Full Changelog: v0.58.7…v0.58.9

​
Build 0.58.8

Re-tag of v0.58.7 to trigger workflowull Changelog: v0.58.6…v0.58.7

​
Build 0.58.7

Full Changelog: v0.58.6…v0.58.7

​
Build 0.58.6

  • chore: Reapply “FileService address book and node details” by @mhess-swl in #17543
Full Changelog: v0.58.5…v0.58.6

​
Build 0.58.5

Full Changelog: v0.58.3…v0.58.5

​
Build 0.58.3

  • feat: cherry-pick: Generated Files 101 & 102 Sequentially Ordered by Node ID by @iwsimon in #17289
Full Changelog: v0.58.2…v0.58.3

​
Build 0.58.0

New ContributorsFull Changelog: v0.57.3…v0.58.0

​
Release v0.57

MAINNET UPDATE: JANUARY 28, 2025
TESTNET UPDATE: JANUARY 8, 2025

​
Release Highlights

This release introduces several new features, improvements, and bug fixes, including:

​
HIPs

  • HIP-423: Long-Term Scheduled Transactions: This release completes the implementation of HIP-423, enabling schedules to execute transactions at a future date and time. This provides developers with a powerful tool for automating on-chain actions and building time-based applications. Benefits include:
    • Automated Transactions: Schedule transactions to execute automatically at a specific time.
    • Time-Based Applications: Build applications that rely on time-based events, such as recurring payments or token distributions.
    • Enhanced Security: Schedule transactions can be signed by multiple parties, ensuring that they are executed only when all required approvals are obtained.

​
New Features

  • Node Operator Queries: This release introduces a dedicated gRPC port for node operators to perform free queries. This enables node operators to monitor the network and their nodes more efficiently without incurring transaction fees.
  • Proxy Redirect Contract for Schedule Entities: This release adds support for a proxy redirect contract for calls to schedule transactions. This allows EOAs to make function calls in schedule entity addresses, enabling more flexible and dynamic interactions with scheduled transactions.
  • HSS System Contract: This release introduces the Hedera Schedule Service (HSS) system contract, providing a set of functions for managing scheduled transactions, including signing and authorizing schedules.
  • Support for Extra Dispatch Authorizations: The ScheduleSignHandler now supports authorizing Key{contractID=0.0.X} and Key{delegatable_contract_id=0.0.X} keys in a schedule’s signatories list, enabling more granular control over schedule execution.

​
Build 0.57.5

Full Changelog: v0.57.4…v0.57.5

​
Build 0.57.4

Full Changelog: v0.57.3…v0.57.4

​
Build 0.57.3

  • fix: tokenClaimAirdrop throws NPE on null sender or receiver by @kimbor in #17096
Full Changelog: v0.57.2…v0.57.3

​
Build 0.57.2

Full Changelog: v0.57.1…v0.57.2

​
Build 0.57.1

Full Changelog: v0.56.7…v0.57.1

​
Performance Results

​
Release v0.56

MAINNET UPDATE: DECEMBER 11, 2024
TESTNET UPDATE: DECEMBER 4, 2024

​
Release Highlights

​
HIPs

HIP-869 Dynamic Address Book—Stage 1: This release includes the implementation of HIP-869, enabling the Dynamic Address Book. Node operators can now update node details and address books via Hedera transactions. This streamlines network operations and enables node operators to manage their associated node entries directly in the Address Book. HIP-904 System Contract Functions: Implements the System Contract Functions section within HIP-904. Introduces Hedera Token Service (HTS) support for the airdrop-related capabilities. These functions are implemented as system contract functions, making it possible for smart contracts to issue Frictionless Airdrops, Token Reject, and AutomaticToken Association configurations for efficient management. HIP-632 - isAuthorized(): The isAuthorized() function introduced in HIP-632 extends the Hedera Account Service (HAS) System Contract, enabling smart contracts to authenticate signatures against Hedera accounts. This provides functionality akin to the validation step following Ethereum’s ECRECOVER, without recovering public keys. It supports ECDSA, ED25519, and complex keys such as threshold keys, though ECDSA is recommended for compatibility and interoperability with Ethereum. This builds on the previous functionality of isAuthorizedRaw() released in 0.52. Other Notable Changes: Block Streams - Dev Access Preview: Block Streams is a new output stream that will replace Hedera’s existing event and record streams into a single stream of verifiable data. This consolidated approach not only simplifies data consumption but also enhances Hedera’s capabilities by including state data. Starting with version 0.56, consensus nodes will publish preview block stream files alongside the existing record stream, which remains the authoritative source of truth for Hedera. This preview allows the community to explore, test, and provide feedback on this new feature, paving the way for its future adoption. Migration from .pfx to .pem Cryptography Files: The consensus node cryptography system was migrated from using .pfx files to more manageable .pem files.

​
Build 0.56.7

  • chore: Cherry-Pick (0.56): Increase CryptoGetAccountBalance throttle by @kimbor in #16852
Full Changelog: v0.56.6…v0.56.7

​
Build 0.56.6

  • chore: Cherry Pick: Modify and mount default block streams output directory by @mhess-swl in #16753
Full Changelog: v0.56.5…v0.56.6

​
Build 0.56.5

  • fix: correct a missing conversion between AddressBook cert hash hex-string-as-bytes and actual SHA2-384 hash bytes for Node entries. by @jsync-swirlds in #16659
  • chore: Do stricter validation of X.509 gossip cert in DAB transactions by @tinker-michaelj in #16666
Full Changelog: v0.56.4…v0.56.5

​
Build 0.56.0

New ContributorsFull Changelog: v0.55.1…v0.56.0

​
Performance Results