I’m building a Binance Smart Chain project that needs a rock-solid smart-contract backbone and a lightweight web/API layer around it. The scope is clear and end-to-end: Token & Core Contracts • Standard OpenZeppelin-based ERC-20 with a fixed 10 M supply. • Owner-only mint, public burn, pausability, and the usual transfer/transfer From hooks. • Ownership must be upgrade-friendly; the initial owner will be a multisig we configure later. Multi-Phase Sale Logic Eight sale phases, each with its own price and supply cap. A single buy() entry point has to accept both on-chain crypto and a bank-card rail (Stripe, Transak, or any proven provider you have used before). Phase limits must enforce caps at the contract level. Three-Level Affiliate System Users generate a referral code; L1, L2, and L3 rewards auto-accrue and can be withdrawn on-chain. Rewards are released instantly after each qualifying purchase. Light Backend & Panels • Public API that lets a web front-end handle email or wallet log-ins, wallet-connect, token balance, purchase history, and referral stats. • Admin dashboard to open/close phases, tweak affiliate percentages, and review users and their networks. Deployment & Handover You will deploy to BSC testnet first, run through a short QA round with me, then push to mainnet. I need flattened source, verified contracts, ABI files, and concise docs that let my front-end team plug in quickly. Help with the first DEX listing is expected (PancakeSwap suffices). Acceptance will be based on: 1. All contract functions behaving exactly as specified under hardhat tests. 2. Successful purchases via both crypto and card on testnet. 3. Accurate affiliate payouts across three levels. 4. Clean, commented code and a one-pager deployment guide. If you have verifiable experience shipping token sales or affiliate logic on BSC, let’s talk.