Start with what we do not claim.
Is OAKEN audited?
No, and we do not claim it. There is no audit badge on this site. Verification means the published source compiles to the deployed bytecode; it does not mean someone reviewed every failure mode. The contracts are deliberately short and no operator can move a lock — read them, or have someone you trust read them. The v4 vault has a 2-of-3 upgrade key with a 48-hour delay; v1–v3 are immutable. The full status, test/invariant coverage and disclosure policy are on the Security page. No bug bounty is live yet — the scope and reporting route are on the bug bounty page.
How do I verify a contract?
Paste its address into Sourcify or the chain's explorer. All eight contracts are exact matches on all four chains. The Verify page has the addresses, the status table and copy-paste eth_call recipes.
Who owns OAKEN?
No operator can move a lock or change its schedule. v4 is upgradeable: a 2-of-3 multisig can schedule a new vault implementation, and every upgrade waits 48 hours on-chain. v1, v2 and v3 have no owner and no upgrade path. The Bonds contracts have an admin — a 2-of-3 Safe behind a 48h Timelock — and that boundary is stated on every Bonds page. The website is a reader; it is not the vault.
Can the lock contract be upgraded?
v4: yes, slowly. The vault and adapter are ERC1967 proxies. A 2-of-3 multisig (the same owners as the Safe) can call scheduleUpgrade; the new implementation can only be activated after 48 hours, can be cancelled in between, and emits an event. v1, v2 and v3 are immutable, and locks in them cannot be moved to v4 or upgraded. The lock-level rules do not change: no pause, no fee switch, no rescue, and only the lock's creator can revoke a revocable lock.
What if this website disappears?
Locks still release. The schedule is stored in the contracts on four chains, and anyone can pay the gas to send a due lock to its beneficiary. You do not need this site, our servers or our permission.
Do you charge a protocol fee?
No protocol fee on locks or on our own factory: you pay gas only. Third-party launchpads charge their own fees, shown before you sign, and those go to them. Bonds have a 0.10% redemption fee that goes to stakers, not to a company treasury.
Is the same address really on every chain?
Yes. The deployments use a deterministic salt, so the address is derived from the bytecode. The vault, adapter, position lock, token factory, MultiSender, airdrop, presale factory and launcher share one address across Robinhood Chain, BNB Chain, Base and Polygon.
How the vault behaves.
Can anyone take my locked tokens early?
No. The vault releases only to the beneficiary, only at or after the schedule. No admin can move or pause a lock, and there is no rescue path. The v4 upgrade key can only replace the vault code after a 48-hour delay; v1–v3 have no upgrade path. A renounced lock is permanent — that is the point of the button.
Who can claim a lock?
Only the beneficiary receives the tokens. Anyone may pay the gas to submit the release — the vault checks who is being paid, not who is paying. This is why the Claim button is visible even when a different wallet is connected.
What does "stepped" / "vesting" mean?
A TGE release followed by a fixed percentage every N days. The step boundaries and the linear schedule give the same numbers at the same dates; steps only make the curve easier to read. The record page reads the steps from the vault, not from the page.
Can I change a lock after it lands?
The owner can edit the amount and the unlock date, and set a title, while the lock is not renounced. Increasing the amount pulls the difference from the owner's wallet. Renouncing blocks every edit, every transfer and every early claim.
What tokens can I lock?
Standard ERC-20s, including LP tokens. Not rebase tokens — a balance that changes on its own breaks the arithmetic. Fee-on-transfer, max-transaction and blacklist tokens need care: exclude the adapter 0xA2898528… and the vault 0x5221A10B… (the v4 pair every new lock uses) from fees and limits first, because the vault only counts what actually arrives. Locks created before 2026-10-23 live in the v1 pair — the adapter 0x16e02A10… and the vault 0xe410d0a2… — so use those addresses when you are changing one of those older locks.
What is a position lock?
A Uniswap V3/V4 position is an NFT. It is held by the position-lock contract until the date, then released to the beneficiary. The lock is only as strong as the collection's own transfer rules — the page says whether the manager is one we verified.
A different product, with a different admin.
Why do Bonds have an admin if Locks have no operator?
aOAKEN needs a NAV feed, fee parameters and a reward stream. Those are governance variables, so they sit behind a 2-of-3 Safe and a 48h Timelock. The Safe cannot move vault reserves, mint aOAKEN without USDG, or force a redemption. Locks and Bonds are separate products with separate trust assumptions; the site does not blur them.
What yield do Bonds pay?
No external yield is promised. Stakers receive the 0.10% redemption fee and a fixed OAKEN emission budget that was actually funded. OAKEN has no market price on this site; OAKEN numbers are token emissions, not a dollar yield. APR is calculated from what is really streaming.
Why can a redemption fail?
aOAKEN is redeemed from the vault's USDG reserves. If reserves are lower than the amount you are redeeming, the contract refuses rather than promising money it does not hold. The page shows vault reserves and the maximum redeemable amount before you sign.
What is the NAV keeper?
A small keeper publishes the NAV on a schedule. After the migration it is the Timelock, and the oracle has a per-update movement cap and a staleness window. If the NAV becomes stale, mint and redeem wait for the next update instead of using an old price.
Our factory, and the houses we route to.
What is different about the OAKEN factory?
One transaction creates a fixed-supply token and sends the whole supply to your wallet. There is no owner, no mint and no external service in the path. Locking is a separate page — the launch form does not lock anything, so there is no bundled lock and no window where the lock is promised but not yet real. It is the only route where the whole launch is our contracts.
Does the factory work on Solana?
Yes — two routes. OAKEN Factory creates a classic SPL mint, writes Metaplex metadata and revokes the mint authority; no OAKEN program sits in that path, and it creates no market, so there is no developer buy. pump.fun creates the coin on its own bonding curve, its rules apply, and the form asks for a developer buy in the same transaction. On Solana you pay rent and network fees; OAKEN takes no launch fee.
Can I lock on Solana?
Yes. OAKEN's own lock program is live on Solana mainnet with its upgrade authority revoked; Jupiter Lock — a third-party vesting program — remains an option. The Solana locks page tells you which program will be used, and that Jupiter's program is upgradeable by its team, before asking for a signature. Locks on Robinhood Chain and BNB Chain are our own EVM contracts.
Are third-party launches risk-free?
No. Pons, Flap, Genius, Clanker and four.meme run their own contracts and backends. We encode the call from their live parameters, but they can change factories, fees, hooks or rules. four.meme's launch is signed by its backend; Clanker's factory owner can change hooks and modules; Flap's portal is upgradeable by its team. Read the warning on the route before you sign.
What does a third-party launch cost?
Each route shows its own fee before you sign. Pons charges a launch fee; Flap and Clanker may charge their own; four.meme charges gas and its curve terms. OAKEN takes no cut of any third-party launch.
Where are token images stored?
For our own factory, the artwork is stored off-chain on our image host and mapped to the token address; the chain has no image field. Third-party launches use their own metadata. If our image host is unreachable, the token still exists and trades — only the picture is missing.
MultiSender, token factory, airdrop, presale.
MultiSender: what happens with 400+ addresses?
The contract caps a batch at 400. The page splits longer lists into sequential transactions and tells you before you start. A zero address, a bad amount or a mismatched list reverts the whole batch — nothing is sent. Use the per-line status to see which line was rejected.
Airdrop: why must I publish the claim file?
The chain stores only the Merkle root. Claimants need the list to build their proof, so the file must be published somewhere they can reach. Anyone can submit a claim for someone else — the tokens always go to the address in the row. The creator can sweep the unclaimed remainder after the deadline.
Presale: where do the tokens come from?
The sale must be funded with enough tokens for the whole hard cap before it opens. That is the difference from a presale that can disappear with the raise: the tokens are already in the sale contract. If the soft cap is missed, every buyer can refund, and the creator can take the unsold tokens back only after the sale has failed.
Token factory: can the supply change?
No. The supply is fixed at deployment. There is no owner, no mint, no pause and no burn function. The whole supply goes to the deploying wallet; locking a part of it is a separate, optional step.
When something does not work.
A transaction failed. What now?
Nothing moved unless the wallet says otherwise. A revert costs only the gas of the attempt, and your tokens stay where they were. The page prints the reason in plain words: you rejected it, gas is short, the token refuses transfers, or the contract will not take that number. The common fixes are approve first, top up gas, or raise the release percentage per cycle.
The page is stuck on "Reading…".
Chain reads go from your browser to public nodes. If a node stalls, the page gives up after a few seconds and offers Retry, which also rotates to the chain's second RPC. A failed read does not affect anything you sign.
My wallet is on another chain.
Pick the chain in the header. The site asks the wallet to switch and offers to add the chain if it is missing. If the wallet is on a chain we have not deployed to, the header says so and asks once per session; nothing is ever sent there.
My wallet is not detected.
Any EIP-1193 / EIP-6963 browser wallet works. On a phone, open oaken.one inside your wallet app's own browser (MetaMask → Browser, Trust/OKX → DApp browser). WalletConnect is offered from the connect panel when the extension is not present.
What lives off-chain.
What data does the site keep?
No accounts and no analytics. Your wallet address is read from your wallet when you connect and is used to build the page. Preferences such as the selected chain are stored in your browser's localStorage. Public RPC providers see the address you query, like any block explorer does. See Privacy for the exact list.
Are uploaded images permanent?
Images for our own factory are stored on an off-chain host and mapped to the token address. They are not part of the chain, and they are not guaranteed to be permanent. If the image host goes away, the token still exists and can still be locked or traded.
Do third-party launchpads see my data?
When you use a third-party route, the request goes to that provider (four.meme's backend, for example). Their terms and privacy practices are theirs, not ours. The route panels say which service is involved before you sign.
Is this legal / financial advice?
No. OAKEN is software, not an advisor or a custodian. Nothing on this site is a recommendation to buy, sell or lock any asset. Read Terms & Risk before using the contracts.