assetTree File


Similar to Git, every registered content file has its own assetTree file in IPFS to describe the property of the asset, including creator, creation time, license, etc. The following is an example of the assetTree file:

  "assetCid": "bafybeibhkd37eteh5eykn36im4gyspwihrxbgvr23fhxmzwu46qjampnci",
  "assetSha256": "1bb1f4817c3d6d2c81f22a1a175b7f22d68aa79b1b077361852d4a2ba2cc8c17",
  "encodingFormat": "image/png",
  "assetTimestampCreated": "2022-08-18T15:33:51.738204Z",
  "assetCreator": "0x40ea78e78f3cF0FAcc04048b5b2e90e1ff610C4A",
  "license": {
    "name": "CC BY-NC-ND",
    "document": ""
  "abstract": "Hello World",
  "nftRecord": "bafkreibxbibhsvqgfurse4qaxvzxdwexpubkpg5gviptdfb5q24tkxnhze"

The assetCid logged in the assetTree is the same as the Nid of the digital media file. You can also find a more complicated example of the assetTree file on IPFS.

When asset is registered, the first commit is made and the assetTree file is also created. The assetTreeCid can be found in the on-chain commit log as well as the Sha256 and Signature of the assetTree file.

Last updated