We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Users don't always understand how to fix the double mint issue, even when the UI displays a warning about a duplicate mint detected.
Add additional text to the UI for the double mint detection dialog: "If you want to re-mint, burn the previous mint first and then retry "
No response
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Describe the problem
Users don't always understand how to fix the double mint issue, even when the UI displays a warning about a duplicate mint detected.
Describe the solution you'd like
Add additional text to the UI for the double mint detection dialog:
![Screenshot from 2023-12-05 18-16-17](https://private-user-images.githubusercontent.com/564979/288232802-ded7e10d-bfa6-49ba-a464-9ea7ee5a41b4.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Mzk2MDYwNDQsIm5iZiI6MTczOTYwNTc0NCwicGF0aCI6Ii81NjQ5NzkvMjg4MjMyODAyLWRlZDdlMTBkLWJmYTYtNDliYS1hNDY0LTllYTdlZTVhNDFiNC5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjUwMjE1JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI1MDIxNVQwNzQ5MDRaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT1kY2U5NDg1MjBjODRkOWUwMWNiOGE0ZTZjNWUyMjhlZWYxNzNiN2Q4NTQ4MzZhNDEzMGQxOWI4ZDU1MjQwNDQwJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCJ9.ApqmcJaZxiAI0OPWZ27YXDCkPhVQB49Sh_s-Jbu0Wbk)
"If you want to re-mint, burn the previous mint first and then retry
"
Alternatives considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: