PROJECT: BMC ILLUMINATI PASS — 500 NFT COLLECTION

Build a complete, production-ready Ethereum ERC-721 NFT collection with an immutable BMC token-burning mint mechanism, secure random assignment, and a responsive mint website.

COLLECTION

Name: BMC Illuminati Pass

Symbol: BMCPASS

Network: Ethereum Mainnet

Total supply: exactly 500 NFTs

Website name: bmc-pass

BMC TOKEN

Contract: 0x38224239f2BDae357D47cb864BC533d7f72dF961

Verify the deployed BMC token's decimals, burnFrom implementation, and allowance behavior before deployment. Use 18-decimal units only after confirming the token's decimals.

MINTING PHASE 1 — FIRST 40 GENESIS

The first 40 successful mints must be Genesis NFTs.

Mint price: 1,000,000 BMC each, permanently burned through burnFrom.

Mint #1:

• Token ID 1
• Genesis artwork genesis-01.png
• Legendary Genesis rarity
• The rarest NFT in the entire collection
• Guaranteed to the first successful minter

Mints #2–40:

• Token IDs 2–40
• Genesis artworks genesis-02.png through genesis-40.png
• All have Genesis rarity

Enforce strict sequential allocation of token IDs and artwork for the first 40 mints.

MINTING PHASE 2 — RANDOM MYSTERY MINT

After the first 40 successful mints, open the remaining 460 mint positions.

Mint price: 350,000 BMC each, permanently burned through burnFrom.

Remaining inventory:

• 37 Genesis NFTs with artworks genesis-41.png through genesis-77.png
• 423 Standard NFTs with fully on-chain SVG artwork

Randomly distribute these 460 outcomes without replacement.

Every mystery mint must receive exactly one outcome, either Genesis or Standard.

Use Chainlink VRF v2.5 or a comparably secure verifiable randomness solution. Do not derive outcomes from block.timestamp, blockhash, prevrandao alone, or user-controlled values.

All 37 remaining Genesis and all 423 Standard outcomes must be assigned exactly once by full mint-out.

Each buyer pays the same 350,000 BMC mystery-mint price regardless of the result.

MINTING AND TOKEN IDS

Use token IDs 1–500 in global mint order.

For token IDs 41–500, do not infer Genesis or Standard rarity from token ID. Store the randomly assigned tier and artwork identifier separately.

Mint one ERC-721 NFT to the buyer per successful mint.

For VRF-based mystery mints, mint a pending-reveal NFT after the BMC burn, then finalize its tier and artwork after verified randomness is fulfilled.

No user or administrator may reroll an outcome or select a specific mystery artwork.

ARTWORK — GENESIS

Use exactly 77 unique square PNG artworks, minimum 1024x1024, named genesis-01.png through genesis-77.png.

All Genesis artworks feature the same original mysterious cartoon frog in a black hooded cloak, premium gold-and-black styling, glowing golden third eye, and floating golden eye-in-triangle.

Genesis #1 must be visually the most exclusive, with its own unique Legendary attributes.

All artwork is original. Do not copy Pepe the Frog or any existing character.

Genesis artwork location: ipfs://[IMAGES_CID]/genesis-NN.png

The Genesis directory CID must be finalized and hardcoded before mainnet deployment. Do not deploy with a placeholder CID.

ARTWORK — STANDARD

Generate exactly 423 distinct Standard NFT artworks fully on-chain as SVG.

Use an original cartoon frog in a dark hooded cloak, with:

• 6 backgrounds
• 5 cloak variations
• 6 eye variations
• 5 symbols
• 6 accessories

Guarantee unique combinations for all 423 Standard NFTs.

Standard NFTs must never contain the Genesis-exclusive golden third eye, floating golden eye-in-triangle, or golden cloak.

METADATA

Generate on-chain JSON metadata through tokenURI.

Include:

• NFT name
• Description
• Tier: Legendary Genesis, Genesis, or Standard
• Artwork identifier
• Relevant visual attributes

For pending mystery NFTs, return neutral pending-reveal metadata that does not disclose the future outcome.

Once assigned, the NFT metadata and artwork must be permanent and immutable.

SMART CONTRACT SECURITY

Use audited OpenZeppelin ERC721, Base64, Strings, and ReentrancyGuard libraries where appropriate.

Use the verified BMC burnFrom method after exact allowance approval.

Prevent reentrancy, duplicate assignments, excess minting, and incorrect burns.

Track total BMC burned through this NFT contract.

Use a gas-bounded random-without-replacement algorithm.

Map every VRF request to its pending NFT.

Support concurrent pending mystery mints, out-of-order VRF fulfillments, and permissionless finalization of stored randomness.

Define a safe handling procedure for unavailable randomness that does not permit rerolls or manipulable fallback randomness.

No owner minting, privileged artwork assignments, metadata changes, price changes, contract upgrades, or administrator withdrawals.

If Chainlink VRF requires a subscription manager, disclose those operational permissions and dependencies. Do not falsely describe a system with privileged VRF configuration as fully permissionless.

Provide ownerOf(), tierOf(), supply counters, remaining mystery inventory, and totalBurned().

WEBSITE — BMC-PASS

Build a responsive mint website with:

• MetaMask and Rabby wallet connection
• BMC balance and allowance display
• Genesis mint button for the first 40
• Mystery mint button for the remaining 460
• Current mint price and remaining supply
• Total BMC burned counter
• NFT preview gallery
• Genesis #1 Legendary showcase
• Pending-reveal status for mystery mints
• Transaction links to Etherscan
• Clear explanations of Ethereum gas and VRF reveal delays

Do not promise fixed odds after the mystery phase begins. Show odds based on the remaining inventory, or explain when outstanding pending reveals make those odds provisional.

TESTING AND DELIVERY

Provide complete Solidity source code and Foundry tests.

Test:

• First minter receives Legendary Genesis #1
• Mints 2–40 receive Genesis #2–40
• Phase 1 costs exactly 1,000,000 BMC
• Phase 2 costs exactly 350,000 BMC
• Exactly 77 Genesis and 423 Standard NFTs exist at full mint-out
• Random assignment without replacement
• Out-of-order VRF fulfillment
• No duplicate artwork
• BMC burn and allowance failures
• Reentrancy protection
• Metadata correctness
• Full 500-mint simulation
• Maximum BMC burned equals 201,000,000 BMC

Deliver:

1. Solidity source code
2. Foundry tests and execution results
3. GitHub repository or pull request
4. Independent security review findings
5. Ethereum deployment instructions
6. Mint website source code

IMPORTANT: Run the IMD free check first. Report blockers, including missing artwork CID, BMC incompatibility, VRF configuration, or unavailable image-generation capabilities.

Do not deploy to Ethereum mainnet, pay service charges, or request token approvals until I explicitly authorize those actions after review.

Transfer rules: Standard ERC-721 transfers. NFTs are freely transferable with no transfer fees, blacklist, or transfer limits. BMC tokens are burned only when minting, not when transferring NFTs.