RMRK.app is a way to abuse Kusama's system.remark extrinsic (?) to write custom notes onto the chain in a standardized and structured way.
Each NFT is part of a collection. Each collection and each member NFT have some defined fields and metadata that can enrich their look, feel, and uniqueness.
system.remark is being abused to make this possible, extra care
needs to be taken to properly read chain state and process only valid RMRK NFTs. More
info in the standards section below.
While it has been added to Kusama's broader NFT strategy you should still not use it for anything non-trivial and should absolutely consider it "alpha". Sign up to the newsletter below to be notified when we launch new NFTs, new standards, and new tools to interact with them.
Standards exist to formalize the shape and form of remark-based NFTs. They're simple JSON structures written according to some rules detailed in the Specs Repo. Here's an example collection and an example NFT in that collection.
The definitions above are based on the RMRK0.1 standard. You can see this version of the
on Github, or below.
NFTs are part of collections. NFTs and Collections are broadly defined as "entities", while interactions between them and the off-chain world are predictably called "interactions". A game called "Zombie collector" can have different NFTs inside it, like "Blue Zombie", "Red Zombie", etc. The "Garmin" sports watch app can have different badges like "Midnight runner", "Long distance swimmer", etc. Collections can also be used to sub-group NFTs: "Garmin - Swimming", "Garmin - Running" and each collection can have its own issuer.
A collection can have metadata in an off-chain location, preferably on IPFS. The metadata contains a description, an image, an external URL on which to learn more, and possibly attributes - descriptors that add uniqueness and rarity to NFTs. Live example
An NFT can (and should!) have metadata in an off-chain location, preferably on IPFS. The metadata contains a description, an image, an external URL on which to learn more, and possibly attributes - descriptors that add uniqueness and rarity to NFTs. It can also contain animation and YouTube video links for more meta info about the NFT. Live example
Interactions have their own extremely simple standard. Tools are expected to recognize this standard, and discard abuse attempts. For example, no one is stopping a random user from crafting a transaction that makes it seem like they sent someone an NFT they do not own. The TX standard is there to formalize transfers according to data in the NFTs and their Collections. We further document this in the Implementer's Guide
The following interactions currently exist:
A single send transaction costs around
0.005 KSM, with a mint transaction going up to
0.01 KSM maximum in our current experiments. There's
room for optimizing these costs further in future iterations of the standards.
It's as serious as people want to take it. It was built as an experiment and hobby project for DotLeap.com, but if it gets a life of its own, great!