Questions about multi-stage ERC-721 blind mint flow

Manifold Support Questions
1

Hello! I’m preparing an ERC-721 collection (~300 items, 2 rarities defined in metadata) and I’ve read the documentation, but I still have a few questions before starting the deployment:

  1. Main phase: blind free mint for allowlist (~150 wallets, 1 each).
  2. Before this phase, I’d like to mint a few specific rare items (~10) to the contract owner’s wallet (for gifting later). Is this possible via batch mint?
  3. Reveal = just metadata update, correct?
  4. Last phase: public mint for the remaining items. After reveal all items are visible, but minting is still “blind” (buyers can’t choose which specific token), right?

Thanks a lot for clarifying, I would appreciate any help!

2

gm! Looks like you’ll be creating an edition page with different phases.

  1. What is the question?
  2. You can airdrop from the edition page. (This will add to the mint totals) Batch mint allows you to mint tokens to the same contract but wouldn’t add to the supply of the drop from the edition page.
  3. Correct
  4. Are you looking to do separate reveals? So reveal the first 150 and then reveal the public one after? Once you do the reveal you can configure however you like, this could mean updating the CSV as you go or in different phases.

Let me know if this answers your questions!

1 Like
3

gm lyndo! Thank you for the quick response!

  1. Oh, my bad — there was no question there, just a statement.

  2. What I need is to send ~10 specific rare items to the owner’s wallet before the blind free mint phase. I found this article: How do I airdrop tokens from my Edition page? | How can we help?, but I couldn’t figure out if it’s possible to select specific token IDs with that method. That’s why I thought I might need to batch-mint those items first and then create the edition page.

Or, if I make those items the very first entries in the CSV, will the airdrop assign those exact tokens? :thinking:

  1. Thanks!

  2. I’d prefer to have a single reveal after the blind mint phase and before the public mint, so public-phase collectors can see the actual items instead of placeholder. Am I correct in understanding that even after the reveal, public mint collectors would still be assigned a random token from the remaining supply, and wouldn’t be able to choose a specific token ID to mint?

I hope my questions aren’t too stupid :sweat_smile: just trying to be sure I can set everything up correctly before I start building the contract. Thanks so much for your help!

4
  1. You can airdrop the first entries to yourself. I think this will probably make the most sense as the tokens will be part of the Edition Page flow. (It’s up to you as both methods work) In the end it will be on the same contract.
  2. A single reveal is fine - The way the blind mints work right now, it is possible if someone were to dig into the code to try to predict the randomness. But the collector cannot choose which token ID to mint, only the next one.

The questions are great! Feel free to ask away.

1 Like
5

Thanks a lot! :folded_hands: Just to confirm:

  1. My task is to put the specific rare items at the very top of the CSV.
  2. The “randomness” just means collectors don’t know which ID is coming next, since minting is always sequential
  3. So technically I could even place all the rare items within the first 150 rows, and then they would all be minted during the blind mint phase, right?