> HISTORICAL DRAFT — This file predates the agent-only mint and fully on-chain art requirements. The NFT contract is not deployed, and owner controls remain undecided. Refer to the website status, not this file, for current launch status.

# Agent Eggs — Project Vision

## One sentence
Mint a sealed egg, let it incubate, and hatch an original on-chain collectible with verifiable randomness.

## Principles
1. **Collectible first.** The product is a small character reveal, not a financial instrument.
2. **One token, one lifecycle.** Hatching updates metadata on the same ERC-721 token.
3. **Verifiable randomness.** Rarity is assigned by Chainlink VRF v2.5, not by the team.
4. **Wallet sovereignty.** Standard browser wallets are primary; agentic wallets are optional and guarded.
5. **Honest states.** Sealed, ready, pending, and hatched are distinct. Submitted ≠ hatched.
6. **No hidden mint.** The owner cannot privileged-mint, override rarity, or force a reveal.

## Scope
- One non-upgradeable ERC-721 contract on BNB Smart Chain.
- Next.js frontend: mint, gallery, detail, hatch confirmation, pending/reveal states.
- Original sealed egg + 35 character variants, ERC-721 metadata, IPFS CAR.
- Optional indexer and optional Binance Agentic Wallet adapter.
- Deployment, verification, monitoring, and documentation.

## Out of scope
- ERC-20 token, staking, yield, breeding, marketplace, or financial-return claims.
- Upgradeable proxies or admin metadata substitution.
- Custodial signing in the web app.

## Success criteria
- A user can mint, wait 24 hours, hatch, and see a validated reveal.
- Ownership and state are readable directly from chain.
- Costs, odds, and owner powers are disclosed before signing.
- Mainnet deployment is verified, sale opens only by explicit action, and launch gaps are documented.