How Lockpad works

Pons is where a token launches and trades. Lockpad is where its creator sets the terms first: it publishes them, deploys contracts that enforce the ones code can enforce, and gives every launch a public Lock Page that re-reads the chain each time it loads. Lockpad runs on Robinhood Chain mainnet (chain ID 4663) and launches tokens through Pons V2 only.

The four steps

1. Create

You configure the token Pons will deploy (name, symbol, description, logo, links), your opening buy, vesting, the creator fee, where fees go, the treasury and the wallets you are disclosing. Nothing is signed yet. Lockpad validates every combination and shows, beside the form, the status each term will earn once verified.

2. Disclose

The first transaction, LockpadCommitments.createCommitment, publishes your terms as one JSON document in the transaction's Disclosure event and stores its keccak256 hash in the registry. Anyone can fetch the document from the chain and confirm it was never edited. Lockpad's server is not needed for that.

3. Lock

The same transaction deploys only the modules you chose, as EIP-1167 clones of fixed implementations:

• Vesting vault. Receives your opening buy and releases it to a fixed beneficiary on an immutable schedule (initial unlock, cliff, linear), optionally capped per 24-hour window. Unused allowance never carries over.
• Fee router. Becomes your Pons creator fee recipient. It splits every wei it receives into fixed buyback, creator and treasury shares. The buyback share can only buy your token and burn it. The router has no function that moves the Pons fee recipient elsewhere.
• Treasury. Every withdrawal or owner change is scheduled in public and executes only after an immutable delay (1 hour to 30 days), within a 14-day window. Optional: a fixed allowlist of destinations and a weekly ETH cap.

None of the modules has an owner, an upgrade path, a pause or a rescue function for committed assets.

4. Launch on Pons

You launch through Pons's own PonsV2LaunchAndBuy router (0xe33E9E479dF8802cb0866d5d05258bEc4cF62948). Your wallet is the initiating account, so Pons attributes the launch to you. Lockpad sets the launch parameters so that the opening buy is delivered straight into your vault and creator fees are paid to your router, both inside the launch transaction itself. Nobody can trade before that transaction lands, because the curve does not exist before it.

A third transaction, LockpadCommitments.bind, ties the commitment to the token after checking Pons's own launch record. When the router is the fee recipient, anyone can bind (a keeper, a buyer); otherwise only the creator can.

What Pons fixes, and what stays changeable

Pons V2 tokens have a fixed supply minted once to the bonding curve, no owner and no mint function. The creator fee (Pons calls it the creator tax, up to 10% at launch time) is stored immutably. The fee split between Pons and the creator recipient is frozen per launch. The fee recipient itself is the one thing a creator can move on Pons, which is why the fee router exists: it is a recipient that cannot move itself.

Pons's protocol owner, a 2-of-3 Safe, keeps standing powers over every launch, including redirecting creator fees after a 3-day public timelock. Lock Pages show this on every launch and flag any pending change. See limitations.

Costs

• Lockpad charges nothing.
• Pons charges its launch fee (read live; 0.0005 ETH at the time of writing) plus the cost of your opening buy.
• Robinhood Chain network fees for three transactions.

Your keys

Lockpad never asks for a private key or seed phrase and never signs for you. Every transaction is simulated against Robinhood Chain before your wallet is asked, and every step is verified afterwards by reading the chain back. A signed transaction is not treated as a successful commitment until that read succeeds.