v0.37.0 #2276
steven-sheehy
started this conversation in
Releases
v0.37.0
#2276
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
This release broadens our support for non-fungible tokens (NFTs) with new NFT-specific REST APIs. A new API was added to return a list of NFTs for a particular token ID. We also added a new API to return a single NFT by its token ID and serial number. Finally, we added an API to see the transaction history for a particular NFT. In an effort to have more manageable REST API code, we now adopt a more object-oriented approach by utilizing models, view-models and services. Below is an example of the three new APIs:
GET /api/v1/tokens/0.0.1500/nfts{ "nfts": [{ "account_id": "0.0.1002", "created_timestamp": "1234567890.000000010", "deleted": false, "metadata": "ahf=", "modified_timestamp": "1234567890.000000010", "serial_number": 2, "token_id": "0.0.1500" },{ "account_id": "0.0.1001", "created_timestamp": "1234567890.000000009", "deleted": false, "metadata": "bTM=", "modified_timestamp": "1234567890.000000008", "serial_number": 1, "token_id": "0.0.1500" }], "links": { "next": null } }GET /api/v1/tokens/0.0.1500/nfts/1{ "account_id": "0.0.1001", "created_timestamp": "1234567890.000000008", "deleted": false, "metadata": "bTM=", "modified_timestamp": "1234567890.000000009", "serial_number": 1, "token_id": "0.0.1500" }GET /api/v1/tokens/0.0.1500/nfts/1/transactions{ "transactions": [{ "consensus_timestamp": "1234567890.000000009", "transaction_id": "0.0.8-1234567890-000000009", "receiver_account_id": "0.0.1001", "sender_account_id": "0.0.2001", "type": "CRYPTOTRANSFER" }, { "consensus_timestamp": "1234567890.000000008", "transaction_id": "0.0.8-1234567890-000000008", "receiver_account_id": "0.0.2001", "sender_account_id": null, "type": "TOKENMINT" }], "links": { "next": null } }This release also adds support for custom fees for HTS as defined in HIP-18. After the mirror node design was completed, the necessary custom fee tables were added and the importer modified to ingest the transactions. A list of assessed custom fees was added to the
/api/v1/transactions/{transactionId}endpoint. The ability to find a token's custom fee schedule at a point in time was added to the/api/v1/tokens/{tokenId}endpoint.We optimized the balance file parsing performance to be able to process files with a large numbers of accounts. We previously loaded every account balance into memory before persisting. When testing files with tens of millions account this would cause the importer process to slow down and run out of memory. This has now been optimized to load the items one by one into memory then batch persist them to the database.
Breaking Changes
If you're using our monitor tool to verify or performance test the network, you should be aware of some breaking changes to its configuration format. In order to make it easier to override the default behavior without having to duplicate its configuration, we changed the scenario properties from a list to a map where the key is the scenario name. Specifically we changed
hedera.mirror.monitor.publish.scenarios,hedera.mirror.monitor.subscribe.grpc, andhedera.mirror.monitor.subscribe.rest. Also, the content of theelapsedduration in the monitor REST API changed slightly to a format like1h2m57s.Enhancements
Bug Fixes
Documentation
Dependency Upgrades
@hashgraph/proto from 1.0.25 to 1.1.4 in /hedera-mirror-rest/check-state-proof #2233Contributors
We'd like to thank all the contributors who worked on this release!
This discussion was created from the release v0.37.0.
Beta Was this translation helpful? Give feedback.
All reactions