With the addition of the version into the RMRK itself, the version inside the collection's data becomes unnecessary and is just dead data weight. This RIP proposes the removal of the version from the collection's data.
RIP Details
Previously, the MINT interaction looked like this:
With that, JSON_OF_COLLECTION does not need the collection's version field, and as such the Collection entity also does not need it.
This applies to NFT minting as well.
Impact
As this is going into V1 onward, it should not cause any problems. Even if the version is still included in the data objects, it will just cost more but do no damage.
Swader
commented
3 years ago
RIP Summary
With the addition of the version into the RMRK itself, the version inside the collection's data becomes unnecessary and is just dead data weight. This RIP proposes the removal of the version from the collection's data.
RIP Details
Previously, the MINT interaction looked like this:
Now, the interaction is:
With that,
JSON_OF_COLLECTIONdoes not need the collection's version field, and as such the Collection entity also does not need it.This applies to NFT minting as well.
Impact
As this is going into V1 onward, it should not cause any problems. Even if the version is still included in the data objects, it will just cost more but do no damage.