Skip to main content

Multi-asset (Multi-resource) NFTs

An asset (previously known as resource) is a type of output for an NFT: usually a media file.

An asset can be an image, a movie, a PDF file, or even a CATALOG (a special entity - see here). A multi-asset NFT is one that can output a different asset based on specific contextual information, e.g. load a PDF if loaded into a PDF reader, vs. loading an image in a virtual gallery, but both the PDF and the image are in the same NFT.

An asset is NOT an NFT or a standalone entity you can reference. It is part of an NFT - one of several outputs it can have.

Every RMRK NFT has zero or more assets. When it has zero, the metadata is "root level". Any new asset added to this NFT will override the root metadata, making this NFT revealable.


It is best to explain with some examples.

  • Revealable NFTs - mint identical NFTs and reveal them as unique later, all on chain without centralizing metadata
  • Cross-game skin files - supporting different game engines for cross-game cosmetics in the same NFT
  • Backing up NFT metadata - metadata redundancy and safety without centralized actors
  • Ticketing systems - tickets and ticket-stubs for proof of attendance and access
  • Mixed Media NFTs - eBooks that are audio and PDF at the same time, songs that are music videos and audio files at the same time, paintings with making-of videos, and more.

Equippables and Forward Compatibility#

When using the Nestable and Equippable NFTs, a multi-asset NFT can be made compatible with collections coming out in the future, adding utility to an NFT project that might otherwise die from lack of community interest post-launch.

As an example, a pickaxe compatible with a Chunky in Skybreach would have a pixel-drawn asset compatible with the Skybreach game engine.

Should a new 3D game come out later on, this same NFT can be made compatible with it easily. The issuer would add a new 3D asset to it, compatible with the new game's engine. Every owner accepting this new asset in their NFT would automatically have a more valuable NFT on their hands - no unrelated airdrops needed, no token spam in owner wallets. Just an NFT that can be and do more.

This not only adds more life to existing NFT projects, it also introduces the concept of dynamic rarity where the more collections an NFT is made compatible with, the more demand and thus value it has.

Proposing, Accepting, Replacing#

Adding a new asset into a multi-asset NFT requires the consent of both the issuer and the NFT's owner.

Specifically, only the issuer of the collection can propose a new asset, and only the owner can accept it. If the issuer and owner are the same, no accept step is necessary.

An owner of an NFT cannot add new assets onto their own NFT. This prevents mock-value from being added to an NFT.

An issuer cannot add new assets to an NFT without the owner's approval. This approval can be made ahead of time, or it can be made on-demand as a new asset is proposed.


The implementations below lead directly to code. For examples of how to utilize them to mint your own NFTs, please refer to the sidebar section for each implementation subtype.