Contract-managed tokens 🪙
In Services 0.29 we have followed the HIP-514 roadmap to give contract authors many new ways to inspect and manage HTS tokens.
The HIP enumerates the ways; examples include a contract that revokes an account's KYC for a token, or deletes a token for which it has admin privileges, or even changes a token's supply key based on the metadata in an NFT!
Note there are four HIP-514 functions that will be part of release 0.30, as follows: getTokenExpiryInfo(address), updateTokenExpiryInfo(address, Expiry), updateTokenInfo(address, HederaToken), isToken(address token) and getTokenType(address token).
Deprecations
Please note this important deprecation that will change how clients fetch token associations and balances after the November release in this year. At that time, mirror nodes will become the exclusive source of token association metadata. This is because HIP-367 made token associations unlimited, so in the long run it will not be efficient for consensus nodes to serve this information.
Contributors
We'd like to thank all the contributors who worked on this release!
- @alshapi
- @anighanta
- @bugbytesinc
- @CordonaCodeCraft
- @Daniel-K-Ivanov
- @dimitar-dinev
- @georgiyazovaliiski
- @ivanparnarev
- @IvanKavaldzhiev
- @jasperpotts
- @JeffreyDallas
- @joan41868
- @MarcKriguerAtHedera
- @Neeharika-Sompalli
- @OlegMazurov
- @qnswirlds
- @rbair23
- @rjuang
- @rusiboyadjiev
- @shemnon
- @SimiHunjan
- @statop
- @stoqnkpL
- @superboo
- @tdermendzhievv
- @tinker-michaelj