Lockpad launches tokens on Pons V2 with the developer's bag in a vesting contract and the creator's fees locked until the curve graduates. Miss the deadline and the fees are buried — bought back and burned. Every rule is a contract you can read; none of them has an owner.
Chrome · lit at runtime · no assets
What gets locked
Other launchpads let a creator promise. Here the promise is a contract deployed in the same transaction as the token, with no owner and no override — not even ours.
The creator's own buy is delivered to a vesting contract in the launch transaction — it never touches their wallet. It unlocks linearly over the duration they chose (7 to 365 days) and the countdown is public.
DevVesting.sol · no admin · no clawback
Every creator fee the curve generates goes to a fee lock, not to the creator. Nothing leaves before the curve graduates; then it unlocks over 30 days. Miss the deadline and anyone can bury the lock: the ETH buys the token back and burns it.
FeeLock.sol · buried locks pay nobody
Pons taxes early buyers to punish snipers. The only buyer we exempt is the vesting contract itself. A creator's second wallet pays exactly what everyone else pays — the pad cannot be used to front-run its own launch.
empty exempt list · verifiable on the curve
The rule
The creator picks two numbers at launch: how long the developer buy vests, and how long the curve has to graduate. Everything else is fixed.
Graduation is recorded on the lock the first time anyone calls checkpoint. From that moment every fee — already received or still to come — unlocks linearly over 30 days. After that, fees pass straight through on each release: 90% to the creator, 10% to the pad.
Once the deadline passes without graduation, anyone can bury the lock. Each call spends at most 2% of the curve's quote reserve buying the token back, and sends what it bought to the dead address — one call per hour, so the burial can't be sandwiched at a profit. A buried lock never pays the creator, or us, again.
How it works
Name, ticker, image, description, socials — the first screen of any launchpad.
How long your developer buy takes to unlock: 30 / 90 / 180 days, or anything from 7 to 365.
How long the curve has to graduate before your fees can be buried: 7 / 14 / 30 days.
The form reads the rule back in plain words, with the dates. What you read is what the contracts will do.
One transaction deploys both locks and launches on Pons V2, with the locks already wired in. The only fee is Pons' 0.0005 ETH.
Live
Every card shows both locks as they are right now: how much of the developer buy is still behind the schedule, and where the fees stand.
What we take
The pad's share is taken by the fee lock itself, at release time, from what the creator is being paid. It is not a launch fee, it is not skimmed while the fees are locked, and it is never taken from a lock that gets buried — if the token dies, the pad earns exactly what the creator earns: nothing. The share is fixed inside each lock at launch; the router's owner cannot raise it on a lock that already exists.
Questions
A lock is only as good as what it does not cover. These answers say exactly where the line is.
Partly, and it is worth being exact. What the locks stop: dumping the developer buy (it is vesting, in public) and taking the creator fees early (they are locked until graduation, and buried if it never comes). What they do not stop: the creator buying from a second wallet like anyone else and selling later. That second wallet gets no exemption from Pons' snipe tax — the only exempt buyer is the vesting contract — so it pays what every other early buyer pays. Lockpad makes a rug expensive and visible, not impossible.
Pons graduates a curve when it has raised 4.2 ETH and moves the market to a pool. The fee lock does not know about that until someone calls checkpoint — anyone can, and the token page does it for you. From the recorded moment, everything the lock has received and everything it receives later unlocks linearly over 30 days. After that, each release pays out whatever has arrived.
Because a vesting schedule needs a start time, and the curve reports a flag, not a timestamp. Recording it on the lock when first observed gives every later calculation one fixed reference that nobody can move. The cost is that a creator who forgets to checkpoint starts their vest late — which is why the site makes it a one-click call that anyone can make.
Once the creator's deadline passes and the curve has not graduated, anyone can call bury. The lock pulls whatever Pons has swept to it, spends at most 2% of the curve's quote reserve buying the token on the curve, and sends the tokens to the dead address. It can be called again an hour later, and again, until the lock is empty. A buried lock never releases to the creator or to the pad — including fees that arrive afterwards.
Because a burial is an open call on a public curve. Moving the price by some fraction costs an attacker about twice the 1% trade fee on the capital it takes to move it, and wins them at most that fraction of the slice. When a slice is under 2% of the reserves the fees exceed the gain, so sandwiching a burial loses money — regardless of any slippage setting, which is why the call has none.
On the curve. Pons collects the trade fee on every buy and sell and sweeps the creator's share to its fee escrow on its own schedule (graduation triggers a sweep too). The token page shows three figures: accruing on the curve, pending in the escrow, and held by the lock. Only the third is subject to the schedule; the first two are still Pons' to move.
No. The router has an owner for three things: pausing new launches, moving the pad's own treasury address, and setting a pad launch fee (zero). Each lock is a separate contract with no owner at all; its deadline, vest duration and pad share are fixed at deployment. The router can name a lock's token and curve exactly once, in the launch transaction, and never again.
Both locks let the current creator propose a new address, which must accept — a two-step hand-over, so a typo cannot lose the role. It changes who is paid; it never changes when or how much.
No. Lockpad is middleware: the router calls Pons' public factory and forwarder, which accept launches from any address. Pons takes its usual fee and runs the market; Lockpad only decides where the creator fees and the developer buy land. Nothing about the token itself is different — same curve, same graduation, same pool.
Ready
Two numbers, one transaction. The rule is read back to you before you sign, and it cannot be edited after.