The Hedera testnet has been upgraded to v0.9.0 — the release notes for the v0.9.0 upgrade can be found in the official Hedera documentation. Although the Hedera Token Service is currently available on the Hedera previewnet in early access with limited functionality; it is not yet available on the Hedera testnet.
Found below is information about changes to the Hedera API (HAPI), new fields in the v0.9.0 transaction proto, new REST APIs for the Hedera mirror node, release of v2 of the official Hedera SDKs, and an update to the Hedera mainnet.
Changes to Hedera API 0.9.0
The Transaction proto will have the following deprecated fields removed. They have been marked as deprecated previously.
- TransactionBody body = 1
- SignatureList sigs = 2
The signedTransactionBytes field will be added. If the appropriate updates are not made, transactions will fail with INVALID_TRANSACTION_BODY or INVALID_SIGNATURE response from the network. You can view the updated transaction proto here and issue here.
New fields in transaction proto (v0.9.0)
Release v0.9.0 will be introducing a new field to transaction proto. The addition of the signedTransactionBytes field to the Transaction protobuf message is designed to ensure that the hash of the entire transaction (including signatures) as calculated by the client and the network is guaranteed to be identical. The new field stores the entire signed transaction including signatures as an array of bytes.
- signedTransactionBytes = 5
This change is a backwards compatible change, so clients that currently use the bodyBytes & sigMap to submit transactions can continue to do so, with the node parsing and hashing the transaction as it currently does.
A transaction can only contain signedTransactionBytes or contain bodyBytes & sigMap. A transaction that contains any other combination of fields will be rejected with an INVALID_TRANSACTION response from the network.
You can view the updated transaction proto here.