MemePad
Solidity Developer · Launchpad Engineering
https://memepad.io ↗Challenge
MemePad is a multi-chain launchpad focused on meme-token launches — a market segment that combines high transaction volume, intense bot competition, and a user base that is mostly non-technical retail.
The engineering pressure on a meme-token launchpad is different from a serious DeFi protocol. The bugs that matter aren't subtle reentrancy variants; they're things that get exploited in the first 30 seconds after a launch: bot snipers buying the entire supply, MEV searchers sandwiching the first hundred buyers, fake "launch successful" UIs draining wallets via approval phishing.
The launchpad contracts have to deal with all of that while supporting non-technical creators who don't read documentation and will deploy whatever default they get. Sensible defaults are not a polish item — they are the security model.
Approach
Work across the launchpad core — fairlaunch flows, anti-bot modules, and the liquidity-lock plumbing wired into every new token launch.
Approach: lean defaults, hard guardrails.
**Anti-bot mechanics by default.** Every new meme-token launch ships with a configurable cooldown between buys, max-wallet caps for the first N blocks, and a blacklist-on-block-N mechanism that locks out any address that bought in the literal first block (which is almost always a sniper bot). Project creators can disable these, but they have to opt out, not opt in.
**Liquidity locked at deploy.** The contract creator does not get to choose whether to lock LP. The fairlaunch flow locks LP for a minimum window automatically; reverting the lock requires the deployer to wait out the window. This kills the most common rugpull pattern (deploy, attract liquidity, withdraw LP, dump tokens).
**Approval-aware UIs.** Launch flow front-end never asks for an "unlimited" token approval. Approvals are exact-amount and one-time per buy. This prevents the most common phishing pattern on meme launches: trick a user into a max approval, then drain via a malicious router later.
**Multi-chain consistency.** Same contract semantics on every supported chain. A user who learns the launchpad on BNB Chain can use it on Ethereum, Polygon, or Base without surprises. Chain-specific behavior is abstracted in deployment scripts, not in business logic.