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
Contracts, verification & launch status
Read the contract version, deployment verification, owner permissions and audit-report status. Source integration does not mean sales are open.
Navigation
BATTLE TOWN / PDF
Smart contract source audit
Know what powers your purchase. Explore the contract source and the audit report in one place.
Explore contract sourceSee the PDF report and its scope in Security.
Payments go directly to the treasury. The contract has no minimum funding threshold and no purchase refund mechanism.
Whitepaper v3.4 · f480d76ff95e ·
7990a8a2f26d289ef24a28b7aabfae624ab5bdd6e8ef1ca146e118a68f027143Solidity · ZIP ↓SHA-256 · JSON ↗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.