Requirements

• Easy to identify which collection any given NFT belongs to
• Possible to find all NFTs that belong to a given collection
• Collection metadata such as its name, description, and image
• NFT metadata such as name, description, image, and traits
• Open collection - not all collection NFTs have to be known/minted when creating a collection
• Backwards compatible with existing inscriptions

NFTs in Asteroid Context

Asteroid protocol already supports arbitrary data inscription with an option to specify a parent and metadata like name, description and mime type (media type of inscribed content)

Let’s define Generic inscription transaction specification to see all the details of what’s available.

Generic Inscription transaction

Inscription transaction MUST specify Inscription operation, optionally CAN provide Inscription data, and optionally CAN require Inscription fee to be paid

Inscription operation

urn:{metaprotocol}:{chain-id}@{version};{operation}${param}={value},{param}={value}