Liqpad documentation · Beta
A practical reference for creators, traders, developers, researchers, and anyone evaluating Liqpad. Contracts remain the source of truth; this guide explains how the pieces fit together.
Start here
Liqpad is a permissionless B20 launchpad on Base. A creator can publish token metadata, create a fixed-supply B20, initialize its VVV market, and lock the launch liquidity position through one guided transaction.
The invariant
Every Liqpad launch uses a B20/VVV Uniswap v4 pool, fixed initial supply, single-sided launch liquidity, and a locked position. The web never asks creators to choose a tick or supply ETH/USDC as the pool quote asset.
Liqpad is in Beta. Beta describes the product and its supporting infrastructure; it does not change what verified contract transactions do on Base.
Use cases
Launch a B20 and its market, publish an IPFS profile, monitor activity, and claim earned VVV.
Discover Factory-created markets and trade through the Liqpad router with transparent estimates and slippage protection.
Read canonical profiles, events, pool configuration, fee accruals, and public indexed data.
Verify burns, fee allocation, locked liquidity, creator reserves, protocol capital, and transaction history.
For creators
Token model
Market cap versus initial supply
Liqpad displays market cap using the current token supply when available. Burned B20 is removed from supply, so market cap should not always be calculated against the original one billion.
For traders
The core market is always B20/VVV. ETH and USDC are convenient routing assets provided by LiqpadSwapRouter; they do not replace VVV as the launch pool quote token.
Trading risk
Locked liquidity and a verified contract do not guarantee price stability. New markets can be volatile, thinly traded, and exposed to slippage.
Fee mechanics
1%
Hook-assessed trading fee
70%
Creator share of assessed VVV
30%
Protocol share of assessed VVV
On the B20 side, the assessed fee is burned. On the VVV side, FeeRouter accounts for the creator and protocol portions separately.
| Flow | B20 outcome | VVV outcome |
|---|---|---|
| VVV → B20 | B20 output reaches the trader | Assessed from exact VVV input |
| B20 → VVV | Assessed B20 input is burned | Assessed from gross VVV output |
Creators claim with claim(token) or claimAll(). A claim changes custody, not the historical amount earned.
Protocol transparency
sweepPlatform() moves only the protocol amount recorded by platformAccrued().harvest() maintains the configured liquid VVV reserve and sends eligible capital through VeniceAdapter.Accounting
How the dashboard labels FeeRouter
Creator VVV awaiting claims is derived from the FeeRouter VVV balance minus protocol VVV pending sweep. The two values are displayed independently so creator liabilities are not presented as treasury capital.
Data model
Factory profiles, token supply, balances, pool state, receipts, and emitted Base events determine what happened.
Supabase stores confirmed, query-friendly copies for discovery, feeds, charts, market summaries, and creator pages.
GeckoTerminal and Dexscreener can supply pool discovery and charts. CoinGecko or DefiLlama can supply external USD references.
If an external FX or chart provider is unavailable, Liqpad should retain token-denominated data and label USD as unavailable.
Indexing delay
A successful Base transaction may appear before the website indexer or a third-party chart provider catches up. Verify the transaction receipt and token address before submitting it again.
For developers
createLaunch(params, quote, signature)getProfile(token)creatorTokens(creator)creatorAccrued(creator, token)platformAccrued()claim(token)claimAll()sweepPlatform()harvest()poolKey(b20)LaunchSwapExecutedFeeAccruedPlatformSweptHarvestUnwindBegunUnwindProgressedThese addresses come from the same runtime configuration used by the Liqpad web application.
Contract precedence
If documentation, cached data, or third-party interfaces disagree with a confirmed contract read or receipt, use the Base contract state and transaction logs as the source of truth.
Read before using
Common questions
Liqpad mines a CREATE2 salt off-chain before launch so the predicted B20 address has the branded suffix. Always verify that the token was emitted by the canonical Factory.
VVV is the common quote asset for every launch. A shared quote model makes launch configuration, pool routing, fees, and protocol accounting consistent.
Not through the Liqpad launch flow. The canonical pool is B20/VVV. ETH and USDC are routing conveniences in LiqpadSwapRouter.
ERC-20 trading can require approval first and the swap second. The second wallet request opens after approval confirms and the quote is refreshed.
The Base launch can be complete before GeckoTerminal, Dexscreener, or the Liqpad indexer has processed the pool. Check the receipt and try again later instead of redeploying.
USD values depend on external reference-price APIs. On-chain token amounts remain valid even when an FX provider is unavailable.
Creator VVV accrues per token in FeeRouter and remains there until the creator calls claim or claimAll from the creator wallet.
No. It processes the separately accounted platformAccrued amount. Creator claim reserves remain liabilities of FeeRouter.
DiemEngine maintains a configured reserve. Only eligible VVV above the reserve is staked during Harvest.
No. It prevents the launch position from being withdrawn through the normal LP path, but price still responds to trading and market conditions.
No. It is a deterministic Liqpad branding suffix. Factory origin, source code, permissions, and transaction history must still be verified.
Include the Base transaction hash, token address, connected wallet, page URL, exact error, approximate time, browser, network, and a screenshot. Never share a seed phrase or private key.