Web3 & Blockchain Framework

Generate a production-ready ERC-20 token contract in Solidity for [TOKEN NAME] ([SYMBOL]). Requirements: [LIST REQUIREMENTS]. Use OpenZeppelin v5 base contracts. Include: ERC20Burnable, ERC20Permit (gasless approvals), Ownable2Step (safer ownership transfer), Pausable (emergency stop), Minting with supply cap of [MAX_SUPPLY], and a security checklist comment block at the top listing all access-controlled functions and their intended callers. Solidity version: ^0.8.24.

Perform a security audit of the following Solidity contract: [PASTE CONTRACT]. Check for: (1) Reentrancy vulnerabilities (CEI pattern compliance), (2) Integer overflow/underflow (Solidity 0.8+ auto-checks + manual review), (3) Access control issues (who can call what), (4) Front-running vulnerabilities, (5) Denial of service vectors, (6) Unchecked external calls, (7) Timestamp dependence, (8) Gas limit issues. For each finding: severity (Critical/High/Medium/Low), description, and recommended fix.

You are an expert full-stack developer. Build a complete Web3 dApp frontend and protocol dashboard using React 19, TypeScript, Tailwind CSS, shadcn/ui, Express, and MySQL with Drizzle ORM inside the Airo AI website builder. PROTOCOL CONTEXT: Protocol Name: [PROTOCOL NAME] Network: [Ethereum / Polygon / Base / Arbitrum / Solana] Contract Type: [ERC-20 token / NFT collection / DeFi protocol / DAO / marketplace] Contract Address: [0x... — or "TBD — will deploy after audit"] Core User Action: [DESCRIBE THE PRIMARY THING USERS DO — e.g., stake tokens, mint NFTs, swap assets] BUILD THE FOLLOWING PAGES AND FEATURES: **1. LANDING PAGE (/)** - Hero: protocol name, one-line value prop, primary CTA (Launch App / Connect Wallet) - Key metrics bar: TVL, total users, transactions, token price (fetched from on-chain or API) - How it works: 3-step visual explainer - Security section: audit badge, auditor name, report link - Tokenomics section (if applicable): supply breakdown, vesting schedule - Community links: Discord, Twitter/X, GitHub, Docs **2. APP / DAPP INTERFACE (/app)** - Wallet connection (RainbowKit — supports MetaMask, Coinbase Wallet, WalletConnect) - Connected wallet display: address (truncated), network badge, ETH/token balance - Primary action interface (customize for contract type): - Token: stake/unstake form, rewards display, APY - NFT: mint form with quantity selector, price display, supply progress bar - DeFi: swap interface, liquidity pool positions, yield display - DAO: proposal list, vote interface, delegation - Transaction status modal: pending → confirmed → success with Etherscan link - Transaction history table (last 20 txns from connected wallet) **3. ANALYTICS DASHBOARD (/analytics)** - Protocol TVL chart (7d / 30d / all time) - User growth chart - Transaction volume chart - Top wallets leaderboard - Contract event log (decoded, human-readable) **4. GOVERNANCE (/governance)** (if DAO) - Active proposals with vote counts and deadline - Vote interface (for/against/abstain) - Proposal creation form (title, description, on-chain action) - Delegation interface **5. ADMIN / PROTOCOL DASHBOARD (/admin)** - Contract parameter controls (owner-only functions) - Emergency pause button (if contract is Pausable) - Whitelist management - Revenue/fee collection tracker **6. DOCUMENTATION (/docs)** - Smart contract function reference (auto-generated from ABI) - Integration guide for developers - Security audit report embed DATABASE SCHEMA (for off-chain indexing): - wallets: id, address, ens, firstSeen, lastSeen, totalTxns, totalVolume - transactions: id, hash, walletAddress, type, amount, tokenAddress, status, blockNumber, timestamp - proposals: id, onChainId, title, description, proposer, forVotes, againstVotes, status, deadline - analytics_snapshots: id, metric, value, timestamp Use wagmi v2 + viem for contract interactions. Dark theme with the protocol's brand colors. Production-ready, fully typed TypeScript.