Artifacts & Token IDs
In Corepack, each Artifact has a record ID but they are NOT the NFT token ID on-chain. To create a successfully create an Artifact, integration partners will have to explicitly specify the token ID. It is recommended that these token IDs are persistent monotonically increasing sequence of numbers.
Artifact Collection Token Standards
ERC721ERC1155
ERC20 is not supported as collection or as a reward.
ERC20 tokens sent to our Rewards Vault contracts will not be recoverable.
Artifact Metadata Standards
Corepack supports metadata that is structured similarly to external NFT marketplaces like OpenSea. Here's the OpenSea metadata standards spec
At the moment, we support the following properties...
| Property name | Description |
|---|---|
| name | Name of the item. |
| description | A human readable description of the item. Markdown is supported. |
| animation_url | A URL to a multi-media attachment for the item. The file extensions GLTF, GLB, WEBM, MP4, M4V, OGV, and OGG are supported, along with the audio-only extensions MP3, WAV, and OGA. Animation_url also supports HTML pages, allowing you to build rich experiences and interactive NFTs using JavaScript canvas, WebGL, and more. Scripts and relative paths within the HTML page are now supported. However, access to browser extensions is not supported. |
| image_url | This is the URL to the image of the item. Can be just about any type of image (including SVGs, which will be cached into PNGs by OpenSea), and can be IPFS URLs or paths. We recommend using a 350 x 350 image. |
Artifact Collection Transferability
Once a collection is deployed on-chain, there's no way to switch on or off transferability. So if a collection is non-transferrable, it will be non-transferrable forever.