The @AzukiZen collection will be revealed on Thursday 12pm noon PST.
Rare NFTs get sniped upon reveal by scripters. A quick thread about my thoughts going into the reveal around metadata.
TLDR; To not get sniped, DO NOT LIST until after reveal.
1/8
🧵👇
Part of the draw of NFTs is the nostalgic feelings reminiscent of opening a pack of Pokemon cards. We feel some of that magic has been lost as the NFT space has grown, and have strived to rediscover it with @AzukiZen
2/8
The metadata reveal is usually an exciting moment for any NFT collection. Everyone is discovering their NFT’s traits for the first time, followed by marketing activity and buzz. Unfortunately, metadata reveal usually results in rares getting sniped at a low price
3/8
To understand how rares get sniped quickly upon reveal, we need to dive deeper into how metadata works for NFTs. When a collection is revealed, the contract is sent a transaction to point the tokenURI at the live metadata. Anyone can now fetch metadata for any token
4/8
While the community is excited and looking at @opensea for their NFT, spamming refresh metadata, the snipers have already deployed a script that executes the moment the metadata URI is set. They can pull all 10k json and develop an understanding of "rarity" within seconds
5/8
While you may still be looking at the collection page slowly seeing images filter in, the people scripting have identified all the top rarities and have begun buying them up. Anyone looking at opensea *never* had a chance at rares, and they are now in the hands of scripters
6/8
The only way to protect yourself is to NOT LIST your NFT until after all the metadata is revealed and you understand what you have. You only open yourself up to heartbreak leaving it up on reveal, scripters are potentially getting a free option to buy your rare
7/8
The reveal of a collection is a magical moment. I wrote this thread because we want to keep the rares in as many hands of our authentic community members as possible. Good luck on bean reveal!
8/8
• • •
Missing some Tweet in this thread? You can try to
force a refresh