Some things should not move.

Oaken Lock keeps tokens and liquidity where they were put. No owner, no upgrade, no admin key — the schedule is written once, and every number the lock pages show is read live from the chain it sits on.

Lock tokens Browse sales See the locks
—
Locks, all chains
—
Distinct tokens
—
Chains deployed
0
Owners · no upgrade
Launchpad

Open right now.

All sales

Token sales on the chains this site lists, with what has been raised and when each one closes. The listing is the snapshot that ships with the build; the clocks are yours.

Reading the listing
How it works

Three steps, none of them ours to undo.

01

Pick the token

Any ERC-20 — a project token, or a liquidity pool token. The same contract handles both.

02

Set the schedule

One unlock date, or a stepped vesting: a release at TGE, then a slice every N days.

03

Anyone can check it

The record page reads the chain, not our database. Point your own node at it if you like.

The schedule, drawn

Vesting is a set of rings. Each one is a date.

A stepped schedule releases a slice every N days — the record page draws that as a ring for every step, and fills them as time passes.

Read it yourself

The same address on every chain we deploy to.

Contracts — one address, every chain

Oaken Lock (adapter)
—
Vault
—
Chains
Same address on every chain we deploy to.
Deterministic deployments: the address is derived from the bytecode, so it is identical everywhere we ship. The chain picker in the header lists the chains that are actually deployed — nowhere else.

What we do not have

  • No owner. Nothing to renounce, because nothing was kept.
  • No upgrade. The contract that holds your tokens cannot be replaced.
  • No audit. We do not claim one. Read the contract instead — it is short, and it is the thing that matters.
The record

Every lock has a page. Look at one.

Reading the chain…