Contract v2 — live on BNB Chain
The $PIZZA contract.
Everything that matters about $PIZZA is enforced here, not in this website. The rules are immutable, the LP recipient is hardcoded to a dead address, and the only thing the deployer can do is rename the metadata URL or walk away forever (renounce).
Contract address (BNB Chain — BEP-20)
0x6b3c9bcd59e13b2cc23d1d750187197874207ba1Immutable parameters
MAX_SUPPLY
21,000,000,000 PIZZA
USER_POOL_CAP (90%)
18,900,000,000 PIZZA
AUTO_LP_RESERVE (10%)
2,100,000,000 PIZZA (held in contract)
MINT_PER_WALLET_PER_DAY
10,000 PIZZA
DAILY_WALLET_CAP
21,000 wallets / UTC day
FEE_USD_8DEC
$0.15 in BNB (Chainlink oracle)
LOCK_DURATION
100 days per claim
VOTE_DURATION
7 days
VOTE_UNIT
100,000 PIZZA = 1 vote
MAX_VOTE_ROUNDS
5 lifetime
LP recipient
0x000…dEaD (hardcoded, burned)
Router
PancakeSwap V2
What the owner CAN do
- → setTokenURI(string) — rename the off-chain metadata JSON. Cosmetic only.
- → startEmergencyVote() — only if LP is not yet seeded and the 90% threshold isn't met. Capped at 5 lifetime rounds.
- → emergencyWithdraw(to) — one-shot, only after a passing community vote (YES > NO).
- → renounceOwnership() — walk away forever.
What the owner CANNOT do
- ✕ Mint more PIZZA (no mint function exists past 21B)
- ✕ Pause the contract
- ✕ Change the fee, daily caps, lock duration, or vote rules
- ✕ Change the LP recipient (it's a constant)
- ✕ Touch any user's escrow (capped by arithmetic, see audit)
- ✕ Blacklist wallets or freeze balances
Read the full source + AI audit
Open audit page →