Audits
What has been verified, by whom, and what remains a dependency rather than a guarantee.
Two kinds of assurance, not the same thing. On-chain verification is reproducible from public state. Third-party audit is a report by people who read the code. The first is stronger; the second catches things the first can't.
On-chain verification#
Verified against event logs, holder tables, and source matched to deployed bytecode — not a repository's current branch.
| Contract | Owner | Upgradeable | Verdict |
|---|---|---|---|
| ODIN token | Renounced 2023-02-05 | No (non-proxy) | Immutable |
| 15 × Uniswap V2 pairs | Never had one | No | Immutable |
| pValhalla | Never had one; partner role unarmed | No | Immutable |
| pOHM | None; live but powerless partner | No | Immutable |
| spValhalla | Renounced in its deploy tx | No | Immutable |
| UNCX locker (60.2% of TSUKA LP) | Lock owner = dead address | No | Immutable-equivalent lock |
| OHMI/ETH third-party lock | Third-party custodian | Yes — proxy | Trust-bounded |
Method, for anyone reproducing it: ownership from complete OwnershipTransferred histories (immune to stale caching); lock status from full holder tables and LP transfer histories; pod behaviour from full-match verified source of deployed bytecode; fee values from exact integer arithmetic over live Transfer events.
What the last row means#
The OHMI/ETH lock is a third-party custodian's upgradeable proxy. It sits on an arbitrage route, not in ODIN's own structure — but it's the one place in the surrounding picture where a guarantee depends on a party who could change their contract.
Naming it is the point. A table where everything says "immutable" is a table nobody checked.
Third-party audit#
Hacken lists an audit profile for ODIN Liquidity Network: hacken.io/audits/odin-liquidity-network
The public profile exposes no report, date, or findings. An audit badge you can't inspect is a promise, not a mechanism — precisely the category ODIN claims to be getting away from.
The on-chain verification above is not a substitute for a code audit. It establishes that the contracts cannot change — not that they are free of bugs.
Peapods publishes audits for the pod contracts underlying the sink: peapods.finance
Live dependencies#
Three, in order of significance. Not risks that have been mitigated — dependencies that exist.
-
Peapods' fee router#
The sink runs on Peapods' contracts. pValhalla itself is immutable, but Peapods' protocol-level fee router is admin-mutable. It affects the rewards leg — not principal, not the burn — and remains the largest single live dependency ODIN carries.
-
Uniswap governance#
The pools are Uniswap V2 contracts. The factory-wide protocol fee switch belongs to Uniswap governance and has already been used — a fixed one-sixth of fee growth, set once, reaching nothing that was already locked. ODIN had no vote. Not having governance means not having one in other people's, either.
-
Ethereum#
Everything rests on Ethereum mainnet continuing to work as it does. Stated for completeness.
Immutability as a security property#
Industry consensus has shifted here: auditors increasingly treat immutability as a risk reducer and upgradeability as a risk factor. An upgradeable contract has an admin key, and an admin key is a target — for compromise, coercion, and error. ODIN's contracts have nothing to compromise.
The symmetrical cost: an immutable contract can never be patched. If a bug exists, it exists permanently — no emergency response, no fix, no migration path. That's the actual trade, and the price of everything else on this site.
Trust-minimised, not trust-free#
The honest summary, and the phrase ODIN uses deliberately.
Removed: discretionary trust in ODIN. No team decision can change your position, because no mechanism exists through which it could.
Remaining: Uniswap's contracts and governance, Peapods' code and its mutable router, Ethereum itself, and the correctness of code nobody can now fix.
The first is real and unusual. It is not the same as depending on nobody, and anyone telling you it is has stopped describing this protocol.