Hedera Services
Hedera Services release information
Last updated
Was this helpful?
Hedera Services release information
Last updated
Was this helpful?
Visit the for the latest versions supported on each network.
MAINNET UPDATE SCHEDULED: DECEMBER 11, 2024
TESTNET UPDATE SCHEDULED: DECEMBER 4, 2024
MAINNET UPDATE SCHEDULED: NOVEMBER 13, 2024
TESTNET UPDATE SCHEDULED: NOVEMBER 5, 2024
Throttle for AccountBalanceQuery
A new throttle for AccountBalanceQuery requests to manage and optimize query load on the network.
TESTNET UPDATE SCHEDULED: OCTOBER 29, 2024
MAINNET UPDATE SCHEDULED: OCTOBER 23, 2024
TESTNET UPDATE SCHEDULED: OCTOBER 16, 2024
This release introduces exciting new features and improvements, including HIP-904 for token airdrops, and HIP-1010 for updating custom fee via smart contracts.
Implementation: Partial implementation
Delivered in this release:
TokenAirdrop transaction is similar to crypto transfers, but differs in one fundamental way - when an airdrop is performed and the receiver does not have available or automatic association slots, rather than failing, the transfer will be kept in state as a pending transfer.
TokenClaimAirdrop transaction introduced for recipients to claim pending airdropped tokens.
TokenCancelAirdrop transaction introduced giving senders the ability to cancel unclaimed airdrops.
Benefits:
Streamlines token distribution, empowers token creators, developers, and projects by allowing them to distribute tokens more efficiently to a wider audience.
Implementation: Full implementation
Delivered in this release:
updateFungibleTokenCustomFees system contract function for updating custom fees for fungible tokens.
updateNonFungibleTokenCustomFees system contract function for updating custom fees for non-fungible tokens.
Benefits:
Enables smart contracts to manage token custom fees, providing more dynamic and autonomous token management capabilities.
TESTNET UPDATE SCHEDULED: OCTOBER 2, 2024
MAINNET UPDATE SCHEDULED: SEPTEMBER 11, 2024
TESTNET UPDATE SCHEDULED: SEPTEMBER 4, 2024
Delivered in release 0.53
isAssociated for token association via proxy facade contract.
Syntax
<tokenAddress>.isAssociated()
Example
IHRC719(<tokenAddress>).isAssociated()
Delivered in prior release(0.38)
Associate and Dissociate Tokens via proxy facade contract
Benefits
Token functions are callable by both EOAs and contracts.
Partial completion of HIP-904 Delivered in 0.53
Sender pays for association
Sender now pays for token association at the time of HTS transaction execution.
Max_auto_associations
Default value for max_auto_assocations will now be -1 meaning that if an account is created automatically by performing a token transfer to an alias that does not yet exist the account is configured with unlimited automatic token association.
HAPI:CryptoCreate will continue to have max_auto_associations defaulting to 0.
Accounts created before the launch of this feature will remain unchanged.
Token reject
Introduces TokenReject Transaction.
maxAutoAssociation users can update their account preferences to unlimited association giving the ability to receive any airdrops without explicitly having to associate with that token.
Slots are only paid for when used, and are initially paid for by the sender during automatic associations.
Entire scope of HIP-850 delivered in release 0.53.
Enables the Supply Key to update an NFT metadata field while the NFT is held in the treasury account via TokenUpdateNftsTransaction function for a specific NFT serial number.
NFT owners can return an NFT to treasury custody in order to update parameters within the metadata of the NFT.
NFT cannot be updated by unauthorized parties once distributed.
Delivered in release .53:
Itemized auto-creation fees
Unified child consensus times
Clean hollow account completion records
Synthetic file creations at genesis
Use natural order for preceding dispatch records
Planned for delivery in release .54:
Fail fast on throttled child transactions
This HIP refines the legibility and extensibility of the record stream.
Accepts three parameters:
address
messageHash
signatureBlob
Validates the provided address (Hedera Account ID or virtual address)
Determines signature type based on signatureBlob length:
65 bytes: ECDSA
64 bytes: ED25519
Extracts v, r, and s components
Runs ECRECOVER to recover signing address
Compares result with the account's virtual addresses
Retrieves Hedera address
Checks for single associated key on account
Verifies signature against message hash and account key
Similar functionality to Ethereum's ECRECOVER precompile
Supports both ECDSA and ED25519 signature verification
Works with Hedera Account IDs and virtual addresses
Simplifies signature verification in smart contracts
Streamlines transaction authentication within contracts
Enhances Hedera-Ethereum authorization flow compatibility
Improves developer experience with familiar authorization mechanism
Allows users to reject undesired tokens
Transfers thefull balance of one or more tokens from the requesting account to the treasury
Supports rejection of both fungible and non-fungible tokens
Handles up to 10 token rejections in a single transaction
Bypasses custom fees and royalties defined for the rejected tokens
Enables users to remove unwanted tokens from their accounts
Protects users from potential scams or unwanted airdrops
Allows rejection of tokens regardless of how they were acquired (manual or automatic association)
Helps users manage their token holdings more effectively
Prevents users from being forced to pay exorbitant or potentially malicious fees to remove tokens
Maintains account association with the token, allowing for future transactions if desired
Provides a simple mechanism for users to clean up their accounts
Enhances user control over their token portfolio
Improves overall user experience in token management
MAINNET UPDATE SCHEDULED: AUGUST 28, 2024
TESTNET UPDATE SCHEDULED: AUGUST 14, 2024
TESTNET UPDATE SCHEDULED: JULY 31, 2024
The accounts.maxNumber and nfts.MaxAllowedMints values both remain at 20 million for this release
MAINNET UPDATE: JULY 17, 2024
TESTNET UPDATE: JULY 2, 2024
Functionality
Defines a new function to the Hedera Token Service system contract that allows for the atomic transfer of HBAR, fungible tokens and non-fungible tokens.
Function cryptoTransfer(TransferList transferList,TokenTransferList[] tokenTransfer)
Exposes an existing HAPI call via smart contracts.
Transfer respects granted allowances.
Benefits
Enables native royalty support on the EVM since native $hbar can now be transferred using spending allowances
Direct interaction with HBAR and HTS tokens
Eliminates the need for token wrapping.
Enhances efficiency and reduces complexity.
Cuts costs by removing intermediary steps i.e., wrapping assets to interact with them.
Enables native royalty support on the EVM since native HBAR can now be transferred using spending allowances
Functionality
Introduces a new Hedera Account Service system contract.
Enables querying and granting approval of HBAR to a spender account from smart contracts code
hbarAllowance, hbarApprove
Developers do not have to context switch out of smart contract code
Benefits
Introduces new account proxy contract for HBAR allowances
Enables grant, retrieve, and manage HBAR allowances within smart contracts
Developers do not have to context switch out of smart contracts code
Simplifies workflows and enhances security
Expands potential use cases, especially for DeFi and token marketplaces
MAINNET UPDATE: JUNE 20, 2024
TESTNET UPDATE: JUNE 5, 2024
MAINNET UPDATE: MAY 22, 2024
TESTNET UPDATE: MAY 14, 2024
MAINNET UPDATE: APRIL 25, 2024
TESTNET UPDATE: APRIL 18, 2024
TESTNET UPDATE: APRIL 11, 2024
MAINNET UPDATE: APRIL 4, 2024
TESTNET UPDATE: MARCH 28, 2024
TESTNET UPDATE: MARCH 20, 2024
fix: Update Configuration hashesRamToDiskThreshold to 0 in MerkleDbConfig
fix: Backport the fix for virtual map flushes.
TESTNET UPDATE: FEBRUARY 29, 2024
MAINNET UPDATE: FEBRUARY 21, 2024
TESTNET UPDATE: FEBRUARY 6, 2024
TESTNET UPDATE: JANUARY 30, 2024
TESTNET UPDATE: JANUARY 23, 2024
MAINNET UPDATE: JANUARY 9, 2024
TESTNET UPDATE: DECEMBER 28, 2023
MAINNET UPDATE: DECEMBER 19, 2023
TESTNET UPDATE: DECEMBER 12, 2023
MAINNET UPDATE: NOVEMBER 27, 2023
TESTNET UPDATE: NOVEMBER 2, 2023
Services v0.43.0 adds the following features:
Services v0.43.0 adds the following enhancements:
MAINNET UPDATE: OCTOBER 24, 2023
TESTNET UPDATE: SEPTEMBER 26, 2023
This release updates the platform SDK version from 0.42.0 to 0.42.6, which removes reconnect.asyncStreamTimeout from the settings files. Doing so ensures that this property will default to the value specified in code (300 seconds).
MAINNET UPDATE: SEPTEMBER 20, 2023
TESTNET UPDATE: AUGUST 22, 2023
MAINNET UPDATE: AUGUST 15, 2023
TESTNET UPDATE: AUGUST 8, 2023
TESTNET UPDATE: JULY 19, 2023
MAINNET UPDATE: JULY 11, 2023
TESTNET UPDATE: JUNE 21, 2023
Services v0.39.0 adds the following features:
MAINNET UPDATE: JUNE 8, 2023
TESTNET UPDATE: JUNE 1, 2023
TESTNET UPDATE: MAY 18, 2023
MAINNET UPDATE: MAY 17, 2023
TESTNET UPDATE: APRIL 24, 2023
MAINNET UPDATE: APRIL 20, 2023
TESTNET UPDATE: APRIL 13, 2023
TESTNET UPDATE: APRIL 4, 2023
Services v0.36.0 adds the following functionality:
update hedera-services to use FSTS CLI instead of system properties
6166: Migrate VirtualMap data from JasperDB to MerkleDb data sources
Implementation of current network functionality in new, modularized application architecture: consensus operations, query workflow, and various preHandle implementations
Changes from services v0.35.2 have also been ported to v0.36.0.
After the security incident on March 9th, the engineers conducted a thorough analysis of the Smart Contract Service and the Hedera Token Service system contracts.
As part of this exercise, we did not find any additional vulnerabilities that could result in an attack that that which we witnessed on March 9th.
The team also looked for any disparities between the expectations of a typical smart contract developer who is used to working with the Ethereum Virtual Machine (EVM) or ERC token APIs and the behaviors of the Hedera Token Service system contract APIs. Such differences in behavior could be used by a malicious smart contract developer in unexpected ways.
In order to eliminate the possibility of these behavioral differences being utilized as attack vectors in the future, the consensus node software will align the behaviors of the Hedera Smart Contract Service token system contracts with those of EVM and typical token APIs such as ERC 20 and ERC 721.
As a result, the following changes are made as of the mainnet 0.35.2 release on March 31st:
An EOA (externally owned account) will have to provide explicit approval/allowance to a contract if they want the contract to transfer value from their account balance.
The behavior of transferFrom system contract will be exactly the same as that of the ERC 20 and ERC 721 spec transferFrom function.
For HTS specific token functionality (e.g. Pause, Freeze, or Grant KYC), a contract will be authorized to perform the associated token management function only if the ContractId is listed as a key on the token (i.e. Pause Key, Freeze Key, KYC Key respectively).
The transferToken and transferNFT APIs will behave as transfer in ERC20/721 if the caller owns the value being transferred, otherwise it will rely on approve spender allowances from the token owner.
The above model will dictate entity (EOA and contracts) permissions during contract executions when modifying state. Contracts will no longer rely on Hedera transaction signature presence, but will instead be in accordance with EVM, ERC and ContractId key models noted.
As part of this release, the network will include logic to grandfather in previous contracts.
Any contracts created from this release onwards will utilize the stricter security model and as such will not have considerations for top-level signatures on transactions to provide permissions.
Existing contracts deployed prior to this upgrade will be automatically grandfathered in and continue to use the old model that was in place prior to this release for a limited time to allow for DApp/UX modification to work with the new security model.
The grandfather logic will be maintained for an approximate period of 3 months from this release. In a future release in July 2023, the network will remove the grandfather logic, and all contracts will follow the new security model.
Developers are encouraged to test their DApps with new contracts and UX using the new security model to avoid unintended consequences. If any DApp developers fail to modify their applications or upgrade their contracts (as applicable) to adhere to the new security model, they may experience issues in their applications.
MAINNET UPDATE: MARCH 31, 2023
TESTNET UPDATE: MARCH 16, 2023
After the security incident on March 9th, the engineers conducted a thorough analysis of the Smart Contract Service and the Hedera Token Service system contracts.
As part of this exercise, we did not find any additional vulnerabilities that could result in an attack that that which we witnessed on March 9th.
The team also looked for any disparities between the expectations of a typical smart contract developer who is used to working with the Ethereum Virtual Machine (EVM) or ERC token APIs and the behaviors of the Hedera Token Service system contract APIs. Such differences in behavior could be used by a malicious smart contract developer in unexpected ways.
In order to eliminate the possibility of these behavioral differences being utilized as attack vectors in the future, the consensus node software will align the behaviors of the Hedera Smart Contract Service token system contracts with those of EVM and typical token APIs such as ERC 20 and ERC 721.
As a result, the following changes are made as of the mainnet 0.35.2 release on March 31st:
An EOA (externally owned account) will have to provide explicit approval/allowance to a contract if they want the contract to transfer value from their account balance.
The behavior of transferFrom system contract will be exactly the same as that of the ERC 20 and ERC 721 spec transferFrom function.
For HTS specific token functionality (e.g. Pause, Freeze, or Grant KYC), a contract will be authorized to perform the associated token management function only if the ContractId is listed as a key on the token (i.e. Pause Key, Freeze Key, KYC Key respectively).
The transferToken and transferNFT APIs will behave as transfer in ERC20/721 if the caller owns the value being transferred, otherwise it will rely on approve spender allowances from the token owner.
The above model will dictate entity (EOA and contracts) permissions during contract executions when modifying state. Contracts will no longer rely on Hedera transaction signature presence, but will instead be in accordance with EVM, ERC and ContractId key models noted.
As part of this release, the network will include logic to grandfather in previous contracts.
Any contracts created from this release onwards will utilize the stricter security model and as such will not have considerations for top-level signatures on transactions to provide permissions.
Existing contracts deployed prior to this upgrade will be automatically grandfathered in and continue to use the old model that was in place prior to this release for a limited time to allow for DApp/UX modification to work with the new security model.
The grandfather logic will be maintained for an approximate period of 3 months from this release. In a future release in July 2023, the network will remove the grandfather logic, and all contracts will follow the new security model.
Developers are encouraged to test their DApps with new contracts and UX using the new security model to avoid unintended consequences. If any DApp developers fail to modify their applications or upgrade their contracts (as applicable) to adhere to the new security model, they may experience issues in their applications.
This includes,
CryptoTransfer to non-existing EVM address alias causing hollow-account creation.
Finalizing a hollow account with the payer signature in an incoming transaction
Use cases for HIP-583 that work in this release :
As a user with an ECDSA based account from another chain I can have a new Hedera account created based on my evm-address alias.
As a developer, I can create a new account using a evm-address alias via the CryptoTransfer transaction.
As a developer, I can transfer HBAR or tokens to a Hedera account using their evm-address alias.
As a Hedera user with an Ethereum-native wallet, I can receive HBAR or tokens in my account by sharing only my evm-address alias.
As a Hedera user with a Hedera-native wallet, I can transfer HBAR or tokens to another account using only the recipient's evm-address alias.
MAINNET UPDATE: FEBRUARY 9, 2023
TESTNET UPDATE: JANUARY 24, 2023
Use v0.34.3 SDK.
To ensure full test coverage of this intricate feature, it will first be enabled only on previewnet.
This release will not enable smart contract rent.
MAINNET UPDATE: JANUARY 12, 2023
TESTNET UPDATE: DECEMBER 22, 2022
Services v0.33.0 adds the following features:
Hyperledger Besu EVM updated to version 22.10.x
'accounts send' subcommand added to yahcli to support sending HTS token units
Developer documentation updates
MAINNET UPDATE: DECEMBER 9, 2022
TESTNET UPDATE: DECEMBER 1, 2022
TESTNET UPDATE: NOVEMBER 11, 2022
TESTNET UPDATE: OCTOBER 27, 2022
Services 0.31 completes the following features:
In addition to the above features,
Enables Smart Contract Traceability.
Adds some changes related to testability improvements.
MAINNET UPDATE: OCTOBER 21, 2022
TESTNET UPDATE: OCTOBER 19, 2022
TESTNET UPDATE: OCTOBER 6, 2022
The updateTokenInfo(address, HederaToken) call is especially powerful. If a token's admin key signs the transaction calling a contract, that contract can now make itself the token's treasury, assume authority to mint or burn units or NFTs, and so on.
All non-deleted contracts will have their expiry extended to at least 90 days after the upgrade date.
Deleted contracts will start to be purged from state; so a getContractInfo query that previously
returned CONTRACT_DELETED may now report INVALID_CONTRACT_ID.
About 90 days after the 0.30 upgrade, some contracts will begin to expire. The network will try to automatically charge the renewal fee (approximately $0.026 for 90 days) to the expired contract's auto-renew account. If an auto-renew account has zero balance, the network will then try to charge the contract itself.
A contract unable to pay renewal fees will enter a week-long "grace period" during which it is unusable, unless its expiry is extended via ContractUpdate or it receives hbar. After this grace period, the contract will be purged from state.
We strongly encourage all contract authors to set an auto-renew account for their contract. This isolates the contract logic from the existence of rent.
This release also brings two peripheral improvements:
It will become possible to schedule a CryptoApproveAllowance transaction.
MAINNET UPDATE: SEPTEMBER 27, 2022
TESTNET UPDATE: SEPTEMBER 7, 2022
TESTNET UPDATE: AUGUST 30, 2022
The HIP enumerates the ways; examples include a contract that revokes an account's KYC for a token, or deletes a token for which it has admin privileges, or even changes a token's supply key based on the metadata in an NFT!
Note there are four HIP-514 functions that will be part of release 0.30, as follows: getTokenExpiryInfo(address), updateTokenExpiryInfo(address, Expiry), updateTokenInfo(address, HederaToken), isToken(address token) and getTokenType(address token).
MAINNET UPDATE: AUGUST 25, 2022
TESTNET UPDATE: JULY 29, 2022
📝 The HIP-351 text does not yet reflect the name change from RandomGenerate to prng, or the system contract specification. It does explain in detail how prng derives its entropy from the running hash of transaction records generated by the network.
This release also includes some bug fixes and smaller improvements; notably, it:
Permits staking to contract accounts.
MAINNET UPDATE: AUGUST 9, 2022
Any ledger that will grow to billions of entities must have an efficient way to remove expired entities. In the Hedera network, this means keeping a list of NFTs owned by an account, so that when an account expires, we can return its NFTs to their respective treasury accounts.
Under certain conditions in the 0.27.5 release, a bug in the logic maintaining these lists could cause NFT transfers to fail, without refunding fees.
We appreciate the Hedera community working with us on this issue. We invite any users who were affected by this bug to contact support at support@hedera.com.
MAINNET UPDATE: JULY 21, 2022
TESTNET UPDATE: JULY 1, 2022
As wallets and exchanges roll out client support, users will now have the choice to stake their hbar to a node. As nodes accumulate stake, from both individuals and organizations, they will become eligible to pay rewards to their stakers. At this point, once the 0.0.800 account balance has crossed a threshold to be set by the council coin committee, rewards will be permanently activated.
This will set the stage for the second phase of staking, in which a node’s contribution to consensus becomes a direct function of its stake, and community nodes with sufficient stake can begin to participate in consensus. Please note the decentralized nature of this process makes it hard to predict exactly when each milestone and phase will be achieved. The immediately visible consequences of the 0.27 release will be simply,
The consensus nodes handle CryptoCreate and CryptoUpdate transactions with staking elections---even if not all wallets and exchanges are updated to make these elections just yet.
MAINNET UPDATE: JUNE 9, 2022
TESTNET UPDATE: MAY 25, 2022
Approved operators can manage an owner's tokens on their behalf; this is necessary for many consignment use cases with third party brokers/wallets/auctioneers.
Any permissions granted in a contract through approve() or setApprovalForAll() have an equivalent HAPI cryptoApproveAllowance or cryptoDeleteAllowance expression---and this expression is externalized as a HAPI TransactionBody in the record stream. That is, the HIP-376 system contracts expose a subset of the native HAPI operations, only within the EVM.
MAINNET UPDATE: MAY 19, 2022
TESTNET UPDATE: APRIL 26, 2022
TESTNET UPDATE: APRIL 21, 202
MAINNET UPDATE: APRIL 15, 2022
TESTNET UPDATE: APRIL 7, 2022
TESTNET UPDATE: MARCH 31, 2022
TESTNET UPDATE: MARCH 24, 2022
This upgrade also creates two new system accounts 0.0.800 and 0.0.801 that will hold reward funds.
MAINNET UPDATE: MARCH 10, 2022
TESTNET UPDATE: FEBRUARY 17, 2022
MAINNET UPDATE: FEBRUARY 3, 2022
TESTNET UPDATE: JANUARY 20, 2022
Highlights of this release include:
Gas limit per ContractCreate or ContractCall raised to 4M.
Per-contract storage capacity increased to 10MB.
MAINNET UPDATE: JANUARY 13, 2022
TESTNET UPDATE: DECEMBER 21, 2021
The Ethereum network makes heavy use of ECDSA cryptography with the secp256k1 curve, and by supporting these keys we ease the developer experience of migrating a dApp to Hedera. Anywhere a Ed25519 key can be used in the Hedera API, it is now possible to substitute an ECDSA(secp256k1) key.
Meanwhile, our team continues exhaustive due diligence for Smart Contracts 2.0... 🚀
MAINNET UPDATE: DECEMBER 2,2021
TESTNET UPDATE: NOVEMBER 18, 2021
Hedera Services 0.20 is primarily a scaffolding release, as our team is working heads-down to deliver the Smart Contract Service refresh with massive new scale and performance; as well as smart contract integration with native tokens created using the Hedera Token Service. The scope of this refresh is significant, and we believe it will be well worth the wait.
Please also note the following deprecations in the Hedera API protobufs:
MAINNET UPDATE: NOVEMBER 4,2021
TESTNET UPDATE: OCTOBER 28, 2021
TESTNET UPDATE: OCTOBER 21, 2021
MAINNET UPDATE: OCTOBER 7, 2021
In Hedera Services 0.18.1, we have a new scalability profile for NFTs in the Hedera Token Service (HTS). Up to fifty million (50M) NFTs, each with 100 bytes of metadata, may now be minted. Of course our CryptoTransfer and ConsensusSubmitMessage operations are still supported at 10k TPS even with this scale.
In this release, we have also enabled automatic reconnect. This feature comes into play when a network partition causes a node to "fall behind" in the consensus protocol. With reconnect enabled, the node can use a special form of gossip to "catch up" and resume participation in the network with no human intervention. This works even when the node has missed many millions of transactions, and the world state is very different from when it was last active.
Once HIP-23 is fully enabled in release 0.19, when their account receives units or NFT's of a new token type via a CryptoTransfer, the network will automatically create the needed association---no explicit TokenAssociate transaction needed. This supports several interesting use cases; please see the linked HIP-23 for more details.
There are three other points of interest in this release.
First, we have removed the HIP-18 limitations noted in the previous release. The tokenFeeScheduleUpdate transaction has been re-enabled, and multiple royalty fees can now be charged for a non-fungible token type.
Second, the address books in system files 0.0.101 and 0.0.102 will now populate their ServiceEndpoint fields. (However, the deprecated ipAddress, portno, and memo fields will no longer be populated after the next release.)
Third, please note that the TokenService getTokenNftInfos and getAccountNftInfos queries are now deprecated and will be removed in a future release. The best answers to such queries demand historical context that only Mirror Nodes have; so these and related queries will move to mirror REST APIs.
TESTNET UPDATE: SEPTEMBER 23, 2021
Then, when their account receives units or NFT's of a new token type via a CryptoTransfer, the network automatically creates the needed association---no explicit TokenAssociate transaction needed. This supports several interesting use cases; please see the linked HIP-23 for more details.
There are three other points of interest in this release.
First, we have removed the HIP-18 limitations noted in the previous release. The tokenFeeScheduleUpdate transaction has been re-enabled, and multiple royalty fees can now be charged for a non-fungible token type.
Second, the address books in system files 0.0.101 and 0.0.102 will now populate their ServiceEndpoint fields. (However, the deprecated ipAddress, portno, and memo fields will not be no longer be populated after the next release.)
Third, please note that the TokenService getTokenNftInfos and getAccountNftInfos queries are now deprecated and will be removed in a future release. The best answers to such queries demand historical context that only Mirror Nodes have; so these and related queries will move to mirror REST APIs.
Performance Measurement Results:
MAINNET UPDATE: SEPTEMBER 2, 2021
TESTNET UPDATE: AUGUST 30, 2021
Unique token types and minted NFTs are more natural for many use cases than fungible token types. The Hedera Token Service now supports both natively, so that a single CryptoTransfer can perform atomic swaps with any arbitrary combination of fungible, non-fungible, and ℏ transfers. (Please do note that the "paged" getAccountNftInfos and getTokenNftInfos queries will remain disabled until release 0.18.0, as several large performance improvements are pending.)
In this release we have made it possible to denominate a fixed fee in the units of the token to which it is attached (assuming the type of this token is FUNGIBLE_COMMON). Custom fractional fees may now also be set as "net-of-transfer". In this case the recipient(s) in the transfer list receive the stated amounts, and the assessed fee is charged to the sender.
There are a few final points of more specialized interest. First, users of the scheduled transaction facility may now also schedule TokenBurn and TokenMint transactions. Second, network administrators issuing a CryptoUpdate to change the treasury account's key must now sign with the new treasury key. Third, the supported TLS cipher suites have been updated to the following list:
TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 (TLS v1.2)
TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 (TLS v1.2)
TLS_AES_256_GCM_SHA384 (TLS v1.3)
⚠️ There are two temporary limitations to HIP-18 in this release. First, the tokenFeeScheduleUpdate transaction is not currently available. Second, only one royalty fee will be charged for a non-fungible token type. Both limitations will be removed in release 0.18.0.
TESTNET UPDATE: AUGUST 24, 2021
Please see 0.17.4 release notes.
TESTNET UPDATE: AUGUST 19, 2021
Please see 0.17.4 release notes.
MAINNET UPDATE COMPLETED: AUGUST 5, 2021
TESTNET UPDATE COMPLETED: JULY 22, 2021
Hedera tokens can now be created with a schedule of up to 10 custom fees, which are either fixed in units of ℏ or another token; or fractional and computed in the units of the owning token. The ledger automatically charges custom fees to accounts as they send units of a fungible token (or ownership of a NFT, see below) via a CryptoTransfer.
When a custom fee cannot be charged, the CryptoTransfer fails atomically, changing no balances other than for the Hedera network fees.
We are very grateful to the Hedera user community for these interesting and powerful new feature sets.
MAINNET UPDATE COMPLETED: JULY 1, 2021
TESTNET UPDATE COMPLETED: JUNE 17, 2021
In Hedera Services 0.15.1, we improved performance and integrated with the latest Platform SDK to enable full support of network reconnect.
These performance improvements let us augment the Hedera world state with records of all transactions handled in the three minutes of consensus time, even when handling 10,000 transactions per second. The HAPI GetAccountRecords query now returns, from state, all such records for which the queried account was the payer account.
MAINNET UPDATE COMPLETED: JUNE 3, 2021
TESTNET UPDATE COMPLETED: MAY 20, 2021
This release includes notable infrastructure work to enable use of the Platform reconnect feature. Reconnect allows a node that has fallen behind in consensus gossip to catch back up dynamically.
A minor improvement to the Hedera API is that the GetVersionInfo query now includes the optional pre-release version and build metadata fields from the Semantic Versioning spec (if applicable).
To simplify life for system admins who are updating a system account's key, we now waive the signing requirement for the account's new key.
MAINNET UPDATE COMPLETED: MAY 6, 2021
TESTNET UPDATE COMPLETED: APRIL 29, 2021 [v0.13.2]
TESTNET UPDATE COMPLETED: APRIL 22, 2021 [v0.13.0]
Note: The schedule transactions feature will not be enabled in this release; it's expected to be enabled on testnet in a subsequent v0.13.2 update on April 29th. This feature is enabled on previewnet.
The new protobuf avoid this duplication, letting us represent node 0 in a protobuf equivalent of,
However, Services will continue to populate the deprecated fields in duplicate entries for six months, to give all consumers of files 0.0.101 and 0.0.102 time to prepare for exclusive use of the new format. After six months, we will eliminate the duplication and the ipAddress, portno, and memo fields will be left empty. (The fields will never be removed to ensure it remains possible to parse early versions of these system files.)
In a minor point, Services now rejects any protobuf string field whose UTF-8 encoding includes the zero-byte character; that is, Unicode code point 0, NUL. Databases (for example, PostgreSQL) commonly reserve this character as a delimiter in their internal formats, so allowing it to occur in entity fields can make life harder for Mirror Node operators.
To simplify tasks for network admins, we have also streamlined the signing requirements for updates to system accounts, and introduced a Docker-based utility called "yahcli" for admin actions such as updating system files.
MAINNET UPDATE COMPLETED: MARCH 12, 2021
TESTNET UPDATE COMPLETED: FEBRUARY 26, 2021
We have given users of the Hedera Token Service (HTS) more control over the lifecycle of their token associations. In v0.11.0, deleted tokens were immediately dissociated from all accounts. This automatic dissociation no longer occurs. If account X is associated with token Y, then even if token Y is marked for deletion, a getAccountInfo query for X will continue to show the association with Y _until_it is explicitly removed via a tokenDissociateFromAccount transaction. Note that for convenience, queries that return token balances now also return the decimals value for the relevant token. This allows a user to interpret e.g. balance=10050 as 100.50 tokens given decimals=2.
MAINNET UPDATE COMPLETED: FEBRUARY 4, 2021
TESTNET UPDATE COMPLETED: JANUARY 26, 2021
MAINNET UPDATE COMPLETED: JANUARY 7, 2021
TESTNET UPDATE COMPLETED: DECEMBER 17, 2020
Also for HTS, we added a property fees.tokenTransferUsageMultiplier that scales the resource usage assigned to a CryptoTransfer that changes token balances. This scaling factor is expected to be set so that the cost of a CryptoTransfer that changes two token balances is roughly 10x the cost of a CryptoTransfer that changes only two hbar balances.
Apart from HTS, this release drops a restriction on what payer accounts can be used for CryptoUpdate transactions that target system accounts. (That is, accounts with numbers not greater than hedera.numReservedSystemEntities.) In earlier versions, only three payers were accepted: The target account itself, the system admin account, or the treasury account. Other payers resulted in a status of AUTHORIZATION_FAILED. This entire restriction is removed, with one exception---the treasury must pay for a CryptoUpdate targeting the treasury.
Apart from these functional changes, we fixed an unintentional change in the naming of the crypto balances CSV file, and improved the usefulness of clients under test-clients/ for testing reconnect scenarios.
MAINNET UPDATE COMPLETED: DECEMBER 3, 2020
TESTNET UPDATE COMPLETED: NOVEMBER 19, 2020
We made several changes to the HAPI protobuf. First, we removed the deprecated SignatureList message type. Second, we added a top-level signedTransactionBytes field to the Transaction message to ensure deterministic transaction hashes across different client libraries; the top-level bodyBytes and sigMap fields are now deprecated and the already-deprecated body field is removed. Third, we deprecated all fields related to non-payer records, include account send and receive thresholds. This followed from the effective removal of non-payer records in v0.8.1.
For the same reason, the semantics of the CryptoGetRecords and ContractGetRecords queries have also changed. The only queryable records are now those granted to the effective payer of a transaction that was handled while the network property ledger.keepRecordsInState=true. Such records have an expiry of 180 seconds. It is important to note that because a contract account can never be the effective payer for a transaction, any ContractGetRecords query will always return an empty record list, and we have deprecated the query.
MAINNET UPDATE COMPLETED: OCTOBER 22, 2020
TESTNET UPDATE COMPLETED: OCTOBER 7, 2020
The mainnet release includes the 0.8.0 version updates.
TESTNET UPDATE COMPLETED: SEPTEMBER 17, 2020
In Hedera Services v0.8.0, we made several minor fixes and improvements. This tag also includes pre-release implementations of several operations for an incipient Hedera Token Service (HTS).
NOTE: HTS operations will remain disabled in non-development environments for some time. These operations are under active development; please consult master for up-to-date semantics.
Update Receipt proto to pair each Status with NodeID - Receipt is deleted only when the latest (duplicate) transaction expires. getTxRecord API will continue to return ALL records with the transaction ID.
MAINNET UPDATE COMPLETED: SEPTEMBER 8, 2020
TESTNET UPDATE COMPLETED: AUGUST 20, 2020
In Hedera Services v0.7.0, we’ve moved to Swirlds SDK release 0.7.3 which enables zero-stake nodes to be part of a network without affecting consensus. Hedera Services v0.7.0 migrated to new interfaces and methods provided in this version of the Swirlds SDK. HCS topic running hashes are now calculated including the payer account id. The release includes other minor fixes and improvements.
Enhancements
Documentation changes
Bug fixes
MAINNET UPGRADE COMPLETED: AUGUST 6, 2020
TESTNET UPGRADE COMPLETED: JULY 16, 2020
Enhancements
Add support for HCS Topic Fragmentation
Documentation changes
Protobuf v0.6.0 with HAPI doc update to support HCS Topic Fragmentation
MAINNET UPGRADE COMPLETED: JUNE 18, 2020
TESTNET UPGRADE COMPLETED: JUNE 8, 2020
Version 0.5.8 includes a patch which addresses the resilience of peer-to-peer networking in the hashgraph consensus platform.
TESTNET UPGRADE COMPLETED: MAY 5, 2020
In Hedera Services v0.5.0, we’ve added TLS for trusted communication with nodes on the Hedera network. For better security, only TLS v1.2 and v1.3 with TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 and TLS_RSA_WITH_AES_256_GCM_SHA384 cipher suites are allowed.
We’ve added new metadata in the Hedera NodeAddressBook, accessible in system file 0.0.101. The versions of the node software and gRPC Hedera API (HAPI) are now queryable via GetVersionInfo under the new NetworkService for node and network-scoped operations.
For Hedera Consensus Service, we’ve updated the topic running hash calculation to use the SHA-384 hash of the submitted message, rather than the message itself. This reduces the storage requirements needed to validate the hash of a topic. The record of a ConsensusSubmitMessage transaction that uses the new hashing scheme will have a new topicRunningHashVersion field in its receipt. The value of the field will be 2.
Hedera File Service also has several fixes of note. First, we enabled immutable files. Second, we relaxed the signing requirements for a FileDelete transaction to match the semantics of a revocation service. Third, we fixed a fee calculation bug that overcharged certain FileUpdate transactions.
For Hedera Smart Contract Service, we’ve improved visibility into transactions that create child contracts using the new keyword by putting created ids in the record of the transaction; and we now propagate parent contract metadata to created children.
Finally, if you use the throttle properties in system file 0.0.121 to estimate network performance limits, you will also be interested in a new standardized format of those properties. The lists below contain these and other minor updates, bug fixes, and documentation changes.
Enhancements
Add support for TLS
Expand address book metadata
Return all created contract ids
Propagate creator contract metadata
Introduce GetVersionInfo query
Standardize throttle configuration
Enforce file.encoding=utf-8 on startup
Make duration properties inclusive for readability
Bug fixes
Use message SHA-384 hash in running hash
Enable immutable files
Relax FileDelete signing requirements
Fix sbh calculation in FileUpdate
Return metadata for deleted files
Enforce receiver signing requirements during contract execution
Reject invalid CryptoGetInfo
Reject CryptoCreate with empty key
Return NOT_SUPPORTED for state proof queries
Waive fees for 0.0.57 updating 0.0.111
Waive signing requirements for 0.0.55 updating 0.0.121/0.0.122
Waive all fees for 0.0.2
Do not throttle system accounts
Documentation changes
Replace “claim” with “livehash” as appropriate
Standardize and clarify HAPI doc
Software update includes the ability for Hedera to dynamically set throttles on network transaction types.
The following throttles would be updated to: 1000 submit messages per second and 5 topic creates per second.
Reassigning of new Council Member nodes
Say hello to the Hedera Consensus Service! This release is the first to include HCS, allowing verifiable timestamping and ordering of application messages.
Network pricing has been updated to include HCS transactions and queries
Network throttle for HCS set to 1000 tps for submitting messages, and 100 tps for each of the other HCS operations.
Improved end to end testing.
General code clean up and refactoring.
ContractCall - TransactionReceipt response to ContractCall no longer includes the contractID called
CryptoUpdate - TransactionReceipt response to CryptoUpdate no longer includes the accountID updated
CryptoTransfer – CryptoTransfer transactions resulting in INSUFFICIENT_ACCOUNT_BALANCE error no longer list Transfers in the TransactionRecord transferList that were not applied
Java SDK has been updated to support the Hedera Consensus Service
JavaScript/Typescript SDK has reached version 1.0.0, supporting all four mainnet services
JavaScript/Typescript SDK supports both running in the browser (with Envoy Proxy) and in Node.
Go SDK now supports all four mainnet services.
Fees
Transfer list within transaction records now shows only a single net amount in or out for each account, reflecting both transfers and any fees paid.
Fixed bug in fee schedule that had resulted in fees for ContractCallLocal, ContractGetBytecode, and getVersion queries being undercharged by ~33%
The Hedera SDK Extension Components (SXC) is an open sourced set of pre-built components that aim to provide additional functionality over and above HCS to make it easier and quicker to develop applications, particularly if they require secure communications between participants.
Components use the Hedera Java SDK to communicate with the Hedera Consensus Service.
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 . 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 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.
chore: Cherry-Pick (0.56): Increase CryptoGetAccountBalance throttle by in
Full Changelog:
chore: Cherry Pick: Modify and mount default block streams output directory by in
Full Changelog:
fix: correct a missing conversion between AddressBook cert hash hex-string-as-bytes and actual SHA2-384 hash bytes for Node entries. by in
chore: Do stricter validation of X.509 gossip cert in DAB transactions by in
Full Changelog:
test: Added a test to submit DAB transactions for JRS test by in
chore: cover HIP-869 test plan by in
test: Use DAB upgrade test in CI runs by in
ci: continuous integration tests and release initial phase 1 changes by in
perf: increase Health Monitor invocation frequency by in
feat: created iterface for inline PCES writer by in
feat: Add TSS related system transaction and state protobufs (Services) by in
feat: increase version to 0.56 by in
ci: Remove unnecessary check in node-flow-deploy-release-artifact by in
feat: Activate smart contract module 0.51 by in
chore: Add missing config files to previewnet config dir by in
test: Extend HAPI tests for TokenAirdrop with custom fees - royalty fees by in
feat: Added states for TssService by in
chore: remove unnecessary checks for value xfer to system contracts by in
chore: Cleanup Signature by in
chore: Add configuration properties for HIP-904 System Contracts by in
feat: Regenerate keys and update node names for tests by in
feat: Replaced AddressBook based NetworkInfo implementations by in
chore: Address review comments by in
chore: add node details/address book export validation in DabEnabledUpgradeTest by in
fix: Handle non-existent token IDs in token fee schedule updates by in
chore: Add Configuration support for GRPC messages by in
feat: use FileChannel for PCES by in
feat: create inline pces wiring by in
chore: remove nextNodeId from config.txt by in
chore: Make hedera-services also code owner of hedera-app by in
fix(container): adds resiliency to the deterministic image entrypoint script by in
chore: Correct locations of various TSS protos by in
chore: Add constructor for Bytes in Hash to avoid copying by in
fix: Add query handling metrics upload by in
fix: Airdrop transfer list size validation by in
ci: Move jenkins checks into its own workflow that executes when node-zxc-build-release artifact completes by in
ci: Fix invalid workflow introduced by 15928 by in
ci: Add skipped status as possible triggering conclusion by in
ci: ensure prepare xts branch launches when node deploy production build finishes by in
fix: 15959: Add more logging for 12311 by in
chore: remove unused wiring options by in
build(deps): bump actions/upload-artifact from 4.3.1 to 4.4.3 by in
build(deps): bump actions/checkout from 4.1.1 to 4.2.1 by in
ci: Checkout the code with GH_ACCESS_TOKEN and persist the credentials by in
ci: Updated XTS job to check statuses and added gpg key to prepare XTS by in
ci: Update tag scheme in prepare XTS flow by in
ci: Add message parameter to forced tag step by in
fix: support restarting from RECORDS -> BOTH by in
ci: Fix issue with zxf prepare extended test suite by in
fix: ensure configuration loading and name resolution is resilient by in
feat: wire skeleton TssBaseService handlers to submission-enabled AppContext by in
feat: permit unpaid queries when executed from localhost by in
feat: introduce NodeId.of(long) by in
feat: 15154 Added createSnapshot method to State API by in
fix: 15994: Need more logging in AbstractHashListener by in
build(deps): bump org.gradlex:java-module-dependencies from 1.7 to 1.7.1 in /gradle/plugins by in
fix: Ensure getAccountInfo returns correct EVM address by in
chore: Fix compiler warnings in token service by in
test: add block contents validator by in
build: update Java Module patching by in
chore: add links to TSS issues by in
build: generalize publishing setup by in
fix: detect post-upgrade txn in presence of pre-upgrade events by in
fix: update the Schema class import statement by in
fix: stabilize keyRotationDoesNotChangeEvmAddress() by in
feat: updateNode needs both admin key and council to sign. by in
chore: enable BLOCKS-only stream mode by in
test: create fake TSS library for testing by in
chore: Fix ownership of services protobufs by in
feat: Remove default memo for lazy created accounts and auto created accounts by in
chore: use 0s as @RepeatableHapiTest valid start offset by in
fix: DefaultKycStatusCall correct returned values from System Contract by in
chore: Remove hedera-base as code owner by in
chore: use fireAndForget() for freeze period background traffic by in
chore: cherry-pick, Do not update file 102 during the first transaction after a freeze upgrade when DAB is disabled by in
chore: tolerate nextNodeId field in config.txt by in
feat: 14726: Proposal for consensus node architecture update by in
refactor: gossip modules creation by in
ci: Updating workflow permissions as per step-security recommendations. by in
chore: standardize and simplify ScheduleService by in
ci: Enable build promotion tagging and XTS completion by in
feat: Readable and Writable Roster state stores by in
chore: eliminate duplicated signature verification logic by in
test: add test to validate null admin key for contract can still xfer value by in
feat: Add logic for TssMessageHandler for happy path by in
ci: Temporarily disable Trigger ZXF Deploy Integration. by in
feat: HIP-904 Token Airdrop System Contract by in
docs: Provide Design document for HIP-904 System Contracts flows by in
chore: migrate cryptography from .pfx to .pem files by in
ci: Add logic to only delete xts-candidate tag if it already exists by in
ci: Fix ZXCron Promote Build Candidate Checkout Tagged Code step by in
ci: Fix bug with deleting xts-candidate tag prior to creation or use by in
feat: HIP-904 Implement TokenClaimAirdrop System Contract by in
ci: Specify java major minor and patch versions by in
feat: counting get balance throttle by in
feat: HIP-904 Implement Token Cancel Airdrop System Contract by in
feat: align state and records for self managed contract keys on create by in
feat: Update BlockStreamConfig StreamMode default to BOTH by in
chore: replace usages of AddressBook with Roster in tipset by in
chore: Address review comments on PR in protobufs by in
feat: throttled tx metrics by in
feat: Set TSS candidate roster logic by in
chore: schedule 0.56 release branch creation by in
feat: Initial TssVoteHandler by in
made their first contribution in
made their first contribution in
made their first contribution in
Full Changelog:
chore: 16356 cherry pick java version fixes by in
feat: Cherry-Pick (0.55): Define throttle for GetBalance queries by in
Full Changelog:
chore: cherry-pick, do not update file 102 during the first transaction after a freeze upgrade when DAB is disabled by in
Full Changelog:
docs: tss ledger id platform design proposal by in
chore: remove unused hedera-evm-* and cli-clients modules by in
chore: 11771 Added more unit tests for WritablePlatformStateStore by in
test: Token Claim Airdrop with receiverSigReq test by in
chore: rename directory 'swirlds-jasperdb' to 'swirlds-merkledb' by in
chore: remove 'itest' test set by in
fix: code style and javadoc fixes by in
test: add a sigRequired true additional test by in
fix: use ServicesSoftwareVersion by in
fix: if the directory exist, don't create it in UnzipUtility by in
fix: 10342: HashListByteBuffer releases DirectByteBuffers lazily, adds memory pressure by in
feat: 15146 Added calculateHash, setHash and getHash methods to State interface by in
chore: Refactor and Remove Duplicate Documentation in Services by in
fix: stop using raw types in Call{Attempt,Translator} by in
chore: Integrate protobufs to build by in
ci: disable release 0.52 regression by in
chore: Remove the script forensic/start-investigation.py by in
chore: add unit tests for ServicesSoftwareVersion utilities by in
fix: Prevent designating deleted accounts as custom fee collectors by in
chore: Bump services version to 0.55 by in
fix: skip checkSignatures when state.isPcesRound() by in
fix: ensure StakePeriodManager current stake period is always up-to-date by in
feat: HIP-632 alias-to-accounts and back by in
fix: allow absent agreement keys on disk and in state by in
chore: Allow injection of CacheWarmer's Executor by in
fix: complete block -> record translation for all PR checks by in
chore: logging config is automatically reloaded by in
build: update to latest versions - Gradle / Develocity plugin / Dependency Analysis plugin by in
build: add 'timeConsuming' test set by in
fix: Remove HederaFileNumbers and HederaAccountNumbers by in
chore: cleanup exception behavior and add javadocs by in
chore: use correct Nullable annotation in 'smart-contract-service-impl' by in
feat: add PBJ support to platform streams by in
chore: Use GossipEvent in PlatformEvent by in
build: avoid mergeJar / Protobuf gRPC update by in
chore: improve noStakingInteractionsForExtendedPeriodIsFine() spec by in
chore: 15405 move tss to hedera cryptography by in
docs: 15091: Design proposal: migrate Queue states from FCQueue to VirtualMap by in
chore: add StateHashedNotification by in
chore: remove hapiProtoVersion by in
chore: implement and test indirect block proofs by in
fix: set active ExchangeRateSet on triggered txn receipts by in
chore: fix/disable hammer tests that are not working by in
chore: default TransactionExecutor simulator to no-op system contract authorization checks by in
fix: 15385 Used MerkleStateRoot.getReadablePlatformState where possible to prevent race conditions by in
fix: permit 100:1 deflation for upgrade ZIP files by in
feat: BlockStreams-Inversion of control by in
fix: Check for usability in various ops by in
chore: Remove PeerInfo.nodeName by in
refactor: remove AbortException by in
feat: metadata view functions via smart contracts by in
fix: freeze time reset check by in
chore: correct the variable name in roster.proto by in
fix: Precision loss for gas calculation of HTS system contracts v2 by in
feat: introduce PbjRecordHasher and RosterUtils.hash(Roster) by in
feat: Add TokenUpdateNFTs as a smart contract operation v2 by in
chore: remove snapshot ops by in
fix: 15167: Remove timeout from reconnect/rehash Iterators by in
chore: testnet event hashing by in
docs: Proposal Process Update - Specify post-acceptance non-material update procedure by in
fix: recreate block hash from state by in
test: fix CryptographyTests by in
build: cleanup settings.gradle.kts / remove build.gradle.kts by in
fix: 15438: Eliminate busy loop in HalfDiskHashMap.endWriting() by in
docs: tss block signing proposal by in
fix: 15494: Improve VirtualLeafRecord serialization to bytes during flushes by in
feat: migrate event serialization to protobuf by in
fix: Validate CustomFees input arrays in UpdateTokenCustomFeesDecoder by in
chore: Add missing javadocs in Consensus Service by in
chore: add TracerBinding interface for TransactionExecutors. by in
test: unit test verifySyncInvalidEd25519() is not stable by in
test: New HAPI test for TokenAirdrop transaction by in
fix: remove dependencies to 'org.testcontainers' in production code by in
chore: use 4.28.2 for com.google.protobuf artifacts by in
refactor: 15413 Split PlatformStateAccessor into two interfaces by in
feat: decouple event constraints from deserialization by in
feat: add file 101 update during the first transaction after a freeze upgrade by in
docs: Update Tss-Library proposal by in
chore: reduce EthereumTransaction relayer fees by in
chore: Remove ImmutableHash by in
feat: create release branch 0.55 by in
test: (cherry-pick) Added a test to submit DAB transactions for JRS test () by in
ci: cherry pick changes to HAPI version checks into release 0.55 by in
feat: cherry pick smart contract module 051 activation by in
chore: (Cherry Pick) Standardize previewnet config dir with other envs by in
fix: Cherry-Pick: Handle non-existent token IDs in token fee schedule updates by in
fix: Cherry-Pick: Add query handling metrics upload by in
fix: Cherry-Pick (0.55): Airdrop transfer list size validation by in
chore: disable dab in 0.55 by in
fix: (0.55) post-upgrade txn detection in presence of pre-upgrade events by in
made their first contribution in
Full Changelog:
: Token Airdrops and Claims
: Update Token Custom Fee Schedules via Smart Contracts
fix: Cherry-Pick (0.54): Airdrop transfer list size validation by in
Full Changelog:
fix: cherry-pick: remove dependencies to 'org.testcontainers' in production code by in
chore: reducer EthTx relayer fees by in
Full Changelog:
feat: Enable health monitor by in
chore: rename detailed consensus event by in
refactor: Use PBJ EventDescriptor by in
fix: split new Reconnect metrics by NodeId in Grafana by in
perf: VirtualHasher.hash() keeps too many tasks in memory by in
feat: refactor CryptoTransferHandler by in
feat: improve hashing performance by in
test: add test for validating numeric values for HAS and ExchangeRate functions by in
ci: Add registry mirrors to daemon-config on crazy-max/ghaction-setup-docker by in
docs: Update glossary defns of aliases, triplets by in
➡ See the full list of changes .
Enables developers to call functions in a way familiar to and .
feat: add enableDAB flag to enable and disable DAB features by in
ci: resolves release issue preventing the publication of the docker images by in
fix: hedera-evm and hedera-evm-impl are overwriting each other in MC by in
fix: change order of descriptor variables by in
docs: 13690 Added a design doc for Ledger State API by in
chore: update Gradle to 8.8 / setup-gradle to v3.4.2 by in
chore: Cleanup obsolete test-clients code and resources by in
docs: update token reject design doc by in
fix: passing upgrade @HapiTest by in
feat: Ensure overwritten operations check for sufficient gas first by in
test: HIP-904 Create HAPI tests for a hollow account on an alias on which we have a deleted account by in
feat: HIP-904 Charge automatic associations during CryptoTransfer by in
chore: inline pces proposal 2.0 by in
feat: implement HIP-632 isAuthorizedRaw method by in
➡ See the full list of changes .
fix: invalid feeSchedules.json by in
chore(0.52): updates the buildkit and docker daemon configuration to use the registry mirror by in
fix: immediately finalize transfer lists for scheduled crypto transfer by in
ci: fix gradle publish failures in release-0.52 for hedera.com.evm by in
fix: 14489 cherry pick docker rate limit fix in release052 by in
fix(bug): Removed daemon config changes () by in
fix: cherry pick misc fixes by in
feat: extract HederaNetwork interface with initial SubProcessNetwork impl by in
build: make annotation library dependencies transitive by in
chore: Address compiler warnings in LoggerApiSpecAssertions by in
chore: disabled new backpressure via settings by in
chore: Add FakePlatform and FakeServicesRegistry by in
docs: File Service design doc by in
build: (de)activate selection of javac lint features by in
fix(reconnect): use AtomicLong for anticipatedMessages counter by in
feat: Move to fully connected network by in
docs: add design document for HIP-904 token cancel airdrop transaction by in
➡ See the full list of changes .
feat(reconnect): introduce ReconnectMapStats interface by in
chore: revert removal of CLI report tool by in
docs: add design document for HIP-904 token reject operation by in
feat: gossip facade by in
feat: add the ability to disable the running event hasher by in
fix: ignore token expiry status in TokenDissociate by in
feat: add javadoc and diagram, delete dead code by in
fix: use civilian payer for modified variants by in
fix: 12853: Memory leak from MerkleDbDataSource.copyStatisticsFrom() by in
feat: Updated hedera-services code to support DAB protobuf changes. by in
➡ See the full list of changes .
chore: Cherry pick 13648 into release 0.50 branch by in
fix(ci): cherry pick milestone assignee checks rel 50 by in
fix: (cherry-pick) Use restart method to all token schemas by in
fix: Enable tokens.balancesInQueries.enabled by in
chore: Enable tokens.balancesInQueries in code by in
➡ See the full list of changes .
feat: reorganize ISS wiring by in
feat(diff-testing): Script (python) to pull intervals - up to a day - from GCP by in
fix: 11750 Fixed synchronization in BreakableDataSource.saveRecords by in
feat: Differential testing: Enhance account store dumper to handle modular representation by in
test: add security v2 model tests for token associate by in
fix: stop checking for minimum birth round by in
feat: make the state compatible with birth rounds by in
fix: FilteredLoggingMonitor by in
feat: diagram tweaks by in
fix: wait longer for freeze transaction to be handled by in
➡ See the full list of changes .
fix: support crypto admin keys in system contract tokenCreate() by in
fix: remove balance adjustment limit from record in state, use 0 for initial gas snapshot by in
fix: cherry-pick midnight rate management on restart () by in
feat: auto-resubmit operations with modifications () by in
fix: ignore token expiry status in TokenDissociate by in
fix: avoid NPE when migrating from genesis (non-prod) state by in
fix: storage link management by in
fix: manage StakingInfos in restart by in
feat: address cold read issue in ExtCodeHash operation by in
fix: 11348: The fix for 11231 doesn't cover ParsedBucket by in
chore: Create ISS detector component by in
chore: Add orderedSolderTo method to OutputWire by in
chore: remove hashgraph demo by in
➡ See the full list of changes .
fix: remove adjustments limit by in
feat: Check platform status before syncing () by in
chore: cherry-pick unified CryptoCreate throttle reclamation ().
chore: Configure maxAggregateRels to 15 million (all envs) ().
fix: only compare child time created against self-parent time created by in
chore: add an old-style queue thread for intake by in
fix: 11746: Backport the fix for to release 0.47 by in
fix: bug when node is removed by in
fix: Fuzzy matching for CreateOperationSuite and Create2OperationSuite 09431 by in
fix: recordCache to commit added entries and implemented correctly the remove elements from the queue by in
fix: Fix and enable all Schedule HapiTests by in
fix: implement sidecars by in
feat: add setting for birth round ancient threshold by in
chore: drop chatter by in
chore: remove state info by in
chore: Rename contract causing services regression due to long name by in
fix: state leak by in
➡ See the full list of changes .
chore: bump HAPI proto version by in
fix: Ensure that the pending creation customizer applies to the address being created by in
chore: bump HAPI proto version by in
feat: wiring diagram improvements by in
chore: Change HashMap to LinkedHashMap in custom fees assessment by in
feat: add implementation in throttling facility to handle N-Of-Unscaled type of throttling by in
build: do not publish test fixtures by in
build: patch everything we use to be a real Java Module by in
chore!: More common tests moved to correct module by in
feat: Config constants created & used by in
feat: script for cleaning build files by in
fix: Compact last PCES file at boot time by in
feat: sync++- by in
➡ See the full list of changes .
fix: Added a feature flag which is by default enabled to disable tokenBalances and tokenRelationships in getAccountInfo, getAccountBalance and getContractInfo queries.
Populate evm function result on failing eth transaction by in
Disable compression. by in
Fix tests in unique token management spec by in
enaled one more test and remove the other one that not really in use by in
Enable tests from CannotDeleteSystemEntitiesSuite by in
Fix tests in ContractBurnHTSSuite by in
Tune dependency scopes by in
unneeded calls to swirlds-common removed by in
Fixed CryptoRecordsSanityCheckSuite by in
Enable test from AssociatePrecompileSuite by in
Enforce NFT allowance check on auto-creation by in
Catch UncheckedIOException during PCES file copy. () by in
Fix PCES copy bugs. ()
Re-add bootstrap.properties file to maintain downstream processes and increase accounts.maxNumber=20_000_000
8815: sort dirty leaves during flush
Add setting to disable critical quorum.
Add a doc for all system entity numbers
08566 - Validate PCES Events When Loading State On Different Network
Differential testing analytic engine: State file file dumper now dumps special files
Added improved startup ASCII art.
Characterize invalid id failure modes for classic HTS calls
Add ordinals to status diagram, and update javadocs
5552: Create a Grafana Data Dashboard to view all existing relevant data metrics
Update Besu to version 23.10.0
➡ See the full list of changes .
HIP-786 ()
Update Besu to 23.10.0 - cherry pick ()
Update the Besu EVM library to version 23.7.2 ()
"Productizing" contract disassembler at last ()
Auto sidecar validations ()
Create fat jar with services CLI so it can be run standalone ()
Upgrade platform SDK ()
0.42 account balance test ()
Re-add bootstrap.properties file and increase accounts.maxNumber=20_000_000 ()
Chore: normalize configuration values (release/0.42) ()
8751: No data source metrics for accounts, NFTs, or token rels ()
Add EIP 2930 support to EthTXData ()
Provide entity and throttle dashboards ()
07748 Postconsensus signature gathering ()
Enable EIP-2930 transactions by default ()
7570: Remove JasperDB ()
Remove support for legacy sync gossip. ()
Disable account balance exports ()
Modify config to support state on disk by default ()
Ethereum transaction type support is expanded to include type 1 transactions () which follow EIP 2930 RLP encoding. This increases the number of native EVM tools and scenarios the Hedera Smart Contract Service supports.
NFT mint pricing is changed to linearly scale based on number of serials minted. Also, minting a single NFT in collection is changed to cost $0.02 from $0.05.
The 0.40 release of Hedera Services delivers . Smart contract developers using the Hedera public mirror node can now track contract nonces as they would on e.g., Ethereum. Use cases might include troubleshooting failed contract calls or writing unit tests that validate transaction ordering based on CREATE1 addresses (once these are set by default in release 0.41+).
Open source contributors to the project will notice major refinements in the Gradle build, thanks to 's expert touch.
VirtualRootNode constructor creates a cache object that doesn't get reused
Implement blocklisting of EVM addresses
Optimize virtual node cache flush strategy
HIP-721: 06026 - add software version to events
Implement CryptoCreate handle method
UtilPrng handle Implementation
Add a PCLI sub command to sign services stream files
Implement token freeze handling
Implement token unfreeze handle()
Combine Admin and Network modules
Implement the modular Pre-Handle Workflow
Move hashes out of leaves node in VirtualMap
TokenFeeScheduleUpdate handle() implementation
Basic File service implementation
Implement Token Association to Account
Implementation of handle workflow
Implement the modular record cache
CryptoDelete handle implementation
Upgrade EVM to Shanghai
EVM version update and optimizations
Turn on the Shanghai version of the EVM in previewnet
Update hedera-protobufs-java version to 0.38.10
Add PCLI command to sign account balance files
Implement topic deletion prehandle ()
Generalize workflows enabled and add workflow ports ()
Pre-handle improvements ()
Support auto-scheduling operations by type within a suite ()
Add SPI and App components supporting TransactionDispatcher for modularized HCS ()
added the missing functionality to FileSignTool ()
Consensus Message Submission Prehandle ()
Add IngestChecker mono adapters for sigs and solvency ()
[HIP-583] Finalize hollow accounts via any required signature in a txn ()
Remove CryptoCreate capability to create hollow accounts ()
Populate EVM Address in CryptoTranscation ()
Enable All EVM E2E suites to run with Ethereum Calls ()
Add tracking of property changes for hollow account completion ()
Adding support for Redirect Token Calls fro evm-module ()
Update FileSignTool ()
Adding block number tool ()
Add client.workflow.operations and test with workflows ()
to expand alias support in CryptoCreate & CryptoTransfer Transactions.
Services v0.34.0 completes the implementation of .
for making payer of the CryptoTransfer sponsor for auto-creation. It also enables auto-creation with Token transfers in addition to Hbar transfers.
for allowing zero unit fungible token transfers
for enabling token creators an option to exempt all of their token’s fee collectors from a custom fee.
Adds support of the ERC20/721 transferFrom method for HTS precompiles from .
Services 0.30 completes the for making Hedera native tokens manageable via smart contracts. There are five new system contracts: getTokenExpiryInfo(address), updateTokenExpiryInfo(address, Expiry), isToken(address token), getTokenType(address token), and updateTokenInfo(address, HederaToken).
⚠️ Contract authors should know this release initiates Hedera's . There will be two visible effects immediately after the 0.30 upgrade:
Mirror node operators will be able to use the daily NodeStakeUpdate export to track the current values of . Please review the linked protobuf comments for more details on these properties.
In Services 0.29 we have followed the to give contract authors many new ways to inspect and manage HTS tokens.
will be enabled on testnet and mainnet in this release.
Please note this that will change how clients fetch token associations and balances after the November release in this year. At that time, mirror nodes will become the exclusive source of token association metadata. This is because made token associations unlimited, so in the long run it will not be efficient for consensus nodes to serve this information.
Services 0.28 gives Hedera devs a new dApp building block in . HAPI has a new with a prng transaction that generates a record with either a pseudorandom 48-byte seed, or an integer in a requested range.
Smart contracts can also get pseudorandom values by calling a new system contract at address 0x169, using the interface as in . Applications might include NFT mint contracts, lotteries, and so on.
Extends to the ERC-20 and ERC-721 functions allowance, getApproved, and isApprovedForAll.
The 0.27 release of Hedera Services initiates the first phase of . We deeply appreciate the community’s feedback on this critical feature!
Observant readers might recall that an earlier of Services 0.27 also enabled . This is a complex feature with some deep implications, and we have decided to defer for one more release before going to production.
In this release, we are excited to deploy support for . and .
HIP-410 adds a HAPI EthereumTransaction by which an account that was with an can submit Ethereum transactions to Hedera by signing with its ECDSA key. (Standard Ethereum restrictions on the sender's nonce apply.) Please see HIP-410 for details, including a summary of some very compelling use cases that the EthereumTransaction enables---for example, "I want to use MetaMask to create a transaction to transfer HBAR to another account".
HIP-415 also anticipates such use cases by standardizing the concept of a Hedera "block"; this is important for a full implementation of the . The definition is simple: One block is all the transactions in a record stream file. The block hash is the 32-byte prefix of the transaction running hash at the end of the file. And the block number is the index of the record file in the full stream history, where the first file had index 0.
Hedera Services 0.26 implements , allowing smart contract developers to use the familiar and "operator approval" with both fungible and non-fungible HTS tokens.
The Hedera Services 0.25 release brings good news for HTS users who manage large numbers of token types, as it delivers . In particular, a single account can now serve as treasury for any number of token types. (Please do note the CryptoService HAPI queries still return information for only an account’s 1000 most recently associated tokens; mirror nodes remain the best source for full history.)
We are also very excited to announce support for . This HIP supercharges contract integration, making it possible for a smart contract to create a new HTS token---fungible or non-fungible, with or without custom fees. (An interested Solidity developer might consult the examples in .)
In a harbinger of , this release will also enable . Token owners can now approve other accounts to manage their HTS tokens or NFTs, in direct analogy to the approve() and transferFrom() mechanisms in ERC-20 and ERC-721 style tokens.
HIP-336 implementation
HIP-358 implementation
HIP-367 implementation
ERC view functions now usable in ContractCallLocalQuery
In the 0.24 release of Hedera Services, we are excited to give smart contract developers a new level of interoperability with native Hedera Token Service (HTS) tokens via . The Hedera EVM now exposes every HTS fungible token as an ERC-20 token at the address of the token’s 0.0.X entity id; and analogously, every HTS non-fungible token appears as an ERC-721 token. This means a smart contract can look up its balance of a fungible HTS token; or change its behavior based on the owner of a particular HTS NFT. Please see the linked HIP for full details.
One change to the Hedera API (HAPI) is that we now have enough evidence to conclude the experimental getAccountNftInfos and getTokenNftInfos queries do not have a favorable cost/benefit ratio, and these queries are now .
Hedera Services 0.23 fleshes out our smart contract service via the implementation of . Smart contract developers are now free to use the CREATE2 EVM opcode. A typical use case is a distributed exchange that wants its pair contracts to have deterministic addresses based on the tokens in the pair.
Please note two issues fixed in this release. , in release 0.22, the nodes returned the bytes ledger_id stipulated by as a UTF-8 encoding of a hex string. The returned bytes are now the big-endian representation of the ledger's numeric id. , prior to this release, the record of a dissociateToken from a deleted token did not list the discarded balance of the dissociated account if the token's treasury was missing. This is now fixed.
The 0.22 release is a paradigm shift for Hedera Services, as we deliver the next major step in our Smart Contracts 2.0 roadmap on the strength of the protean , a technical foundation for scaling the world state of our ledger to billions of entities without sacrificing the high TPS enabled by the hashgraph consensus algorithm.
Network EVM capacity increased to 15M gas-per-second. (Please see for details.)
Solidity integration with native HTS tokens. (Please see for details.)
We expect more progress in these directions over the coming releases. Do note that the gas usage of the HTS integrations is still evolving; follow to track the finalized gas charges leading up to mainnet release.
There are two other HIP's included in this release not related to the smart contract service. First, enhances queries like CryptoGetInfo with a ledger id that marks which Hedera network answered the query. Second, allows a client to include the expected decimals for a token in a CryptoTransfer. This means a hardware wallet can guarantee its token transactions will have the precision seen by the user in the device display.
While we are gaining momentum in our smart contracts roadmap, we are also deeply committed to improving the developer experience, and welcome issues and ideas in our and !
In Hedera Services 0.21 we are pleased to announce support for and .
Auto-account creation lets a new user receive ℏ via a CryptoTransfer without having already created an 0.0.X id on the network. The new user only needs to provide their public key, and when a sponsor account sends ℏ "to" their key via a new , the network automatically creates an account with their key. Additional transfers to and from an auto-created account may also use its alias instead of the account id.
An alias may also be used to get the account balance and account info for the account. (Do note there is a that causes the getAccountInfo query response to echo back the account alias instead of its 0.0.<num> id; this will be fixed in the next release. Please use the free getAccountBalance query to check the 0.0.<num> id that corresponds to an alias.) You will be able to use the alias in all other transactions and queries in a future release.
The main deliverables in this release are improved automation for node operators to use in software upgrades; and a handful of minor bug fixes, including for .
The , which is redundant given the existence of the .
The , as this limit is now simply a side-effect of the given gas limit.
In Hedera Services 0.19, we are thrilled to announce migration of the Hedera smart contract service to the Hyperledger Besu EVM, as laid out in . This enables support for the latest v0.8.9 Solidity contracts, and harmonizes our gas schedule with that of the “London” hard fork. The Besu migration also sets the stage for a step change in smart contract performance on Hedera.
Two other HIPs targeting the Hedera Token Service go live in this release. First, the feature set is now enabled, so that any account that has been configured with a non-zero maxAutoAssociations can receive air-drops (i.e., units or NFTs of a token type without explicit association). Second, we have also implemented , which provides a safety measure for token types created with a pauseKey. If a TokenPause is submitted with this key’s signature, then all operations on the token will be suspended until a subsequent TokenUnpause.
We are happy to also announce that accounts can be customized to take advantage of the upcoming feature set. That is, an account owner can now "pre-pay" for token associations via a or transaction, without knowing in advance which specific token types they will use.
Developers will likely appreciate two other release 0.18.1 items. First, we have migrated to for dependency injection. Second, there is a new getExecutionTime query in the that supports granular performance testing in development environments.
In Hedera Services 0.18.0, we are happy to announce support for . This feature lets an Hedera account owner "pre-pay" for token associations via a or transaction, without knowing in advance which specific token types they will use.
Developers will likely appreciate two other release 0.18.0 items. First, we have migrated to for dependency injection. Second, there is a new getExecutionTime query in the that supports granular performance testing in development environments.
In Hedera Services 0.17.2, we are excited to announce support for , with a complementary extension to that lets an NFT creator set a royalty fee to be charged when fungible value is exchanged for one of their creations.
In Hedera Services 0.16.0, we are excited to announce support for .
The five case studies in show the basics of how custom fees are charged, and how they appear in records. Note that at most two "levels" of custom HTS fees are allowed, and custom fee-charging cannot require changing more than 20 account balances.
⚠️ There is one variation on custom fees that requires a work-around in this release. Specifically, if a fixed fee should be collected in the units of the "parent" token to whose schedule it belongs, then in Release 0.16.0 this must be accomplished using a FractionalFee as described in . In Release 0.17.0 the more natural FixedFee configuration will be available.
In this release, we have also enabled previewnet support for . Unique token types and minted NFTs are more natural for many use cases than fungible token types. The Hedera Token Service will soon support both natively, so that a single CryptoTransfer can perform atomic swaps with any arbitrary combination of fungible, non-fungible, and ℏ transfers.
We have also finalized the design for the non-fungible token (NFT) support to be added to the Hedera Token Service (HTS) in release 0.16.0. The protobufs for new HAPI operations are available in the 0.15.0 tag of the GitHub repository.
To simplify fee calculations, there is now a maximum entity lifetime of a century for any entity whose lifetime is not _already_ constrained by the maximum auto-renew period. A HAPI transaction that tries to set an expiration further than a century from the current consensus time will resolve to INVALID_EXPIRATION_TIME.
In Hedera Services 0.14.0, we have implemented account auto-renewal according to the specifications of . This feature will not be enabled until a later date, after ensuring universal awareness of its impact in the user community.
In Hedera Services v0.13.0, we have schedule transactions. The new design gives collaborating nodes a well-defined workflow if they happen to schedule identical transactions, even if they are using different gRPC client libraries (for example, Go and JavaScript). The new design also reduces the number of signatures required to submit a valid ScheduleSign transaction in many common use cases. Users will be able to schedule CryptoTransfer and ConsensusSubmitMessage transactions in this release. Other transaction types will be introduced in future releases.
This release deprecates three fields in the for system files 0.0.101 and 0.0.102. The three deprecated fields are ipAddress, portno, and memo. When we rely on these fields, we cannot concisely represent node with multiple IP addresses. For example, take mainnet node 0 (account 0.0.3), which as of this writing has proxy IPs 13.82.40.153, 34.239.82.6, and 35.237.200.180. The mainnet 0.0.101 file must include a NodeAddress entry for each proxy, which means duplicating fields like nodeCertHash.
In Hedera Services v0.12.0, we completed the MVP implementation of the Hedera Scheduled Transaction Service (HSTS) as detailed in design document. This service decouples what should execute on the ledger from when it should execute, giving new flexibility and programmability to users. Note that HSTS operations are enabled on Previewnet, but remain disabled on Testnet and Mainnet at this time.
In a final Hedera API (HAPI) change, we have extended the memo field present on contract and topic entities to the account, file, token, and scheduled transaction entities. (Note this memo is distinct from the short-lived memo that may be given to any TransactionBodyfor inclusion in the TransactionRecord.) All of these changes to HAPI are now more easily browsed via GitHub pages ; the new is now the authoritative source of the protobuf files defining HAPI.
Apart from these enhancements to HAPI, the "streams" consumable by mirror node operators now include an alpha version of a protobuf file that contains the same information as the _Balances.csv files. The type of this file is .
In Hedera Services v0.11.0, we upgraded the record stream format from v2 to v5 and the event stream format from v3 to v5. These changes are described in detail in the "Record and Event Stream File Formats" .
We also updated startup code to make the number of system accounts in development and pre-production networks match the number of system accounts on mainnet, account numbers 900-1000 on startup if they do not exist.
In Hedera Services v0.10.0, we improved the usability of the Hedera Token Service (HTS) with a newTotalSupply field in the receipts of TokenMint and TokenBurn transactions. Without this field, a client must follow the entire record stream of a token's supply changes to be certain of its supply at the consensus timestamp in the receipt. (Note that HTS operations are now enabled on Previewnet and Testnet, but remain disabled on Mainnet at this time. Please consult the for HTS semantics.)
In Hedera Services v0.9.0, we finished the alpha implementation of the Hedera Token Service (HTS). Note that all HTS operations are enabled on Previewnet, but remain disabled on Testnet and Mainnet. Please consult the for HTS semantics.
Deprecated fields related to threshold records in HAPI protobuf
First drafts of tokenCreate, tokenUpdate, tokenDelete, tokenTransfer, tokenFreeze, tokenUnfreeze, tokenGrantKyc, tokenRevokeYc, tokenWipe, and getTokenInfo HAPI operations. and
Migrate to Swirlds SDK release 0.7.3 with appropriate settings and logging configurations ,
Update HCS topic running hash to include the payer account id
Add zero-stake node functionality
Add new stats for the average size of HCS submit message transactions that got handled and for counting the number of platform transactions not created per second ,
Change gRPC CipherSuite to be CNSA compliant
Make recordLogPeriod dynamic with a default of 2 seconds
Add record with 3-min expiry to effective payer account after handling transaction
Enhancements for going open source ,
Clarify interpretation of response codes UNKNOWN and PLATFORM_TRANSACTION_NOT_CREATED ,
Prevent CryptoCreate and CryptoUpdate transactions from giving an account an empty key ,
Fix incorrect submitted smart contract transactions count
Validate total ledger balance before starting up Services
Add a new rolling file to log all queries with controlled maximum rate
Other minor bugs
In Hedera Services v0.6.0, we’ve enhanced the Hedera Consensus Service by supporting . We added, into the ConsensusSubmitMessageTransactionBody, an optional field for the current chunk information. For every chunk, the payer account that is part of the initialTransactionID must match the Payer Account of this transaction. The entire initialTransactionID should match the transactionID of the first chunk, but this is not checked or enforced by Hedera except when the chunk number is 1.
v0.5.8 includes all of the updates found in
You may get more information regarding transaction record fees .
Learn more about Hedera SXC .
Build version.0 -
Build version.1 -
Build version.2 -
Build version.3 -
Build version.4 -
Build version.5 -
