v0.67.0 #4741
steven-sheehy
started this conversation in
Releases
v0.67.0
#4741
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
HIP-367 deprecated the list of token balances for an account returned via HAPI. The mirror node has been working on its replacement for a few releases by storing the current account balance, combining contract and entity tables, and adding a history table for
token_account. This work has paved the way for a new token relationships REST API that will list all fungible and non-fungible tokens associated with a particular account. This API also returns some metadata like balance, KYC status, freeze status, and whether it's an automatic association or not. Currently the fungible token balance being returned is from the 15 minute account balance file. We are actively working towards tracking the real-time fungible token balance and it will be updated to reflect that in a future release.GET /api/v1/accounts/{id}/tokens{ "tokens": [{ "automatic_association": true, "balance": 15, "created_timestamp": "1234567890.000000002", "freeze_status": "UNFROZEN", "kyc_status": "GRANTED", "token_id": "0.0.1135" }], "links": { "next": null } }HIP-513 details how smart contract traceability information from consensus nodes is made available via sidecar files. The contract state changes within the sidecar are persisted by mirror nodes and made available on the contract results APIs. However, these state changes do not always reflect the full list of smart contract storage values since not all slots are modified during any particular contract invocation. We now persist a rolled up view of state changes to track the latest slot key/value pairs. This contract state information is now exposed via a new
/api/v1/contracts/{id}/stateREST API whereidis either theshard.realm.num,realm.num,num, or a hex encoded EVM address of the smart contract.GET /api/v1/contracts/{id}/state{ "state": [{ "address": "0x0000000000000000000000000000000000001f41", "contract_id": "0.0.100", "slot": "0x0000000000000000000000000000000000000000000000000000000000000001", "timestamp": "1676540001.234390005", "value": "0x0000000000000000000000000000000000000000000000000000000000000010" }], "links": { "next": null } }In a push for further decentralization, we now randomize node used to download data files after reaching consensus. Previously, the data structure we used generally caused us to use the first node returned in the verified list, which was usually
0.0.3. We now randomly pick a node until we can successfully download the stream file. We also internally changed all tables that used node account ID to use its node ID instead.On the testing front, we enhanced various test and monitoring tools to add support for new APIs. We also added an acceptance test startup probe to delay the start of the tests until the network as a whole was healthy. This avoids the mirror node acceptance tests reporting a false positive when a long migration or startup process on the consensus or mirror nodes causes a delay.
Enhancements
hedera-evm-apidependency tohedera-mirror-web3module #4650Bug Fixes
Documentation
Dependency Upgrades
@hashgraph/proto from 2.10.0 to 2.11.0 in /hedera-mirror-rest/check-state-proof #4629@hashgraph/proto from 2.10.0 to 2.11.0 in /hedera-mirror-rest #4627Contributors
We'd like to thank all the contributors who worked on this release!
This discussion was created from the release v0.67.0.
Beta Was this translation helpful? Give feedback.
All reactions