Docs

How a launch works, and what is checked.

GooBooPad is an independent interface. Launches run on the Pons V2 contracts on Robinhood Chain. This page describes the contracts as their verified source has them, lists every address the interface calls with its verification status, and says plainly what is and is not verified.

Updates are posted on X at @GooBooPad. That account never sends direct messages asking for keys, funds or "verification"; anything that does is not GooBooPad.

The launch flow

A launch is one call to the factory’s launchToken(params, launchConfigId, pairToken), sent with exactly the launch fee in ETH. With an opening buy it is instead launchAndBuy(…) on the router, which calls the factory on your behalf and buys on the new curve in the same transaction. Either way the factory deploys the coin (a fixed-supply ERC-20 that mints its whole supply to the curve) and the curve, records the launch, emits TokenLaunched, and trading is open in that block.

The parameters include an expectedEconomics digest. GooBooPad reads it from previewLaunchEconomics at review time and passes it back, so if the owner changes the supply, fees, virtual reserve, threshold or pool terms between your review and inclusion, the transaction reverts (LaunchEconomicsMismatch) instead of launching on different terms. The CREATE2 salt is fixed per draft and carries a GooBooPad prefix, which is how launches made here are recognised later without trusting anyone’s word.

Costs

The factory charges launchFee() in ETH, read live (it is owner-adjustable). Gas is paid to the network. Trades on the curve pay the configuration’s curveFeeBps plus the creator’s chosen tax; a launch-window tax applies to non-exempt buyers in the first seconds. GooBooPad takes no fee anywhere. Its own token, $GBPAD, is separate from the launch protocol: nothing on this site requires it, and its contract address is published only on the $GBPAD page.

Liquidity and locking

The creator supplies no liquidity. The curve prices against a virtual reserve (phantomQuote) and holds what buyers pay. When the real reserve reaches graduationThreshold, the buy that crosses it calls graduate, which sweeps the reserves into the factory. Then anyone may call createGraduatedPool: the factory initialises a Uniswap v4 pool, mints a full-range position to the launch locker, registers the pool hook, and locks the token remainder that could not enter the pool at the terminal price.

The locker (RobinFunFiV2LaunchLocker, Sourcify bytecode match) has lockPosition, lockTokenSupply, isLocked and no function that transfers a position or tokens out. That is the evidence. GooBooPad shows each graduated coin’s locker record and the position’s current owner on its page rather than promising "locked forever"; a future upgrade of Uniswap’s PositionManager or a bug in any of these contracts is outside what a source read can rule out.

What the protocol owner can do

The factory is Ownable2Step and ownership cannot be renounced (renounceOwnership reverts). From the verified source, the owner can:

• Change the launch fee, add or edit launch configurations, open or close public launching and whitelist launchers (affects future launches only).
• Approve or remove pair assets and set their curve economics (future launches only; a live curve keeps its constructor terms).
• Propose a new creator-fee recipient for any coin, effective after a 3-day timelock and executable for 3 days after that (setCreatorFeeRecipient). A creator’s own transfer does not cancel it.
• Switch a coin’s buyback off (never on).
• Force-sweep a sold-out curve whose pool seed the guard refuses, and, 7 days after any sweep with no pool created, release the swept reserves to an address of its choosing (rescueSweptGraduation). Anyone can pre-empt this by creating the pool.
• Pay a stuck curve’s pending fees directly to their recipients (rescueCurveFees).

It cannot mint a coin, change a coin’s metadata, take reserves from a curve that is trading, or withdraw a locked position.

Contracts

Addresses are published at https://docs.ponsfamily.com/docs/v2 and re-checked by pnpm verify:config against Sourcify and the factory’s own on-chain pointers. Last verified 2026-09-30 09:25 UTC. Owner: 0x263e…19Dd ↗.

Each coin and each curve is a fresh contract created by the verified deployer. Their ABIs are compiled from the factory’s own verified sources (solc 0.8.35), cross-checked against an exact-match verified coin instance, and every selector is checked against a live curve and coin by pnpm verify:config.

Pair assets

68 assets are listed (1 native, 1 stablecoin, 55 Stock Tokens, 8 ETF Tokens, 3 community coins); 4 more are accepted by the factory but unconfirmed and reachable only through the import check. Sources: factory PairTokenApprovalUpdated events + approvedPairTokens()/pairTokenEconomics(); https://api.robinhood.com/rhj/assets → assets[].deployments[chainId=4663].contractAddress · terms() · shared issuer beacon · https://docs.robinhood.com/chain/stock-tokens/; https://docs.robinhood.com/chain/contracts/ → "USDG". See the directory.

Confirmations and finality

Robinhood Chain gives a sequencer soft confirmation in well under a second. GooBooPad calls a transaction confirmed after 10 blocks on top of a successful receipt, re-checks that the receipt is still canonical, and only then parses the factory event. Pages also show the chain’s documented stages (soft-confirmed, posted to Ethereum, final on Ethereum) from the RPC’s safe and finalized tags.

The launch index

There is no protocol API in the trust path (the protocol’s own guidance to integrators). GooBooPad indexes the factory’s TokenLaunched and PoolGraduated events itself over a rolling window, keyed by chain, transaction and log index, with block-hash checkpoints for reorganisations and a cursor that resumes across runs. Launches made here are kept; others age out but stay readable by address straight from the factory. A deployment without a database runs in live mode instead: the listing is the newest launches read straight from the factory’s events (about the last hour of blocks), refreshed as pages are opened, and any older coin opens by address. Either way, nothing is ever shown that was not read from the chain.

Data and privacy

Drafts live in your browser’s local storage and nowhere else. Uploaded images are re-encoded, stored by content hash and served publicly (the URL is written on-chain). The only wallet signature the site ever asks for besides transactions is a free, single-use message for a creator’s note. No seed phrases, no private keys, no tracking scripts. The site’s RPC relay forwards read-only methods to a fixed upstream and cannot broadcast.

Not verified

• No audit. Source verification shows what the contracts do, not that they are free of bugs.
• The graduation guard (0xf56951…) has no Sourcify record; it is created by the verified factory’s constructor and only answers view pre-checks.
• The hook, escrow, vault, locker and graduation executor are bytecode (partial) matches on Sourcify: the compiled code matches, the metadata hash does not.
• No USD prices. Coins are shown in their pair asset only.
• Nothing about a pair asset’s issuer, or a community coin’s creator, is vouched for beyond the on-chain facts listed above.