RIP-004: Migrate Collection

[Swader]

• author(s): Bruno Škvorc
• contact: [email protected]
• RIP type: upgrade

RIP Summary

The MIGRATE interaction allows for porting a collection from a previous standard to the current standard in which the MIGRATE interaction is defined.

RIP Details

The MIGRATE interaction can only be called on Collections, and immediately applies to all child NFTs. The MIGRATE interaction can only be called by the current issuer of the collection.

Some fields might get dropped during a migration (i.e. a change from computed to static property or vice versa) while others may get added (e.g. RIP 002 or RIP 003).

Impact and notes

Tools should allow users to migrate their collections. Tools should not allow interactions across RMRK standard versions and should instead force a user to upgrade to the new standard version first.

Interactions that have been emitted using a previous standard (e.g. a LIST issued under 0.1 and the collection containing the listed item moving to 0.2) are still fine and to be interpreted by the tools according to the originally specified standard version. Given that interactions are short lived, no migration is necessary. A notable exception can be the LIST interaction which can be CANCELED and re-issued using the new standard if needed (in case of bugs found in the previous standard's implementation or other concerns).

[Swader]

This was originally written as a RIP for 1.0.0 but we decided to deprecate and kill the 0.1 mints entirely, thereby allowing a clean slate for 1.0.0. The migration will still be needed for ^1.0.0.