Update NFT metadata
A TokenUpdateNftsTransaction
updates the metadata property of non-fungible tokens (NFTs) on the Hedera network. The transaction requires signing with the metadata key and will fail otherwise. The new metadata must be a valid byte array and is limited to 100 bytes. All transactions are recorded on the network, providing an auditable history of changes. The metadata key allows updates to existing NFTs in a collection; if no value is provided for a field, it remains unchanged.
🚨 Metadata keys, like other token keys, must be set during the token creation. If metadata keys are not set when the token is created, they cannot be added later, and you won't be able to update the token's metadata.
With the introduction of HIP-850, the Supply Key now has the enhanced capability to update the metadata of NFTs while they are held in the treasury account. This enhancement allows for dynamic updates to NFT serial numbers before they are distributed, ensuring that once the NFTs leave the treasury account, their metadata remains immutable. This approach provides security and control, preventing unauthorized modifications after distribution.
Property | Description |
---|---|
Token ID | The ID of the NFT to update. |
Serial Numbers | The list of serial numbers to be updated. |
Metadata | The new metadata of the NFT(s). |
Transaction Signing Requirements
Metadata key is required to sign.
Transaction fee payer account key.
Transaction Fees
Please see the transaction and query fees table for the base transaction fee.
Please use the Hedera fee estimator to estimate your transaction fee cost.
Methods
Method | Type | Requirement |
---|---|---|
| TokenID | Required |
| List<int64> | Required |
| bytes | Optional |
FAQs
Contributors: MilanWR
Last updated