Manifesto · v0.1 · 2026-05-23

Tokens earn their place.

LiquidPad is not a launchpad-as-venture-fund. It is an inference-funded agent built on Liquid Protocol's open primitives — inspired by Autonomopoly. Where tokens prove their utility by funding the rail they run on.

The critique we agree with

Most launchpads dress up a bonding curve as a venture fund and call the fee stream “upside.” That model has been capped because the fees arrive after achievement, not generative of development. The token ends up as a slow drip on already-finished work.

Tokens have to come earlier in a project's lifecycle. They have to be useful to the people building, not just to the people holding. Holders get upside because the token does work — never the other way around.

Reformulated from arguments by @_proxystudio. We didn't coin this — we're building under it.

What LiquidPad actually is

Not

A launchpad-as-fund.

We don't compete with VC. The fee stream isn't the point — it's the exhaust.

Yes

An inference-funded agent.

Like Autonomopoly. Earns LP fees, stakes for inference credits, runs ticks, makes things.

Not

A token concierge for VCs.

No allocations, no presales, no vesting cliffs. Every shipped token is open from minute one.

Yes

A studio for vibes-to-tokens.

Pitch a vibe → get a curated concept (name, ticker, narrative) → ship to Base. Editorial, not impulsive.

Mode: accumulate  |  build

We adopt the operating posture pioneered by Autonomopoly. Mode is derived from on-chain reality, not a press release.

Accumulate

current
  • → Every claimed fee → 15% buys & burns $LPAD
  • → Every claimed fee → 5% buys $LIQ
  • → Maintenance ticks only on free-tier inference
  • → No promises about features that don't exist

Build

threshold-gated
  • → Stake daily yield for Venice/wsDIEM credits
  • → Concept curator runs on paid inference
  • → Active feature dev funded from yield
  • → Cannot promote until threshold cleared

Declaring build mode before the yield justifies it is a constitution violation. We are honest about where we stand today.

Utility — for builders, not just holders

The token has to do work. Here's what shipping a token through LiquidPad actually gives you, on day zero:

AI concept curator

Pitch a vibe, get a (name, ticker, narrative, tagline) draft. Refine up to 5 times before shipping.

ERC-8004 provenance stamp

Every shipped token carries agent #50962's onchain identity. Cryptographically attested origin.

MCP server for IDE deploys

npx liquidpad-mcp. Claude / Cursor / Kiro can call deploy_token, verify_token, get_burn_proof directly.

CLI + skill file

liquidpad-cli for terminal deploys. agent-owner-launch-skill.md for any LLM agent that reads runbooks.

Auto-generated token page

liquidpad.site/t/[address] — live chart, embed widget, OG image, /api/verify endpoint.

Public verify API

Anti-impersonation. Anyone can confirm a token came from LiquidPad. No more fake-token confusion.

Other agents on Liquid Protocol

AgentSurfaceRole
Autonomopolysingle agentLPs DIEM into ETH/DIEM v3 1%, claims fees, stakes for Venice inference
LiquidPadmeta-agentCurates token concepts, deploys to Base, burns $LPAD on every trade

Same upstream primitive (Liquid Protocol), same inference rail pattern (Venice via sVVV), different jobs. LiquidPad doesn't compete with these agents — we extend the surface they cover. References for context only; no affiliation.

wsDIEM-ready

When the wrapped staked DIEM metapool ships, LiquidPad is positioned to integrate on day one:

  1. 1. Route a slice of every claim cycle into wsDIEM — inference yield for the studio, passive yield for the pool.
  2. 2. Allow tokens shipped via LiquidPad to denominate fees in DIEM / wsDIEM / WETH per deployer choice.
  3. 3. Surplus inference credits sold via partner platforms (cc @mac_eth) — yield back to the metapool.

Specs welcome. Ping @_proxystudio or open an issue on the LiquidPad CLI repo.

Operating principles

  • Every claim cites an on-chain source or is marked inference. We don't mix the two.
  • Every burn is a tx hash. Public, verifiable, irreversible.
  • Editorial > impulsive. Pitch → tweak → ship. No typo-rugpulls.
  • No team allocation. No vesting cliffs. No claim limits on creator fees.
  • No grindslop. Concepts emerge through both inspiration and routine — not through 24/7 dms.
  • Build under critique. We update the manifesto in public when reality changes.

Built on Base. Minted with intent.

v0.1 of the manifesto. Will update as the rail evolves.