A recent free-to-mint NFT project called Kuma Boss received a backlash from the community due to some mishap that happened with their minting event. Let’s find out what actually happened with the Kuma Boss NFT collection.
About the Kuma Boss collection
Kuma Boss NFT is a collection of 5,555 bears (Kuma is Japanese for “bear”). The team announced that it would be a free-to-mint NFT. In addition, buyers could mint Kuma Boss NFTs on July 13th for just the cost of gas. As expected, the NFTs were minted in no time. Evidently, Kuma Boss looked to take advantage of the current hype around free NFT mints. Many will know that free NFT mints have surged in popularity during the current bear market.
However, Kuma Boss has done something that not many projects have been doing lately. It actually had a website and lore.
Smart contract issues in the Kuma Boss NFT mint
F
The first and foremost issue with the Kuma Boss NFT collection was its smart contract. In short, the team launched the smart contract on OpenSea incorrectly. The team had labeled the contract as “testingggg”. As one tweet from the thread explained,
this was the name of the testnet collection and we had changed the name of the collection on http://testnets.opensea.io to “KumaBoss” and updated all relevant details. We assumed this would carry over when we launched our contract on mainnet, we were wrong.
However, the team response just opened up a door to more issues.
Once we launched, we saw the name on Opensea and our brains went into a state of panic so we thought the best plan of action was to pause the mint and put out a tweet stating that we will be launching a new contract and everyone who minted will be airdropped a free NFT. We quickly realized the flaw in this being that those who bought off secondary would be left without compensation so we deleted the tweet.
The team eventually consulted with an experienced developer who advised them to simply keep the contract and update the details on OpenSea. But that was too late. Because of the tweet, there were minters who sold their NFTs thinking that there would be a new contract, thus ending up with nothing.
Developer issues
As it turns out, the Kuma Boss NFT dev did in fact sell a 1/1 from the 200 NFTs that Kuma Boss held back for its team. Kuma Boss maintains that the team pulled one of the three 1/1s in the collection “by pure luck”. What’s more, it revoked the dev’s access to the OpenSea collection before the dev could unload any more NFTs.
So, this mint was really an embarresment for the whole team as they were looking quite unprofessional here. Can the team regain the trust of the community? No one knows. But one thing is for sure that it would be a very tedious task to do the same. Furthermore most of the twitter followers of the Kuma Boss Mint were fake which may hinder the progress of the project.
