Docs

The short version, in one page.

OAKEN is a lock service and a small launchpad. On the EVM chains we deploy to, tokens and liquidity go into contracts where no operator can move a lock, pause it or take a fee. v4 keeps one power deliberately: a 2-of-3 multisig can replace the vault code, and every upgrade waits 48 hours on-chain. v1, v2 and v3 are immutable. Solana locks: OAKEN's own program is live on mainnet with its upgrade authority revoked; Jupiter Lock remains a third-party, upgradeable option — the Solana section below says exactly what is live. Everything this site shows is read from the chain it sits on; the site is a window, not the vault. Audit and bug-bounty status, coverage and known limitations are on the Security page — no audit claim is made.

Chains we are on

ChainIDNativeExplorer
Robinhood Chain4663ETH Blockscout
BNB Chain56BNB BscScan
Base8453ETH BaseScan
Polygon137POL PolygonScan
The header picker lists exactly the chains our contracts are deployed to — a chain we are not on would take your signature and do nothing with it. Adding one to your wallet is offered by the site itself (wallet_addEthereumChain, with these parameters) the first time you switch to it.

Contracts — same address on every chain

Oaken Lock (adapter) · v4 (proxy)
0xA2898528eb4Aea0bDAf47202A5BA3bA4f58F831c
Vault · v4 (proxy)
0x5221A10B772D5e2d51B60E8e3dd5DA9338b04ab0
Launcher · v4
0x9600f22d2f629904B44c7dA2d958f5AfB3a1e5Ff
Upgrade multisig · v4 (2-of-3)
0xCb847B572352156be50c90FBc752cfd032114666
Delayed proxy admin · v4 (48h)
0xDB998916A34b87c7DA337d922bC1219970FA0319
Oaken Lock (adapter) · v3
0x6022DA059FAa0673E3058ADECEef375c2Abfb4A1
Vault · v3
0xd4064d8E73AAB53D7d9efd8A6E8DBE2003d1de4B
Launcher · v3
0x4488C369116D0C6FEA84162313c3840976D5A9a5
Oaken Lock (adapter) · v2
0xDBE1f3dc1d6E6759355E1B164231748f0589cb41
Vault · v2
0xbC511F31967D9EBF775d203661a2BEfF6AA42615
Launcher · v2
0x0d7cCEA7BabC5e3b4849267740D8fBBe6C4FDa58
Oaken Lock (adapter) · v1
0x16e02A106fE6E978fB98F76756B3a06b4995a7A6
Vault · v1
0xe410d0a21C1376992874a9bEEeE0d623A50D4a34
Launcher · v1
0x1d7561fC331594820382E8dd64582645EbafD873
Position lock
0xfC9A43c90e0E0d548D95cEf3C77fce802806CbA9
MultiSender
0x1f380ef5eFF9113314Ee175dCE4F226DFd75A50C
Token factory
0xc0A3AD1428EeB70cAF88bb89c3B17D0191E1Bd34
Airdrop
0x17E9910cDC37BdA5531414012aeA5b0862C22066
Presale factory
0xAC070cf2ed45aEcb9f5299d4C670fFfCE6387724
v4 is what new locks and new launches use. The vault and adapter are ERC1967 proxies; a 2-of-3 multisig can replace the implementation after a 48-hour delay. v1, v2 and v3 are immutable and stay live for the locks created under them; the site reads all four. Same addresses on every chain we deploy to.
source verified All lock-family contracts, on all four chains are exact matches on Sourcify (the lock contracts are also published on Blockscout). Paste any address above into Sourcify to compare it byte for byte. Verification is not an audit — we claim none.

Solana — two launch routes, one lock route

OAKEN Factory (own launch) creates a classic SPL mint with a fixed supply, writes Metaplex metadata, and then revokes the mint authority. There is no OAKEN program in this path: the token is governed by the SPL Token and Metaplex programs, both live on Solana. You pay rent and network fees only.

pump.fun is a third-party route: its program creates the coin on its bonding curve. pump.fun's market, graduation and fee rules apply, and its program is upgradeable by pump.fun.

Locks on Solana use OAKEN's own program (Co9ZnAVxX2siGThhjTpPgXPHYrCev1nrXFyGB1VcZcQW), deployed on mainnet with its upgrade authority revoked, or Jupiter Lock (LocpQgucEQHbqNABEYvBvwoxCPsSbG91A1QaQhQQqjn), a third-party vesting program that Jupiter's team can upgrade. The Solana locks page says which program it will use before it asks for a signature. EVM locks on Robinhood Chain and BNB Chain are live and unchanged.

Solana wallets are separate from the EVM wallet in the top bar. The Solana pages detect Phantom, Solflare, Backpack and Glow in the browser; nothing is signed until you approve it in that wallet.

HOW TO CHECK A LOCK YOURSELF

Three ways, none of them through us.

01

Open its record page

Every number there is an eth_call from your browser to a public node — not a value we stored. If the page and a block explorer ever disagree, believe the explorer.

02

Call the vault directly

Paste 0xe410d0a2… into a block explorer, open getLock(id) and hit read. It returns the same amounts, dates and steps this site shows.

03

Run your own node

Nothing here is required for a lock to release on time. The schedule lives in the contract; when it is due, the vault pays the beneficiary and nobody else.

KNOWN LIMITATIONS

What this does not do.

  • No rebase tokens. A balance that changes on its own breaks the arithmetic of "how much is in there" — the lock would be wrong the moment it lands.
  • Fee-on-transfer and max-tx tokens need care. Exclude the v4 adapter 0xA2898528… and the vault 0x5221A10B… from fees, limits and blacklists first. Locks created earlier live in the v1–v3 pairs (listed above) — use those addresses when changing an older lock. The vault measures what actually arrived, so a taxed transfer locks less than you sent — the record page will say so.
  • A renounced lock is permanent. There is no un-renounce — that is the point — so it is offered only when the schedule is already what you want.
  • Position locks hold ERC-721s. Their strength is the NFT's own: a collection with a back door can move the position anyway. The collection address is part of every record, and "this LP is locked" is only ever said about known position managers.
  • Token images are off-chain. For our own factory the chain has no image field; the artwork is stored on our image host. If that host is unavailable, the token still exists and trades — only the picture is missing. Third-party launches use their own metadata.
  • We cannot recover mistakes. Tokens sent to the wrong address, or locked with no beneficiary, are gone. Nobody — including us — has a rescue function, because nothing was kept.
  • This is new. The contracts are short and public, but young. Start with an amount you are comfortable testing.
FAQ

The questions the form does not answer.

Which wallets work?

EVM: any browser wallet that injects a standard provider (EIP-1193 / EIP-6963) — MetaMask, OKX, Rabby, Coinbase Wallet, Rainbow and friends — or WalletConnect from the connect panel. Solana pages detect Phantom, Solflare, Backpack and Glow separately; the EVM wallet in the top bar is not used there. The site never asks for a seed phrase.

What does it cost?

Locks cost nothing. You pay gas, that is all. Third-party launchpads (Pons, Flap, Clanker, four.meme) charge their own fees — shown before you sign — and those go to them, not to us.

Where does the money go?

Nowhere. The vault holds tokens and pays the beneficiary, and there is no other function to call. OAKEN has no treasury in any of these contracts.

Who can claim a lock?

Only the beneficiary. Anyone may pay the gas to send it to them — the vault checks who is being paid, not who is paying.

What if this website disappears?

Locks still release. The schedule is in the contract, and the contract is on four chains. This site is a reader; it is not required for any of it.

Why is the launchpad listing sometimes empty?

Sales come from a listing snapshot plus live clocks. When nothing is inside its window the list says so, and when the listing itself cannot be reached the page says that instead of pretending there are no sales.

Can I lock on Solana?

Yes — with OAKEN's own lock program (live on mainnet, upgrade authority revoked) or Jupiter Lock, a third-party vesting program. The Solana locks page states which program will be used and that Jupiter's program is upgradeable before it asks for a signature. EVM locks on Robinhood Chain and BNB Chain are our own contracts.

Something is stuck on “Reading…”

Chain reads go straight from your browser to public nodes. If a node stalls, the page now gives up after a few seconds and offers Retry — which also rotates to the chain's second RPC. Nothing you sign is affected by a read failing.

A transaction failed. What now?

Nothing was sent, unless the wallet says otherwise — a revert costs only the gas of the attempt, and your tokens stay where they were. The page shows the reason in plain words: a rejection in the wallet, not enough native currency for gas, a token that refuses transfers, or a number the contract will not take. The usual fixes are “approve first”, “top up the gas balance”, or “raise the release % per cycle”.

My wallet is on another chain.

Pick the chain you want in the header — the site asks your wallet to switch, and offers to add the chain if the wallet does not have it yet. If your wallet sits on a chain we have not deployed to, the header says Wrong network and asks once per session; nothing is ever sent there.

What is “amount” on a record page?

What the vault is actually holding for that lock — measured when the transfer landed, not what the sender typed. For a fee-on-transfer token the two differ, and the record page says so.

Still stuck? Ask on X — that is the only channel we have. @oakenhood Lock tokens