Thanks for the suggestion lyndo! Here’s what happened when I tried:
I cleared local storage, logged back in, and then tried the process again. I got the same error when trying to update on mainnet. Also when I try to use the etherscan tools on this token I get crazy errors as well. Can’t burn.
Hi Lyndo! Thanks again for your reply. I see that invisible (to my manifold page) #9 was burned but I was still unable to burn #10 via the etherscan method. I ended up burning it on Foundation.app and that seems to have worked. If you’re curious is this the error I kept receiving when attempting to burn #10 via etherscan.
That high burn cost warning was appearing before I tried burning on Foundation. My supposed solution was to burn on Foundation but I guess that means it’s still everywhere. How unfortunate.
Hey there @rollin
I had the same problem. Burned the token on FND but it still shows up on OpenSea and everywhere else. When tried to remove it manually via ether scan, I also was having that high price warning (around $500) on metamask.
I guess I’ll try to ask the marketplaces to hide it for me as you suggested, assuming it’s possible.
One related question @lyndo there is an option on OpenSea that says delete collection. If I do that, will it only remove my manifold contract/collection from their site without doing it everywhere else? Or that would burn it completely?
If it’s owned by the Null Address it has already been burned. You’re seeing the large amount because it’s owned by the burn wallet. If you would like Opensea to hide this token, like it’s described in the thread you’ll need to reach out to their support. Deleting the collection Opensea doesn’t burn anything it just hides the contract from Opensea.
