Vesting vault
Your opening buy lands here inside the launch transaction and leaves only on schedule, never faster than the daily limit.
Anyone can launch a token in seconds. Lockpad helps creators define their launch conditions before the market opens, making their commitments public and verifiable.
Pons is where a token launches and trades. Lockpad is where its creator sets the terms first — and locks every term that code can enforce, before anyone can buy.
Each commitment deploys only the modules you choose, as minimal clones of fixed code. None has an owner, an upgrade path or a way out for committed assets.
Your opening buy lands here inside the launch transaction and leaves only on schedule, never faster than the daily limit.
Becomes your Pons fee recipient. Every wei it receives splits by fixed shares; the buyback share can only buy and burn.
Withdrawals are scheduled in public and wait out a delay that can never be shortened, with optional allowlists and caps.
“Team tokens are locked for six months.”
The opening buy lands in a vault inside the launch transaction. Nothing leaves it faster than the schedule allows.
LockpadVestingVault.release(amount) → reverts if amount > vestedAmount(now) − released
Pons is where the token launches and trades. Lockpad is where the terms are set and committed before the first trade. Two signatures, both from your own wallet.
Configure the token, the opening buy, vesting, fees, treasury and the wallets you will disclose. Lockpad validates every combination before anything is signed.
Your terms are published as one document inside the commitment transaction. Its hash is stored onchain, so anyone can check it was never edited.
The same transaction deploys the modules you chose: a vesting vault, a fee router and a timelocked treasury. None has an owner or an upgrade path.
You launch through Pons's own launch-and-buy router. The opening buy lands in the vault and creator fees route to the fee router, in the launch transaction itself.
Lockpad never rounds a statement up into a guarantee. Each term carries the status its mechanism earns, and the last column names what stays outside its reach.
| Term | Mechanism | Status | Outside Lockpad's control |
|---|---|---|---|
| Creator allocation and vesting | Opening buy delivered straight into an ownerless vesting vault | Locked onchain | Tokens bought later, from any wallet |
| Release rate | Vault caps releases per 24-hour window | Locked onchain | When released tokens are sold |
| Minting | Pons V2 tokens have a fixed supply and no mint function | Locked onchain | Nothing; holders can only burn their own tokens |
| Creator fee rate | Set once in the Pons launch; Pons stores it immutably | Locked onchain | Nothing |
| Fee distribution | Fee router as Pons fee recipient, with fixed shares and no exit path | Locked onchain | Pons protocol owner can redirect fees after a 3-day public timelock |
| Treasury withdrawals | Timelock, optional allowlist and weekly ETH cap | Locked onchain | A key holder who waits out the timelock |
| Treasury owner | Read onchain: single key or Safe multisig, threshold shown | Verified state | Who holds the keys |
| Team wallets | Listed in the disclosure; each wallet can sign to prove key control | Disclosed | Identity, and wallets that were never disclosed |
| Selling from a wallet | Cannot be enforced by any contract | Disclosed | Everything |
What was disclosed. What was actually locked. What can still change. Which wallets were named. What happens next. Every launch gets a public page that reads the chain each time it loads.
A Lock Page only says It's locked where enforcement was verified onchain at the block shown. Everything else is labelled for what it is. Your browser can re-run the whole check without Lockpad's server.