Non-native parent-child abstraction on AssetHub

[vikiival]

This is a discussion related to nestable NFTs on AssetHub.

Few ideas to share

• Using on-chain attributes to store parent-child relationships, with the parent key as the collection-token ID string.
• A parent registry contract that serves as a proxy pointer to map nesting structures.

[niklasp]

id go with the easy way of attributes storing a parent key as i am hoping there will be native implementations at some point and it could be migrated then.

I think however that only that info is not enough. the rmrk standard stores more (havent looked into it a long time) but the slot the item is placed in, if it is equipped, also multi resource nfts, ... it would be sad if any of those information is lost. Maybe just do a setAttribute call on the nft with a long json string storing all rmrk nestable, equippable data for now?