📄️ Introduction and Legacy
RMRK is a set of NFT standards which compose several "NFT 2.0 lego" primitives. Putting these legos together allows a user to create NFT systems of arbitrary complexity.
📄️ RMRK Legos, part 1
Nestable NFTs
📄️ RMRK Legos, part 2
Catalogs and Equippable NFTs
📄️ RMRK Legos, part 3
On chain emotes
📄️ Concepts, part 1
Now let us learn about some concepts that RMRK standards (legos) make possible.
📄️ Concepts, part 2
Global Item Economy
📄️ Use Cases, cross-game assets
Putting together all we know about RMRK, let us consider some use cases.
📄️ Use Cases, ticketing
Ticketing
📄️ Use Cases, revealable NFTs
Revealable NFTs
📄️ Use Cases, metadata backup
Backing Up Metadata
📄️ Use Cases, part 5
Mixed Media NFTs
📄️ Use Cases, part 6
Character Progression Systems
📄️ Use Cases, part 7
Puzzles
📄️ EVM, part 1
Let's learn about RMRK's EVM implementation.
📄️ EVM, multi-asset part 1
An asset is a type of output for an NFT, usually a media file.
📄️ EVM, multi-asset part 2
Deploy Script
📄️ EVM, nestable part 1
The concept of nested NFTs refers to NFTs being able to own other NFTs.
📄️ EVM, nestable part 2
User Journey
📄️ EVM, nestable and multi asset, part 1
Nestable and MultiAsset RMRK legos can be used together to provide more utility to the NFT.
📄️ EVM, nestable and multi asset, part 2
User Journey
📄️ EVM, merged equippable p1
The MergedEquippable composite of RMRK legos uses both the Nestable and MultiAsset RMRK legos as well as the Equippable lego. In addition to these three RMRK legos, it also requires the Catalog RMRK lego. Let's first examine the Catalog RMRK lego and then the Equippable one.
📄️ EVM, merged equippable p2
Deploy Script
📄️ EVM, merged equippable p3
Adding assets to Gems is done in the addGemAssets. It accepts Gem, address of the Kanaria smart contract and the address of the Catalog smart contract. We will add 4 assets for each gem; one full version and three that match each slot. Reference IDs are specified for easier reference from the child's perspective. The assets will be added one by one. Note how the full versions of gems don't have the equippableGroupId.