-
Notifications
You must be signed in to change notification settings - Fork 155
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
Inconsistency in NFT ID Handling #51
Comments
This is intentional. We want to cycle through all the token Ids. If you want to prevent rarity sniping, make a second baseURI update after all the IDs have been cycled through once. |
We might make it an option in the future to allow recycling token Ids, but we have other priorities. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello guys,
I am currently testing the DN404 protocol, and I've encountered inconsistencies regarding NFT IDs.
Here is the scenario:
This process raises concerns about consistency in NFT ID. Shouldn't there be a mechanism in place to maintain consistency and ensure that IDs are not lost?
If I'm not mistaken, The ERC404 protocol addresses this by adding a queue for burned IDs to be minted again later, ensuring consistency with the NFT IDs
Thanks for advance
The text was updated successfully, but these errors were encountered: