Hedera Services 0.23 fleshes out our smart contract service via implementation of HIP-329 (Support CREATE2 opcode). 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. First, in release 0.22, the nodes returned the bytes ledger_id stipulated by HIP-33 as a UTF-8 encoding of a hex string. The returned bytes are now the big-endian representation of the ledger's numeric id. Second, 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.
Contributors
We'd like to thank all the contributors who worked on this release!