CollectionItem SubType
When the top level type is collectionItem
the subTypeData
is defined here.
subTypeData data
The following properties define the subTypeData
object and should be used if your collectionItem
ordinal has additional information that should be associated with it. A collectionId
at the top level is required for collectionItem
ordinals. Since a collection is an ordinal, all top level required fields are still required as well.
Name & Description | Required | Type | Example |
---|---|---|---|
| Y |
| TODO: use a good example |
| N | int | 3 |
| N | int | 10 |
| N | string enum based on | "legendary" |
| N | traits as defined by collection | see examples below |
| N |
| https://... b://... c://... |
Trait
The definition of trait
within the traits
array:
Name | Description | Required | Type |
---|---|---|---|
name | The name of the trait | Y | string |
value | The value of the trait | Y | string |
rarityLabel | A rarity label to associate with the trait | N | RarityLabel |
occurrencePercent | The percentage which this trait occurs within this collection | N | string |
Attachment
Name | Description | Required | Type |
---|---|---|---|
name | The name of the attachment | Y | string |
description | The description of the attachment | N | string |
content-type | The content-type of the attachment | Y | string |
url | The url of the attachment | Y | string |
Transaction Structure
This pseudo-script creates an ordinal with metadata called "The Awesome Ordinal" with only the minimum required fields, and adds a signature via AIP so the issuer can be verified.
Output 1:
Example ord
type data
ord
type dataLast updated