Open Yuripetusko opened 2 years ago
Any discussions open on how this will work regarding multiple networks? And are there any plans to support custom protocols for specific networks, like INV4 in Tinkernet, which can be used to wrap around RMRK NFTs and ownership can be sold in fractions.
Assuming all networks / parachains use the same pallet then it's just a matter of adding new rpc endpoints to a config and indexer.
As for INV4 this is a different topic I know nothing about. How would this wrapper prevent the NFT owner from transferring an NFT using RMRK pallet if it's owned by multiple accounts on wrapper side? is this some kind of transfer function overwrite?
It's not that it prevents transfer, that can be easily worked around by forcing the NFT to be depegged before it can be listed. What I meant was that it would be interesting to have this protocol integrated into Singular too, as it gives RMRK NFTs complete DAO properties allowing for this wrapper to have multiple RMRK NFTs pegged to it and, since it has its own account, also allows for fungibles to be owned by it. Furthermore, ownership and control over this primitive is done through tokens that grant the owner voting power, which is where fractions can come into play, I believe it would be interesting to have these tradable alongside normal depegged NFTs!
Once we have the base rmrk pallet nfts added to Singular, I am happy to add Invarch wrapper to the roadmap too
Finding Substrate developers is the main blocker for this task, and the main reason why it's progressing slower than EVM implementation. If you are a substrate developer, please contact us at "jobs AT rmrk DOT app"
Revamp Singular to support RMRK pallets. The primary goal here is support for minting, interacting, and trading of NFTs built using RMRK Substrate pallets