Yes the minting transaction should contain the right metadata, but I actually have found a more flexible way now to also update the metadata (as long the minting policy allows me to). So I assume now that the latest mint transaction that contains the 721 label is the valid one. So you can still update some of the metadata in case of mistakes. What do you think of this idea?
A version could make sense actually. How about adding a “version” property under the 721 key? And assume it’s version 0 if it’s not there.
Any IPFS gateway can find the file in the network. It just takes longer for a node that has not pinned the data initially. I wouldn’t add a centralized gateway like https://ipfs.io in the metadata actually. The hash is actually just the important thing and with ipfs:// you signal that you use the ipfs protocol, which makes it very flexible to also use any other protocol to where fetch the data from. The hash size is consistent that’s why I had no problem with ipfs:// (less than 64 bytes).
Do you mean 100 indivual NFTs with the same image or one token group with supply 100?
The idea behind other properties is that people can add whatever they want to their metadata to keep it flexible. Only image and name are key properties because this is what most 3rd party tools care about. They probably don’t go to specific in your NFT use case.
Yeah the off-chain idea was really just a thought. Haven’t used it either and probably just stick with the on-chain approach.