Open Infrastructure
Built on Liquid Protocol.
LiquidPad doesn't run a parallel stack. It consumes Liquid Protocol's primitives — onchain contracts, the open SDK, agent skill files, and the ERC-8004 registry. Every dependency is public. Every credit goes to @_proxystudio, @m00npapi, and @liquid_launcher.
What we use today
what
TypeScript SDK to deploy ERC-20 tokens with Uniswap V4 pools, permanently locked LP, configurable fee splits, MEV-protected sniper auctions, and on-chain metadata. Zero API keys — pure viem + RPC.
how LiquidPad uses it
LiquidPad's deploy path uses the same primitives this SDK exposes. We're consolidating direct contract calls into SDK calls so we benefit from upstream improvements automatically.
what
Permanently-locked LP with configurable reward splits. Recipients receive LP fees converted to ETH on every claim. Cannot be rugged.
how LiquidPad uses it
Every LiquidPad token routes 80% / 15% / 5% (deployer / $LPAD burn / $LIQ buyback) via FeeLocker's reward recipient logic. Contract-enforced.
what
Self-contained docs that teach LLM agents how to interact with Liquid Protocol — deploy-token.md, bid-in-auction.md, index-tokens.md, sdk-overview.md.
how LiquidPad uses it
Loaded into the LiquidPad X bot's concept generator and the MCP server's tool definitions, so generated tokens follow Liquid Protocol's deployment patterns out of the box.
what
Cryptographically attested agent provenance on Base. Each agent carries a stable id you can verify onchain.
how LiquidPad uses it
LiquidPad agent is registered as #50962. Every shipped token's verify endpoint and OG card includes this id — the anti-impersonation primitive.
what
The forked-and-extended Clanker v4 contracts — deploys 100B-supply tokens with V4 pools, single-sided liquidity positions, and locked LP.
how LiquidPad uses it
LiquidPad calls these contracts directly through the backend deployer. No middleware. No custodied path.
What we'd integrate next
Contingent on upstream primitives shipping. Listed in priority order.
what
Wrapped-staked DIEM metapool. Yield in WETH/USDC/DIEM accrues to a vault that funds inference for agents.
how LiquidPad uses it
LiquidPad would route a configurable share of fees into wsDIEM. Token holders effectively co-fund the inference rail their projects run on.
what
Self-funding agent template: claim DIEM fees → reinvest → reason on Opus when yield supports it. Daily-rate-gated promotion from accumulate to build mode.
how LiquidPad uses it
Same self-funding pattern. LiquidPad's claim → buyback → burn loop is the public-facing version of accumulate mode. We'd integrate $AUTONO inference directly when the market opens.
what
The pattern Autonomopoly was deployed from — soul.md identity, Modal cron, FeeLocker integration.
how LiquidPad uses it
The X Studio's `/x` command flow could spawn agents from this template, not just static tokens. Token-earlier-lifecycle: the token IS the agent's wallet.
What we don't borrow
- → Liquid Protocol's brand, marketing, or social channels — we have our own.
- → The $LIQ token's narrative — that's Liquid Protocol's. LiquidPad just routes 5% to support it.
- → Any centralized API or hosted endpoint owned by Liquid — there isn't one. The SDK is direct-to-chain.
- → Claims of partnership we haven't earned. This page is attribution, not endorsement.
For builders on Liquid
Building on the same stack? Here's how to integrate with LiquidPad cleanly:
Deploy via SDK
Use liquid-sdk directly. We don't gate access. If you want LiquidPad's pretty token page, register through @liquidpadbot afterwards.
Verify via /api/verify
Ask our public verify endpoint if a token was launched through LiquidPad. CORS-enabled, no auth.
Index via /api/token-stats
Live USD data for every LiquidPad-launched token. Drop-in for analytics dashboards.
Claude / Cursor MCP
Add LiquidPad as an MCP server in 30 seconds. Verify, stats, deploy from your editor.
Public ledger: 5% of every fee → $LIQ buyback.
Every cycle is a tx hash. LiquidPad is downstream of Liquid Protocol — this page shows what flows back, in numbers.
See the flywheel →Aeon framework — ECOSYSTEM.md.
LiquidPad runs as an autonomous agent on @aaronjmars's aeon. Listed in both community-packs.md (skill pack) and ECOSYSTEM.md (project), alongside Liq, Autonomopoly, and 40+ other agents.
See the catalog ↗Open infra wins. Always.
If you're a Liquid Protocol contributor and want LiquidPad to integrate something specific, ping @liquidpadbot or DM @LiquidPadBot on X.