AssetTree
Every asset has a Tree file on IPFS that describes the properties of the asset, including creator, creation time, license, etc. This Tree file, known as the "AssetTree," is a crucial component in managing and verifying the authenticity of digital assets on a blockchain. The AssetTree contains a collection of metadata, also known as "Nid" or content identifiers, that describe the properties of the asset.
The Nid of the AssetTree is included in the on-chain Commits. AssetTree allows anyone to retrieve the assets from IPFS and verify the properties of the asset. This allows anyone to verify that the asset has not been tampered with, and that it can be traced back to its original creator.
To illustrate, consider a digital art piece, the AssetTree for that piece would include information such as the artist's name, the date the art was created, the license under which the art is distributed, any relevant keywords, and any other information about the art. This information can be used to verify that the digital art is authentic and has not been tampered with, and also makes it easy for others to discover and learn more about the art.
Overall, AssetTree provides a comprehensive view of the properties of the asset and ensures transparency and accountability, making it an essential part of the assetization process.
AssetTree is a JSON file on IPFS containing the following information:
- 1.
assetCid: (string) The Nid of the asset file - 2.
assetCreator: (string) Name of the asser creator - 3.
encodingFormat: (string) The asset's type expressed using a MIME format - 4.
assetTimestampCreated: (timestamp) Creation time of the asset file - 5.
assetSha256: (string, optional) SHA-256 hash of the asset file - 6.
abstract: (string) A summary or abstract of the asset - 7.
creatorWallet: (string, optional) Wallet address of the asset creator - 8.
license.name: (string, optional) License of the asset file - 9.
license.document: (string, optional) URL of the license file - 10.
usedBy: (string, optional) URL of the website that uses the asset - 11.
nftRecord: (string, optional) IPFS Cid where you can find all the NFT records. More details can be found in the nftRecord page. - 12.
custom: (JSON, optional) Custom metadata
The DBDiagram describes the relationship between Commit and AssetTree tables. Here is an example of the AssetTree file. You may also refer to the nit open-source project for more examples of how to create AssetTree and Commit.
Note:
- This specification follows the EIP-191 verification method for input: data, signature and output: signer's wallet address.
Last modified 1mo ago