NFT Metadata

On-chain metadata

We support the `TokenMetadata` from NEP-177 version 1.0.0 [1]
1
type TokenMetadata = {
2
title: string|null, // ex. "Arch Nemesis: Mail Carrier" or "Parcel #5055"
3
description: string|null, // free-form description
4
media: string|null, // URL to associated media, preferably to decentralized, content-addressed storage
5
media_hash: string|null, // Base64-encoded sha256 hash of content referenced by the `media` field. Required if `media` is included.
6
copies: number|null, // number of copies of this set of metadata in existence when token was minted.
7
issued_at: string|null, // When token was issued or minted, Unix epoch in milliseconds
8
expires_at: string|null, // When token expires, Unix epoch in milliseconds
9
starts_at: string|null, // When token starts being valid, Unix epoch in milliseconds
10
updated_at: string|null, // When token was last updated, Unix epoch in milliseconds
11
extra: string|null, // anything extra the NFT wants to store on-chain. Can be stringified JSON.
12
reference: string|null, // URL to an off-chain JSON file with more info.
13
reference_hash: string|null // Base64-encoded sha256 hash of JSON from reference field. Required if `reference` is included.
14
}
Copied!

Description of the metadata that will show up on Paras

  • title: The name of this NFT
  • description: A longer description of the token.
  • media: URL to associated media. Preferably to decentralized, content-addressed storage. If you have base_uri on your contract metadata, it will be prepended to media.
  • copies: The number of tokens with this set of metadata or media known to exist at the time of minting. This will be shown on Paras as copies
  • extra: anything extra the NFT wants to store on-chain. Can be stringified JSON. You can put attributes here which will be explained later.
  • reference: URL to an off-chain JSON file with more info. You can put more info or anything from on-chain metadata to be replaced with the ones on reference

Non-standard metadata

You can put the non-standard metadata as on-chain extra or inside JSON file in reference.

Attributes

Attributes that will be shown on each NFT, e.g.
1
{
2
"attributes": [
3
{
4
"trait_type": "Base",
5
"value": "Starfish"
6
},
7
{
8
"trait_type": "Eyes",
9
"value": "Big"
10
},
11
{
12
"trait_type": "lvl",
13
"value": 1
14
}
15
]
16
}
Copied!

Animation URL

  • animation_url : URL to multimedia attachment. If you have base_uri on your contract metadata, it will be prepended to animation_url. We use animation_url for the newly supported audio NFTs with .MP3, .AAC, and .WAV formats.

Collection Info (only if you are using shared NFT contract)

If you are using x.paras.near or paras-token-v1.testnet you need to put these inside the reference JSON. You need to create a collection first using Paras UI or API.
  • collection : collection name, e.g. "Genesis"
  • collection_id: collection id, e.g. "genesis-by-parasnear"
  • creator_id : creator NEAR wallet address, e.g. "paras.near"