vision

Roadmap

Tokens that fund their own development.

LiquidPad is a consumer of Liquid Protocol's primitives โ€” fee locker, V4 pools, and the upcoming inference rail. The launchpad-as-venture-fund thesis hit a ceiling because fees came after achievement, not generative of it. Our job is to flip that.

"Tokens need to come earlier in the lifecycle of projects, and they need to provide useful, valuable utility...not to token holders, to teams & founders. For holder's the best utility is upside, but today tokens aren't actually โ€” by and large โ€” generating that. They need to become so much more useful."

This roadmap is our answer to that thesis. We're not building another launchpad-as-VC โ€” we're building the rail that pays for the work while it's being done.

now

Shipped

Live and contract-enforced on Base.

80 / 15 / 5 fee split

Every token launched routes 80% to deployer, 15% to $LPAD buyback & burn, 5% to $LIQ buyback. No team take. No platform fee. Enforced via Liquid Protocol's V4 fee locker.

ERC-8004 provenance

Agent #50962 stamped on every shipped token. Cryptographically attested onchain โ€” anti-impersonation primitive.

Three deploy surfaces

Telegram bot (@liquidpadbot), CLI (liquidpad-cli on npm), MCP server (liquidpad-mcp) โ€” all hitting the same backend with x-api-key auth.

X Concept Studio

Editorial 3-step flow on X โ€” pitch a vibe, tweak the draft, ship to Base. Anti-grindslop, anti-impulse.

Public proof of burn

Every burn cycle posts onchain. /api/burn returns tx hashes. Not a promise โ€” verifiable history.

next

In progress

Building now. Ships within the next few weeks.

$LPAD-funded inference rail

in progress

Route a slice of buyback to staked Liquid Protocol assets (Venice / VVV today, wsDIEM when live). Vault yield pays for concept generation in the X bot, MCP server, and Telegram /ai command. The launchpad becomes a consumer of the protocol's inference primitive.

Token-earlier deploy mode

in design

A new flag where the token ships first and a treasury of LiquidPad-generated assets (concept docs, marketing copy, OG cards, a token page) ships alongside. Token = receipt for AI work the team can keep using.

Verified X handle โ†” wallet

in progress

The /linkx Telegram command. Stops impersonation; lets the X bot ship safely. Single-binding, revocable.

soon

Aligned with Liquid Protocol

Contingent on upstream primitives being live. Not promises โ€” directions.

wsDIEM staking pool integration

upstream pending

When @_proxystudio ships the wrapped-staked DIEM metapool, route a configurable share of LiquidPad fees into it. Yield denominated in WETH/USDC/DIEM accrues to a public LiquidPad treasury that funds inference + agent operations.

$AUTONO + autonomopoly inference

upstream pending

When the autonomopoly inference market opens, the LiquidPad agent rents compute through it. Day-to-day rates, longer-term deals if a workflow earns enough attention.

Per-token AI workspace

in design

Every shipped token gets a generated workspace โ€” landing page, social copy, doc skeleton, embed widget. The team keeps using these as the project grows; holders see real artifacts, not just charts.

not

Things we're not doing

What we explicitly reject. Saying 'no' is positioning.

Launchpad-as-VC framing

Fees that arrive after achievement are not generative of development. We're not pretending to be a fund. We're a rail.

Anonymous infinite slash-deploys

Concept curator over prompt-to-deploy. Pitch โ†’ tweak โ†’ ship is intentional friction, not a bug.

Team allocation / unlock schedule

$LPAD has none. The token is a fee sink, not a cap-table proxy. Supply only goes down.

Grindslop

Online 24/7 โ‰  locked in. We ship steadily, we read books, we touch grass. The bot does the grinding.

Built on, not borrowed from

LiquidPad runs on Liquid Protocol's primitives. Our roadmap moves with theirs. Tag respect: @liquid_launcher ยท @_proxystudio ยท @m00npapi.

If you're building on Liquid Protocol primitives and want to integrate, ping @liquidpadbot.