Collection Landing and WIP Whitelist Funnel (Collection Landing And Wip Whitelist Funnel)

Mint is not a button — it is a sales funnel

At Bare Crypto, the CBD All-Stars surface sells a collection story first: WIP (Whitelist Immediate Purchase) opens, 750 limited spots, a ~67% discount promise, and Discord/social in one hero. The chain call is secondary; the funnel's job is trust, urgency, and wallet readiness.

Hero
  ├─ brand + #GETINTHEWIP
  ├─ supply counter (750)
  ├─ mint CTA (MetaMask-only)
  └─ social / Discord
        ↓
Roadmap → FAQ → How to mint
        ↓
Wallet ready? → mint page

This part frames the landing as a product funnel before contract detail; later parts drop into IPFS mint and reveal.

Concepts, defined where they first appear

📦 WIP
Whitelist Immediate Purchase: a limited, discounted mint window for early buyers.

📦 Supply Counter
Total supply minus minted; a live urgency signal (e.g. 750 − totalSupply).

📦 Mint Landing
Single-page React surface carrying story, funnel, and mint CTA.

📦 Wallet Priming
Preparing the user for MetaMask (or multi-wallet later) before mint.

WIP is product language, not a smart-contract feature. On-chain you usually only have price, supply, and mint functions.

What the landing sells

All-Stars and Confident Gorillas share the same skeleton: brand hero, price (0.1 ETH), WIP copy, roadmap milestones (10% / 50% / 100% WIP), and FAQ. Users read 'why now' — not the mint ABI.

Brand hero
  → WIP promise (discount + 750)
  → Roadmap rewards
  → FAQ (wallet, reveal, ownership)

Funnel steps

Typical path: Discord/social → landing → install MetaMask → fund ETH → mint CTA. FAQ answers 'which wallet?' and 'where do I see my NFT?' early, cutting support load.

Traffic → Landing → Wallet install
         → Fund → Mint CTA → Tx

ADR: split landing from mint engine

Decision: marketing surface (copy, i18n, roadmap) stays apart from mint utils. The Minter container knows quantity and contract calls; HomePage reads supply and fires the CTA. Collection copy can change without ABI blast radius.

ADR-01 Landing / Mint split
  HomePage (copy, counter, CTA)
       │
  Minter container → nftContractUtils
       │
  web3Utils / IPFS (later parts)

Failure: 'open' mint aimed at stub addresses

Early All-Stars pointed token/nft/reserve/auction at the same stub address. Landing says WIP NOW OPEN while the call hits the wrong or empty contract; the user finishes the funnel and gets a revert or nonsense state.

The mappings that get confused most often

❌ Mint landing = just a green Mint button
✓ Mint landing = story + urgency + wallet priming + CTA

❌ WIP requires an on-chain merkle allowlist
✓ WIP can be a product window; on-chain allowlist is a separate ADR

❌ FAQ can wait
✓ Wallet and reveal questions are part of the funnel; support cost dies here

A checklist for auditing your own system

1. Are brand, price, supply, and one CTA clear in the hero?
2. Which contract call feeds the 750 / remaining counter?
3. Does FAQ cover MetaMask setup before mint?
4. Does changing landing copy redeploy mint utils?
5. Can stub contract addresses leak into a production build?

What to take away from this part

1. An NFT mint product is a funnel first; the contract comes second.
2. WIP language creates trust and urgency; it can be designed apart from chain rules.
3. Landing/mint separation shrinks ABI blast radius when copy changes.

Writing WIP NOW OPEN is easy; proving the open door hits the right contract and network is the real work.