v0.59.0 #4010
steven-sheehy
started this conversation in
Releases
v0.59.0
#4010
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
The previous release saw support for the persistence of HIP-406 staking-related data. Staking persistence saw further fine-tuning in this release to adapt to changes in the
NodeStakeUpdateTransactionprotobuf. Thedecline_reward,staked_account_id,staked_node_idfields were added to/api/v1/accountsand/api/v1/accounts/{id}to show account-level staking properties. We also added staking related fields to the existing/api/v1/network/nodesREST API (see example below).GET /api/v1/network/nodes{ "nodes": [ { "description": "address book 1", "file_id": "0.0.102", "max_stake": 50000, "memo": "0.0.4", "min_stake": 1000, "node_account_id": "0.0.4", "node_cert_hash": "0x01d...", "node_id": 1, "public_key": "0x4a...", "service_endpoints": [], "stake": 20000, "stake_not_rewarded": 19900, "stake_rewarded": 100, "stake_total": 100000, "staking_period": { "from": "1655164800.000000000", "to": "1655251200.000000000" }, "timestamp": { "from": "16552512001.000000000", "to": null } } ], "links": { "next": null } }Support for the new record file v6 format as defined in HIP-435 was added in this release. Record file v6 adds block number as well as support for the new sidecar record files that carry detailed contract traceability information that mirror nodes can optionally choose to download. The record and signature files are now in a more maintainable protobuf format that should make them easier to enhance with new fields in the future without requiring breaking changes. Also, the v6 record files will now be compressed which should translate into reduced network and storage costs while potentially improving performance. Once v6 is enabled in a future hedera-service's release, mirror node operators will be required to update to a version that supports the new v6 format to avoid downtime.
Rosetta saw a number of improvements this release to better align it with the Rosetta specification. A configurable valid duration seconds option was added to the transaction construction API to support customization of this value. Support for a consistent block number regardless of
startDatewas added in Rosetta now that Hedera has a consistent block as defined in HIP-415. A0xprefix was added to alias addresses returned via the API to denote that the data is hex-encoded.Enhancements
Bug Fixes
Dependency Upgrades
@hashgraph/proto from 2.4.2 to 2.5.0 in /hedera-mirror-rest/check-state-proof #3903@hashgraph/proto from 2.4.2 to 2.5.0 in /hedera-mirror-rest #3895Contributors
We'd like to thank all the contributors who worked on this release!
This discussion was created from the release v0.59.0.
Beta Was this translation helpful? Give feedback.
All reactions