I’ve launched a few burn pages where people are burning tokens from an OpenSea contract to redeem tokens from a new Manifold Contract on Base. For some users it’s working fine, for others, it’s not recognizing the eligible tokens in their wallet. There is especially an issue when users purchase qualified tokens to burn after the claim page has been published. Example, you need 3 tokens to qualify, someone with 1 token buys 2 more. When they go to the claim page the site is not recognizing the 2 tokens they just purchased.
Howdy, thanks for reporting. We’re aware of the issue and doing what we can to speed things up. Our base nodes have been having trouble and we’re in direct contact with the base team. Issue comes from our node being a few blocks behind the real world, so this causes things like
Newly minted/bought token not appearing as eligible for burn
Token that was just burnt seemingly eligible for burn again
The good news is for 1, that issue fixes itself after somewhere between 2-10 minutes.
For 2, the good news is that our contracts are very well written and would never allow someone to double burn a token. They will get an error if they attempt to be sneaky like that, and they will not be able to even fire off a transaction and waste gas on a tx that would fail.
If you ever have any doubt about what is and is not in your wallet, check against the following as a sanity check:
OpenSea
Your browser wallet extension
Etherscan
Those 3 places were probably correctly showing the tokens as no longer in your wallet post-burn.
On etherscan I can the tokens did completely burn as expected, so rest assured it’s all working, just some delays in data showing.