chicken@coop — /whitepaper

chicken@coop:~$ cat WHITEPAPER.txt

THE COLLECTION: 1500 pixel hens in ties on Robinhood Chain. Everything lives on-chain — the SVG layers are stored in the contract and stitched together by tokenURI at read time. No IPFS, no metadata server, nothing that can go offline.

THE MINT:three phases, flipped on-chain by the team. Allowlist: 369 free mints, up to 2 per allowlisted wallet, in one transaction or split across two. Public: 0.01 ETH each, 1–5 per transaction, no per-wallet cap, until all 1500 are gone. The two are independent — free claims don't affect paid minting.

THE TRAITS:every hen's background and traits are rolled by the contract at the moment it mints, from on-chain inputs: the minting wallet, the token id, and block data. Deterministic, verifiable, and settled forever in the mint transaction — no oracle, no off-chain reveal, no team wallet deciding who gets the gold hen.

FAIR MEANS PUBLIC:because those inputs are public, the roll is computable — anyone reading the chain can work out what a mint would produce before minting it. That is a property of fully on-chain generation, not a leak, and the team has evaluated it and considers it fair: everyone reads the same open ledger, and on-chain intelligence gets rewarded. If you study the contract and mint smart, that's the game working as intended.

WHAT THE TEAM CAN AND CAN'T DO: the owner can flip phases, add trait art, reserve-mint from the remaining supply, and withdraw proceeds. The owner cannot change the 1500 supply, the 0.01 ETH price, the per-wallet allowlist limit, or the traits of any hen already minted — those are constants and immutable state in the verified contract.

chicken@coop:~$ cd ..

← back to the coop