-
Notifications
You must be signed in to change notification settings - Fork 170
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
Create a generic transaction to burn NFTs #236
Comments
You should be sending an nft to the Burner contract in case it has any callback functionality defined Contract address and name isn't really enough, either. You'd need resource name as NFTs do not need to be called NFT. I would suggest taking in the resource type and id as inputs. |
Of course, the |
@btspoony Do you know if this is something that a lot of people are still asking for? I think something that is a generic receiver is probably a bit too much work for us to maintain, so I believe that our best bet is to just have a transaction like this that can transfer any NFT to the burner contract which destroys it. A user of any NFT project would simply just run that transaction and it could burn any NFT. We could add it as an option on flow port for now so a user of Top Shot for example could transfer their NFT to flow wallet, then log in to flow port and choose the burn NFT option to burn it. Do you think that sounds reasonable? |
That makes sense to me. |
Good point, I'll update it to accept multiple NFTs |
Issue To Be Solved
Users need an easy way to burn NFTs from anywhere that doesn't require the specific app to implement burning functionality. A burner address like in Ethereum would be easiest, but that isn't really possible since you can't transfer to an uninitialized account.
Suggest A Solution
Burner
.The text was updated successfully, but these errors were encountered: