URI

To keep it in the light of evolution, our project's metadata URI will evolve in three stages:

1. Static Firstly, metadata will be treated as static, saved in the usual baseURI approach, which many other NFT projects also utilize for its cost-efficiency. In simple terms this involves storing a single link containing all metadata files, usually hosted via IPFS, for all NFT IDs.

2. Semi-dynamic Secondly, we'll start to allow Token Slots to be made, where an NFT could have more than one metadata stored, deviating from the standard baseURI. This could mean a change in the artwork's appearance, name changes, story altercations, the framing of the card and more. These token slots make it possible for the owner to create (or request) non-destructive changes to their NFTs, but will require some manual effort on our side to process.

3. Dynamic Thirdly, the conversion of the standard URI to Base64 URI. This will allow for more automated changes and creates some interesting avenues to explore. For instance: creating a leveling system, changing storylines in a gamified manner where holders co-write a story for their characters without our involvement, equipping items or having dynamic stats. The possibillities are endless.

---

Here we didn't go all too deep into the details of how the metadata will work and how it will get implemented. See ZkRoninsMeta.sol in the Overview section for this.