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 #29
- Expand address book metadata #30
- Return all created contract ids #31
- Propagate creator contract metadata #31
- Introduce GetVersionInfo query #32
- Standardize throttle configuration #33
- Enforce file.encoding=utf-8 on startup #34
- Make duration properties inclusive for readability #35
Bug fixes
- Use message SHA-384 hash in running hash #36
- Enable immutable files #37
- Relax FileDelete signing requirements #38
- Fix sbh calculation in FileUpdate #39
- Return metadata for deleted files #40
- Enforce receiver signing requirements during contract execution #41
- Reject invalid CryptoGetInfo #42
- Reject CryptoCreate with empty key #43
- Return NOT_SUPPORTED for state proof queries
- Waive fees for 0.0.57 updating 0.0.111 #44
- Waive signing requirements for 0.0.55 updating 0.0.121/0.0.122 #45
- Waive all fees for 0.0.2 #46
- Do not throttle system accounts #47