You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Like the ""burn"" feature we have on datadex.itheum.io in the wallet section, a user can "burn" a Data NFT they own.
In wallet view, have a burn button. Check the wallet on datadex.itheum.io for design
When the user clicks that, we need a confirmation popup "Are you sure you want to burn this?" - Check the wallet on datadex.itheum.io for design idea for the popop. But iplike that one which allows you to pick how much supply you want to burn as MultiversX supports multiple suppy... in the EVM app, we dont need this... we just ask them "Are you sure you want to burn this?".
You can also follow the same design as :
When they confirm, then "burn" the data NFT. Show a progress model for the TX... i'm not 100% sure how we can "burn" on the EVM blockchain, I think it may be as simple as sending a TX to the 0x or null address? you need to do some research
If the TX is a fail, then show an error message on the popup (like in above design which shows error messages)
if the TX is a success, then close the popup and refresh the wallet items so that the burned item goes away
The text was updated successfully, but these errors were encountered:
Like the ""burn"" feature we have on datadex.itheum.io in the wallet section, a user can "burn" a Data NFT they own.
You can also follow the same design as :
When they confirm, then "burn" the data NFT. Show a progress model for the TX... i'm not 100% sure how we can "burn" on the EVM blockchain, I think it may be as simple as sending a TX to the 0x or null address? you need to do some research
If the TX is a fail, then show an error message on the popup (like in above design which shows error messages)
if the TX is a success, then close the popup and refresh the wallet items so that the burned item goes away
The text was updated successfully, but these errors were encountered: