Mints exactly 300,000,000 BTOWN once to one constructor recipient
No additional mint, owner, transfer gate, or contract-level pause
Allocation constants do not create eleven separate token balances
BATTLE TOWN
BTOWN supply, allocation & vesting
Review the 300M BTOWN supply, eleven allocation buckets and vesting schedules. Distinguish allocation constants from contract custody.
Navigation
300M BTOWN distribution
Whitepaper v3.4 pins a single 300,000,000 BTOWN constructor mint and eleven allocation constants. Liquidity is 10M Initial Liquidity plus 20M Liquidity Reserve. Most buckets are numeric canon rather than contract-level custody controls.
Three contract-enforced vesting schedules complete at months 10, 16, and 22. Official tournament creation is separated by at least 60 days; there is no quarterly guarantee. Winner and random-player reward legs transfer in full when settled, with no one-third monthly tranches. Community fees nominally resolve to 95% winner, 1.5% NFT epoch, and 3.5% Treasury, subject to integer rounding and epoch-opening conditions.
The Solidity constants split liquidity only into 10,000,000 BTOWN Initial Liquidity and 20,000,000 BTOWN Liquidity Reserve. No contract in this source set deploys liquidity, locks these balances, or enforces a release schedule, DEX/CEX split, market-making sleeve, or raise-derived formula.
Allocation values are numeric canon, not a complete custody map. The Token constructor mints all 300M once to one recipient; TEAM is capped by Vesting, and the reference deployment funds RewardsVault with 80M. The contracts do not enforce a presale-proceeds budget. Presale finalization routes unsold inventory above locked liabilities to RewardsVault.
Official Whitepaper (PDF)A smart-contract core
Whitepaper v3.4 is aligned to immutable source-set SHA-256 7990a8a2f26d289ef24a28b7aabfae624ab5bdd6e8ef1ca146e118a68f027143. The catalog includes the deployable Presale. Mainnet deployment (chain ID 56) is published separately below; the whitepaper remains the immutable source reference. The presale panel reads the current sale status from the contract.
BNB Smart Chain · Mainnet · Chain ID 56
Security
The source set uses OpenZeppelin ownership and reentrancy primitives. It has no contract-level emergency pause, proxy, upgrade path, or on-chain multisig requirement. Operational authority remains concentrated in owners, granters, operators, and organizers.
See the PDF report and its scope in Security. The report reviews source code; deployed bytecode and live settings are outside its scope. Current contract addresses are listed on the presale page.