I launched an NFT collection with 100 tokens on the Ethereum blockchain. After using the burn function to destroy 5 of these NFTs, they still appear in my OpenSea collection page. I tried refreshing metadata multiple times but the burnt tokens remain visible.
I found OpenSea documentation stating that items can only be deleted if created through their Shared Storefront, which I didn’t use for my collection. Is there a method to remove these burnt NFTs from the collection view on OpenSea?
oh wow, this is so frustrating! i’ve been watching this problem across different collections and opensea just doesn’t prioritize fixing their burn detection.
have you checked if your contract emits the right events when burning? are you using the standard ERC721 burn function or something custom? sometimes opensea isn’t listening for the specific burn events your contract emits.
also, has anyone tried the newer opensea api endpoints for collection management? heard they were working on better tools for collection owners but haven’t tested it myself.
what’s interesting is some collections handle burns fine on opensea while others don’t - makes me think it’s about how the burn function is implemented or what events get fired. did you base your contract on openzeppelin’s burnable extension?
this whole situation really shows how centralized these nft marketplaces still are. we’re all at opensea’s mercy for indexing quirks even when our on-chain data is perfect.
No direct way to remove burnt NFTs from OpenSea’s collection display with custom contracts. I dealt with this exact problem on my collection last year. OpenSea keeps showing the metadata even after you burn tokens because their database doesn’t sync with burn events automatically. The refresh metadata button just updates existing data - it won’t remove burned tokens. Here’s what worked for me: update the metadata for burned tokens to show “BURNED” in the name and use a blank or burn-specific image before running the burn function. They’ll still show up on OpenSea, but at least users can see they’re destroyed. Not perfect, but it’s a decent workaround until OpenSea fixes their indexing to handle burns properly.
yeah, opensea’s indexing is broken for burns. same thing happened with my pfp project - contacted support but they said tough luck unless you’re using their storefront contract. only fix i found was setting tokenURI to return empty metadata for burned tokens, but opensea still takes weeks to update sometimes.