Releases: hashgraph/hedera-services
Hedera Services v0.9.0
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 SDK documentation for HTS semantics.
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; 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.
Enhancements
- Complete alpha implementation of HTS, e.g. #646 #703 #751
- Ensure deterministic transaction hashes via the
Transaction#signedTransactionBytesfield #611 - Drop some artificial constraints on the form of a
CryptoTransferused for a query payment #581
Deprecations
- Remove all code involved with non-payer records; deprecate all associated protobuf elements #548
Bug fixes
- Consolidate fees for variable-size transaction records to ensure the payer's max
transactionFeeis respected #502 - Fix issues with pre-alpha HTS implementation, e.g. #698
Contributors
We'd like to thank all the contributors who worked on this release!
Hedera Services v0.9.0
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 SDK documentation for HTS semantics.
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; 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.
Enhancements
- Complete alpha implementation of HTS, e.g. #646 #703 #751
- Ensure deterministic transaction hashes via the
Transaction#signedTransactionBytesfield #611 - Drop some artificial constraints on the form of a
CryptoTransferused for a query payment #581
Deprecations
- Remove all code involved with non-payer records; deprecate all associated protobuf elements #548
Bug fixes
- Consolidate fees for variable-size transaction records to ensure the payer's max
transactionFeeis respected #502 - Fix issues with pre-alpha HTS implementation, e.g. #698
Contributors
We'd like to thank all the contributors who worked on this release!
Hedera Services v0.9.0
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 SDK documentation for HTS semantics.
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; 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.
Enhancements
- Complete alpha implementation of HTS, e.g. #646 #703 #751
- Ensure deterministic transaction hashes via the
Transaction#signedTransactionBytesfield #611 - Drop some artificial constraints on the form of a
CryptoTransferused for a query payment #581
Deprecations
- Remove all code involved with non-payer records; deprecate all associated protobuf elements #548
Bug fixes
- Consolidate fees for variable-size transaction records to ensure the payer's max
transactionFeeis respected #502 - Fix issues with pre-alpha HTS implementation, e.g. #698
Contributors
We'd like to thank all the contributors who worked on this release!
Hedera Services v0.8.0
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.
Enhancements
- Deprecated fields related to threshold records in HAPI protobuf #506
- Update Receipt proto to pair each Status with NodeID - Receipt is deleted only when the latest (duplicate) transaction expires.
getTxRecordAPI will continue to return ALL records with the transaction ID. - First drafts of
tokenCreate,tokenUpdate,tokenDelete,tokenTransfer,tokenFreeze,tokenUnfreeze,tokenGrantKyc,tokenRevokeYc,tokenWipe, andgetTokenInfoHAPI operations. #505 and #522
Documentation changes
- None
Bug fixes
- None
Contributors
We'd like to thank all the contributors who worked on this release!
Hedera Services v0.8.0
In Hedera Services v0.8.0, Hedera Services v0.8.0 includes minor fixes and improvements listed below:
Enhancements
- Deprecated fields related to threshold records in HAPI protobuf #506
- Update Receipt proto to pair each Status with NodeID - Receipt is deleted only when the latest (duplicate) transaction expires.
getTxRecordAPI will continue to return ALL records with the transaction ID.
Documentation changes
- None
Bug fixes
- None
Contributors
We'd like to thank all the contributors who worked on this release!
Hedera Services v0.8.0
In Hedera Services v0.8.0, Hedera Services v0.8.0 includes minor fixes and improvements listed below:
Enhancements
- Deprecated fields related to threshold records in HAPI protobuf #506
- Update Receipt proto to pair each Status with NodeID - Receipt is deleted only when the latest (duplicate) transaction expires.
getTxRecordAPI will continue to return ALL records with the transaction ID.
Documentation changes
- None
Bug fixes
- None
Contributors
We'd like to thank all the contributors who worked on this release!
Hedera Services v0.8.0
v0.8.0-alpha2 Second preliminary release candidate for Services
Hedera Services v0.7.0
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
- Migrate to Swirlds SDK release
0.7.3with appropriate settings and logging configurations #347, #427 - Update HCS topic running hash to include the payer account id #88
- Add zero-stake node functionality #274
- 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 #316, #334
- Change gRPC CipherSuite to be CNSA compliant #215
- Make recordLogPeriod dynamic with a default of 2 seconds #315
- Add record with 3-min expiry to effective payer account after handling transaction #348
- Enhancements for going open source #378, #379
Documentation changes
Bug fixes
- Prevent
CryptoCreateandCryptoUpdatetransactions from giving an account an empty key #58, #60 - Fix incorrect submitted smart contract transactions count #371
- Validate total ledger balance before starting up Services #258
- Add a new rolling file to log all queries with controlled maximum rate #59
- Other minor bugs #373
Contributors
We'd like to thank all the contributors who worked on this release!
Hedera Services v0.7.0
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
- Migrate to Swirlds SDK release
0.7.3with appropriate settings and logging configurations #347, #427 - Update HCS topic running hash to include the payer account id #88
- Add zero-stake node functionality #274
- 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 #316, #334
- Change gRPC CipherSuite to be CNSA compliant #215
- Make recordLogPeriod dynamic with a default of 2 seconds #315
- Add record with 3-min expiry to effective payer account after handling transaction #348
- Enhancements for going open source #378, #379
Documentation changes
Bug fixes
- Prevent
CryptoCreateandCryptoUpdatetransactions from giving an account an empty key #58, #60 - Fix incorrect submitted smart contract transactions count #371
- Validate total ledger balance before starting up Services #258
- Add a new rolling file to log all queries with controlled maximum rate #59
- Other minor bugs #373
Contributors
We'd like to thank all the contributors who worked on this release!
Hedera Services v0.7.0
In Hedera Services v0.7.0, we’ve moved to Swirlds SDK release 0.7.2 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
- Migrate to Swirlds SDK release
0.7.2with appropriate settings and logging configurations #347, #427 - Update HCS topic running hash to include the payer account id #88
- Add zero-stake node functionality #274
- 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 #316, #334
- Change gRPC CipherSuite to be CNSA compliant #215
- Make recordLogPeriod dynamic with a default of 2 seconds #315
- Add record with 3-min expiry to effective payer account after handling transaction #348
- Enhancements for going open source #378, #379
Documentation changes
Bug fixes
- Prevent
CryptoCreateandCryptoUpdatetransactions from giving an account an empty key #58, #60 - Fix incorrect submitted smart contract transactions count #371
- Validate total ledger balance before starting up Services #258
- Add a new rolling file to log all queries with controlled maximum rate #59
- Other minor bugs #373
Contributors
We'd like to thank all the contributors who worked on this release!