Closed uohoo closed 2 years ago
Encountering the same issue. Has anyone figured this out?
It reproduces for me too. If I figure it out on my own I'll text back.
Hey 👋
Have you found any news or workarounds ?
Same issue too.
Is nobody going to pick this up?
I see that someone fixed it, but it requires approval: https://github.com/metaplex-foundation/metaplex/pull/1589
Same issue, anyone has idea what is wrong here? Is there a workaround?
Hello, any news about this critical issue ?
When we disabled candy machine v1, this also broke the Candy Machine option with gumdrop. We need to improve our documentation and make a better UI to allow using gumdrop with the whitelist mint option of Candy Machine v2.
In the meantime, you can make a whitelist mint for Candy Machine v2 (guide to this in our docs) and then airdrop the whitelist token using Gumdrop.
encountering the same issue
After following the documentation: NFT Candy Machine Pre-sale The workflow for a Candy Machine pre-sale through the Gumdrop program is as follows:
CLI instruction used: ts-node src/gumdrop-cli.ts create -k ~/.config/solana/devnet.json --claim-integration candy --candy-config 39Uaw6YtadW7s6jeJTm5WUmpyeYhqkvuN8oHYHDpfAoJ --candy-uuid 39Uaw6 --distribution-method wallets --distribution-list gumdrop.json
The --keypair is the address used to upload the candymachine and the config is what i get in .cache folder when uploading.
Is it possible setting a whitelist directly to a candymachine already created? What's the way to get it?