OAKEN is a small set of contracts that hold tokens and liquidity, and a website that reads them. The product decision was not "add more features" — it was to remove the parts that create a reason to trust an operator: no operator can move a lock, no pause, no protocol fee, no custody of your wallet. v4 keeps one power deliberately: a 2-of-3 multisig can replace the vault code, after a public 48-hour delay. v1–v3 are immutable. What remains is a schedule written once, on a contract anyone can call.
Who can change the vault?
- No operator over a lock. No key can move a lock's tokens or change its schedule directly — not ours, not anyone's.
- v4 is upgradeable, slowly. A 2-of-3 multisig can schedule a new vault implementation. It waits 48 hours on-chain, can be cancelled, and emits an event.
- v1–v3 are immutable. Locks created in those vaults stay in them; no admin can upgrade or rescue them.
- No pause, no fee switch, no rescue. Even the upgrade path cannot pause a lock, take a fee, or move a balance — it can only replace the code after the delay.
Why the same address everywhere?
Every contract is deployed with a deterministic salt. The address is derived from the bytecode, so the vault, the adapter, the position lock and the four tools land on the same address on Robinhood Chain, BNB Chain, Base and Polygon. There is one address to check, not one per chain — and the verification links are the same bytes on each.
The chain picker in the header only lists chains where those contracts actually exist. A chain we are not on would take your signature and do nothing with it, so it is not offered.
OAKEN next to a typical locker
| Question | Typical locker | OAKEN locks |
|---|---|---|
| Can the contract be upgraded later? | Often yes — owner or upgrade proxy | v4: 2-of-3 + 48h delay. v1–v3: no. |
| Where does the number on the page come from? | Their database | eth_call from your browser |
| What does it cost? | A locking fee or a token percentage | 0 protocol fee — gas only |
| Do you have to trust the website to stay up? | Often yes | No — the schedule lives in the contract |
| Is the contract audited? | Usually a badge | We claim no audit. The code is short and public — read it. |
Amber is not a promise.
It is a material fact: the acorn is inside, and it stays inside. That is the product, and the whole brand.
The 15-second film is on the home page.
Locks have no operator. Bonds have an admin.
Do not read "no owner" on this site and assume it applies to every product. Locks v1–v3 are immutable; v4 has a 2-of-3 upgrade key with a 48h delay. Bonds have a Timelock admin. We say which is which on every page.
Locks · vault, positions, tools
- No operator over a lock. The schedule is fixed when the lock lands. v4 has a 2-of-3, 48h-delayed upgrade key; v1–v3 are immutable.
- Anybody can pay the gas to release a due lock; the vault pays the beneficiary and nobody else.
- The tools are ownerless too — fixed-supply token factory, MultiSender, Merkle airdrop, presale with refunds.
Bonds · aOAKEN
- Parameters are managed by a 2-of-3 Safe behind a 48h Timelock. Fees, NAV limits and keeper settings can change — that is a governance surface, and it is disclosed.
- The Safe cannot move vault reserves, mint aOAKEN without USDG, or force a user's assets. Redemptions are paid from reserves, and can be limited by them.
- No external yield is promised. OAKEN emissions are token emissions, not a market yield. There is no aOAKEN secondary market on this site.
"Source verified" is not "audited".
Verification means the published source compiles to the bytecode running at that address. It does not mean the code was reviewed for every way it can fail. We claim no audit. What we do claim is smaller and checkable: the contracts are short, no operator can move a lock, and every number on this site is read from them.
Verify the bytecode
Open Sourcify or Blockscout, paste an address, and compare the source to the deployed bytecode.
02Read the limits
The known limitations — rebase, fee-on-transfer, position NFTs, no recovery — are on the docs page, not in a footnote.
03Ask the hard questions
Why no audit? What if the site disappears? What happens to a failed transaction? The FAQ answers them directly.