Comment on page
A special subType to describe a collection of ordinals
The collection subType is an ordinal including an on-chain record describing a collection. Member ordinals reference the collection subType by
A collection inscription should be created first before any ordinals that reference it. If you do not record the collection inscription before the member ordinals, they will not be considered valid members of the collection.
The collection record should be signed with AIP using a key that matches the signature on member ordinals.
Since a collection is an ordinal, all top level required fields are still required. When defining a collection there will be no
collectionIdpresent in top level metadata.
The collection subType is also an ordinal whos inscription should be of type
While other content types will be considered valid, it it strongly recommended to use an image type to ensure apps can reliably display a collection preview.
To be considered valid by the indexer, accumulated rarity occurrences must equal 100.
To be considered valid by the indexer, each occurancePercentage array must sum to 100.
This pseudo-script screates a collection called "The Awesome Collection" with only the minimum required fields, and adds a signature via AIP so the issuer can be verified.
1SAT_P2PKH <INSCRIPTION> OP_RETURN MAP SET app <mint_platform> type ord subType collection name "The Awesome Collection" description "57 wonderul things" | AIP <address> "BITCOIN_ECDSA" <signature> [-1]