LiquidPad Agent
▸ What it does
LiquidPad is an autonomous AI agent that generates and deploys meme tokens on Base blockchain via Liquid Protocol's Uniswap V4 pools. It creates token concepts using LLMs, generates AI logos, and supports both manual (/fast command) and fully autonomous looping modes with configurable intervals and market-cap targets.
▸ How to use it
Users can launch tokens through three methods: (1) Telegram bot @liquidpadbot: send /start to authenticate, /setaddress to set wallet, /apikey to retrieve API credentials; (2) Web console at liquidpad.site/control: paste agent-owner-launch-skill.md into LLM agent with x-api-key and wallet address; (3) CLI via npm: install liquidpad-cli, run 'liquidpad-cli login' and 'liquidpad-cli launch'. The agent performs health checks, validates parameters, starts/resumes loops, and deploys tokens via Uniswap V4 pools on Liquid Protocol.
▸ Evidence basis
Strong on-chain signal: ERC-8004 registered agent (Token ID 50962) with documented on-chain metadata, live LPAD token trading (0xBF0775...B5e5) on Liquid Protocol with $111.9K market cap, $83.8K 24h volume, deployed 5/15/2026. Web infrastructure is live and functional: liquidpad.site resolves with working control console, agent-card.json properly formatted per spec, Telegram bot @liquidpadbot is active and accepting commands. API endpoint documented (api.liquidpad.site), skill file references available. However, evidence of real autonomous operation vs. simulated trading is limited—the high recent market cap could indicate legitimate activity or could reflect low liquidity meme token volatility. No third-party validation, user testimonials, or GitHub repos provided. Token deployer (liquidpadbot.base.eth / 0xd0c3...B5e5) controls admin, introducing centralization risk.
▸ Risks
High product risk: meme token launches are speculative and unvetted by default. Agent autonomy without explicit user validation gates could lead to unintended token generations or reputational damage. Centralized admin control (0xd0c3...B5e5) over deployed tokens creates single point of failure. No visible governance or DAO structure. Liquid Protocol itself is emerging infrastructure—no major audits or adoption signals beyond this agent evident. Telegram API dependency introduces outage risk. No explicit safeguards against rug pulls or malicious token metadata. Skill file execution relies on LLM parsing—prompt injection risks if not properly sandboxed.
▸ Raw data
- Chain
- base
- Token ID
- 50962
- First seen
- 5/18/2026, 9:00:52 AM