#1. The airdropped tokens were not minted as part of the collection, which is why it’s showing a mismatch of 19 tokens. These airdropped tokens were minted separate from this collection due to an error in the dapp. We can either treat these as separate tokens, or you can burn them. Please let us know how you would like to proceed.
We are still investigating the bug in the dapp and have disabled airdrops for now.
#2. Can you share a screenshot with respect to editing the collection page? I just tried to load your page and there doesn’t appear to be any issues.
after that i tried to manually from the contract 19 airdrop. My goal was to test whether it works or not. then i was not join the collection edit page again but the 19 airdrop after someone else minted 1 from manitold but opensea and my manifold mint dapp did not show proper numbers (minted count). can we fix all of counts 1,117 i got many messages people ask why the mint counts are different. people are afraid to mint right now because of this confusion.
Right now i tried to 1 publish it said deployed but mint count not fixed. but
the contract shown right now true mint count: 1,117. Still manifold mint dapp not shown true number. it says: 1,098
The count can’t be fixed because you entered the wrong information when doing the airdrop on the contract and didn’t drop on the same collection group. The way you did the “airdrop” caused 19 tokens to be minted on your contract but from a different collection (the smart contracts are structured in a way that allows for multiple collections to be created on the same contract).
Because of this, the count cannot be “fixed”. There are a few options at this point:
Burn the 19 tokens
Treat those 19 tokens as special tokens from another collection (which we would have to help you setup manually)
As for the out of sync warning, we’re going to have to investigate why that is. The fact that you directly interacted with the contract in an odd way has caused this to get out of sync.
Looks like you airdropped tokens to:
0x38a6b4daedd61d06d4df77e1354b9f1ffa60267e
That address will have to burn tokens 1098 → 1116
WARNING: By burning the tokens, these tokens will no longer exist. HOWEVER, we do not know if OpenSea’s token count will update appropriately. If you really want to check before taking these actions, try minting and burning a token on a different contract
You airdropped with an instanceId value of “1”. Your instanceId is actually ‘3851358448’ for this claim page. By airdropping with an instanceId of “1”, you technically dropped to a separate claim on this contract.
what about the burned ones? your api not read true count. but onchain reads true. what happned next? when the 2,000 pcs sold out. probably your dapp not ready all of token?? even burnt? can you handle to upload 2,000 pcs NFT + metadas for revealing on arwee.
each of my nfts are unique #1 … to #2000 you offer me burn? so i don’t have those some of tokens. when the 2,000 pcs sold out your dapp manifold can able too upload real metadas with true #numbers??
They must have transferred it out. As I mentioned, there are two ways to deal with this, have those tokens burned or treat those and reveal those separately and reveal them separately if you do not have control of these tokens.
Given that you didn’t drop them to yourself, the current best course of action is to keep the tokens and reveal them separately (we can help you create another configuration page for this if this is what you choose to do.
To keep the supply cap the ‘same’ (upper limit of 2000), drop the total mint count of your claim page to 1981. If you do this, every platform will properly show 2000 tokens minted, however the claim page will show only 1981 available to be sold.
Again, the reason this happened is because you called the smart contract directly with the wrong parameters. This can be addressed, but you’ll have to decide what course of action you want to take.
