New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Forbid sending an equipped NFT #187
Comments
@mrshiposha thanks for the reporting. In Kusama rmrk-tools version we unequip during sending. Ideally to have feature parity, so will look into that. |
I think forbidding SEND would be difficult as send is part of rmrk-core, but equip (and the Equippings storage) is part of rmrk-equip...and unequipping during SEND would be difficult for the same reason... |
But there is an |
indeed |
I suggest forbidding sending of an equipped NFT. I believe sending an equipped NFT can lead to exploits like #185...
Also, I think that it is logically more accurate to unequip an equipped NFT first and then send it to some user/token.
The text was updated successfully, but these errors were encountered: