The frozen core
The Engine Principle: the core never changes, and everything interesting happens around it.
Most protocol documentation has a roadmap. This section is the opposite — things ODIN has decided not to do, and will not do later either. A commitment not to change is only worth something if it's specific enough to be broken.
Not everything ODIN doesn't do is a never. Some things — bridging, for instance — are open questions gated on conditions. This page is about the ones that aren't.
The Engine Principle#
The core protocol stays stable and permanent. Innovation happens around it, never by modifying it.
The sixteen pools and the token contract are finished — not "for now," finished. They have no admin surface to modify them through, so the principle is enforced by the contracts rather than by anyone's discipline.
Everything that gets built — odinOS, the agentic surface, the OS family — sits outside the core and reads from it. Deleted tomorrow, the pools would keep quoting and k would keep ratcheting.
The test: if a new thing can break the old thing, it's in the wrong place.
Simplicity as engineering, not aesthetics#
Every unnecessary feature adds attack surface and maintenance burden. Complexity is justified only when it adds lasting resilience — and most doesn't.
The product test for any proposal: does this strengthen the foundation of decentralised liquidity? If not, it's probably unnecessary, however clever.
This is why ODIN has no governance module, no fee switch, no treasury, no staking contract of its own, no rebase, and no vesting schedule. Each is a feature someone could have argued for. Each is also a lever, a dependency, and a thing that can fail.
What ODIN does build#
The work goes into surfaces that help people understand what the core is doing — because the largest real gap between ODIN and the people it might serve is comprehension, not features. Someone who doesn't understand permanently locked liquidity isn't helped by a seventeenth pool.
The surfaces are what that looks like in practice.
The honest version#
ODIN is trust-minimised, not trust-free.
The pools are Uniswap's contracts. Uniswap governance holds one lever that reaches them — the protocol fee switch, already used, once, for a fixed sixth of fee growth. It cannot be turned up and it cannot reach the originally locked liquidity, but a capped lever is still a lever, and ODIN had no vote in it.
The sink runs on Peapods' contracts. pValhalla itself — the pod that wraps ODIN, and the thing that burns — is immutable: no owner, no pause, no proxy, fees fixed at construction. Nobody can change the wrap fee, the 50% burn share, or the 33,333,333 locked at the dead address.
What is admin-mutable is one component beside it: Peapods' protocol-level fee router, which directs the rewards leg of collected fees. It cannot reach principal, and it cannot reach the burn. It is named here because it is somebody else's code with somebody else's key on it, not because it threatens the mechanism this page is about.
Ethereum itself is a dependency, which is the assumption everyone makes.
What ODIN removes is discretionary trust in ODIN: no team decision can change your position, because no mechanism exists through which it could. That's real and unusual. It is not the same as depending on nobody.