OHM is a treasury-backed liquidity and credit token, not a “yield token” anymore

Olympus lives or dies on one design choice: a protocol treasury that actively underwrites OHM’s liquidity and credit, instead of outsourcing “liquidity” to mercenary incentives.

In the current Olympus architecture, OHM is positioned as a treasury-backed, liquidity-enabling token on Ethereum. That framing is not marketing fluff. It is the operating model, as described in the protocol overview docs.

Token role clarity matters here:

OHM is the base token (ERC-20 on Ethereum).

gOHM is the governance wrapper used for protocol upgrades and, operationally, as collateral for Cooler Loans. Olympus docs are unusually direct that gOHM’s only use cases “today” are governance voting and Cooler Loans collateral.

From a treasury risk seat, that is the right progression. Yield narratives attract reflexive flows. Treasury mechanics keep the lights on.

History that matters for tokenholders

Olympus launched in March 2021.

The initial distribution and early growth loop were built around staking and bonds. The genesis-era “fair launch” mechanics are documented in Olympus’ own launch post. It specified an initial OHM supply of 68,260, with 50,000 offered in the presale and 18,260 seeded as initial liquidity.

The other structural change that matters is that Olympus’ original rebasing regime is explicitly “legacy” now. The docs state that rebasing is no longer in effect, while staking still exists primarily to obtain gOHM for governance and Cooler Loans.

Stability tooling also evolved. Range Bound Stability (RBS) is documented as the original system for market operations, but the docs say RBS is currently disabled and replaced by the Yield Repurchase Facility for downside operations and the Emissions Manager for upside operations.

Finally, Olympus’ on-chain governance is implemented through a Governor Bravo process with explicit quorum and approval thresholds (covered below). That matters because treasury policy is only as stable as the mechanism that can change it.

Supply, emissions, and distribution: from rebases to policy-driven issuance

OHM supply is not capped in the conventional “fixed max supply” sense. CoinGecko currently displays Max Supply as ∞ and reports Total Supply and Circulating Supply as dynamic values.

As of CoinGecko’s current page view, Circulating Supply is shown as 15,645,551 OHM and Total Supply as 19,891,573 OHM.

Mechanically, the OHM token contract exposes a mint function gated to a privileged role (“onlyVault”), and burn functions. That is the core “policy-controlled money” surface area.

Olympus frames today’s supply expansion as programmatic issuance when OHM trades at a premium to backing. The Emissions Manager is the policy that emits new OHM supply based on a base emissions rate and a minimum premium threshold, with premium computed as market price divided by backing price.

The docs describe emissions as: when premium exceeds the minimum premium, Olympus creates a Convertible Deposits auction offering a computed amount of OHM in exchange for USDS reserves. It also documents the emission equation: new supply = total supply × base emissions rate × (premium + 100%) / (minimum premium + 100%).

Convertible Deposits documentation goes further and enumerates “Emission Mechanics (January 2026)” including a Base Emissions Rate of 0.04% of supply/day and a Minimum Premium of 50%, alongside a backing reference point used in those mechanics.

OHM’s “private sale” exposure shows up through pOHM, which Olympus describes as a derivative that grants the option to mint OHM by burning pOHM and providing intrinsic value (example given: 1 DAI + 1 pOHM to mint 1 OHM). pOHM vesting is explicitly supply-based, and the Medium post states that team, investor, and advisor pOHM cumulatively vest as 11.8% of OHM supply.

From a dilution-risk lens, pOHM is not just “a team allocation.” It is an embedded claim on future OHM issuance capacity that activates when OHM trades with meaningful extrinsic value. Olympus designed it that way on purpose. The trade-off is straightforward: funding and alignment vs. a long-duration dilution overhang that becomes more relevant in upside regimes.

For a contrasting case study in stablecoin-linked monetary design, see our crvUSD tokenomics review.

Treasury design: liquid backing, reserve concentration, and budget discipline

Olympus’ docs treat the Treasury as the system’s center of gravity. It is defined as the on-chain assets “owned and controlled by the protocol,” responsible for OHM liquidity on open markets and stabilization via direct market operations in the treasury design docs.

There are two details in the treasury description that matter more than any token emission curve:

1) Reserve custody and format. Olympus states it uses a streamlined strategy with reserve assets held as sDAI, which RBS and Cooler Loans can access, automatically converting to DAI when needed.

2) Access control. The same doc notes additional modules can be granted access via On-Chain Governance. That is the risk boundary. If governance can grant treasury spend authority broadly, “treasury-backed” starts to look like “treasury-available.”

Olympus also runs with explicit budgeting language in governance. OIP-163 describes a “Treasury Framework” motivated by Cooler Loans requiring liquidation of the treasury into DAI so that 95% of treasury value is available for potential lending demand, and it frames the goal as defining budget and governing policies for gains above liquid reserves.

That is the right direction. Treasury-backed systems fail when “ecosystem funding” becomes a discretionary line item with weak constraints. If you want survival, you treat discretionary token reserves and discretionary stable reserves as different species. One is volatile dilution risk. The other is solvency fuel.

Utility and fiscal flows: how the machine expands, contracts, and pays for itself

Olympus has multiple, distinct fiscal loops. The important part is not that they exist. It is that they are increasingly policy-bounded and automated.

Programmatic expansion when premium exists. Emissions Manager checks premium (market price divided by backing) every 3 epochs, triggered by the Heart, and emits supply only when premium is above a minimum threshold. When active, it routes issuance through Convertible Deposits auctions for USDS, and can fall back to Bond Protocol to sell any undersold OHM under the emissions policy rules.

Contraction through yield-funded repurchases. The Yield Repurchase Facility (YRF) is an automated system that uses protocol-generated yield to buy back OHM, then borrows USDS against purchased OHM at backing and burns the OHM to “increase purchasing power” of the facility while reducing supply. It is integrated into the Heart and activates on Heart beats every 8 hours, with a weekly yield pull cadence and daily purchase cadence.

Credit utility that substitutes for sell pressure. Cooler Loans allows gOHM holders to borrow USDS against gOHM collateral via a “perpetual” lending facility backed directly by the Olympus Treasury. The docs emphasize 0.5% APR, no price-based liquidations, and default behavior tied to unpaid interest thresholds when you borrow against gOHM.

Cooler V2 terms include a minimum debt of 1000 USDS and a liquidation premium of 1%, with parameters governed and adjustable.

For a more conventional credit-market comparator, see our Maple tokenomics review.

Liquidity as infrastructure, not a subsidy. Olympus documents Protocol Owned Liquidity (POL) as a mechanism to ensure liquidity “without relying on liquidity mining incentives.” It notes Dex POL held in an OHM/wETH Uniswap v3 pool (intended to be permanent, subject to governance), and that RBS historically provided OHM/DAI liquidity with an algorithmic reserve-vs-liquidity balance.

Stability ops migration. With RBS disabled, the docs explicitly assign downside bound handling to YRF and upside bound handling to Emissions Manager.

Put bluntly: Olympus moved from “rebases as the primary user-facing incentive” toward “balance sheet and policy tooling as the primary mechanism.” That improves survivability. It also forces a harder conversation about who really benefits from the treasury’s risk budget.

Governance and parameter control: gOHM, Governor Bravo, and constrained treasury authority

Olympus’ governance is not a single mechanism. It is a set of constraints that decide who can touch the treasury and under what conditions.

Governance token. Olympus states gOHM is the only token used for proposing upgrades to the Olympus protocol, and that gOHM can be obtained by wrapping OHM and vice versa; see the token role details.

Proposal threshold. The Submission Guidelines for On-Chain Governance (OCG) state proposals are submitted by calling propose() on a Governor Bravo contract, and the proposer must hold and maintain at least proposalThreshold of total gOHM supply. The docs state the current proposalThreshold is 0.017% of total gOHM supply.

Quorum and approval. Olympus’ Proposal Lifecycle doc specifies that activating a proposal records quorumVotes derived from gOHM supply, and states the current quorumPct is 20% of gOHM supply. It also states the current approvalThresholdPct is 60%.

Timing. The same Proposal Lifecycle doc states the current votingDelay is 3 days, the current timelock delay is 1 day, and the current GRACE_PERIOD is 1 day.

Pessimistic vote casting. Olympus’ Governor Bravo implementation uses a “pessimistic” vote casting approach that takes the lower of a voter’s prior votes at proposal start and at the time of voting. The doc presents this explicitly as a defense against manipulating voting power by changing exposure.

Process hardening via simulation. Olympus also requires code review and simulation via the olympus-v3 repository, and notes the Emergency multisig will veto proposals that do not satisfy requirements.

This governance posture is compatible with a treasury-first survival model. High quorum plus supermajority approval makes parameter shocks harder. The trade-off is slower adaptation if conditions change quickly. For money-like systems, that is often acceptable.

Risk register: Olympus survives or fails on treasury drawdown control

Dominant risk: the treasury becomes a high-velocity liquidity outlet faster than it can be refilled.

Olympus’ modern design leans into something most protocols avoid: it makes the treasury economically reachable.

Cooler Loans is the clearest expression. Olympus describes Cooler as a perpetual lending system where loans originate from the Olympus Treasury and are issued in USDS against gOHM collateral, with a fixed 0.5% APR and no price-based liquidations.

That is a powerful utility. It also creates a new failure mode: if the protocol promises deep borrow capacity against backing, then the treasury must maintain a disciplined liquidity buffer and a conservative lending envelope. Olympus governance acknowledges this explicitly. OIP-163 states Cooler Loans required liquidation of the treasury into DAI so that 95% of its value is available for potential lending demand, and it proposes a framework to define budgets and policies for gains above liquid reserves.

Here is the mechanism-level problem a risk manager worries about:

When OHM trades at a discount to backing, the Emissions Manager is structurally less likely to emit new supply, because emissions are conditioned on premium exceeding a minimum threshold.

At the same time, Cooler Loans does not require a market premium to be used. Borrow demand can rise precisely when market confidence is falling, because holders prefer borrowing stablecoins to exiting into a thin market. That is rational behavior. It also means the treasury can face large stable outflows in the same regime where refill channels are constrained.

Olympus tries to counterbalance this with automated contraction and yield loops. YRF is explicitly designed to use protocol yield to buy back OHM and burn it, and it even “recycles” backing from purchased OHM into additional purchases.

But YRF is not a magical sink. It is bounded by realized yield and by governance-defined parameters. If yield compresses, or if reserve assets underperform, YRF’s ability to stabilize downside weakens. That pushes more weight onto treasury liquidity management and the credibility of the “liquid backing” concept.

That choice is coherent, but it concentrates operational risk in a small number of pipes. Any disruption to the underlying stable reserve stack, or governance miscalibration of lending parameters, becomes existential faster than most tokenholders intuit. And because Olympus’ “money” pitch depends on reliable liquidity and credit, a visible retreat from these guarantees can damage confidence more than a normal DeFi protocol would experience.

The sustainability posture that best fits Olympus’ design is boring. Ring-fenced reserves. Explicit liquidity coverage targets for Cooler demand. Limits on discretionary ecosystem spending that cannot be overridden casually. Olympus is already speaking this language in OIP-163. The survivability question is whether those constraints remain binding when the DAO is tempted to spend, diversify aggressively, or subsidize growth.

Top 3 risks

  1. Treasury liquidity shortfall against protocol promises. Trigger: a regime where OHM trades at or below backing while Cooler borrowing demand rises. Mechanism: emissions are conditioned on premium and can shut off, while Cooler loans source USDS directly from treasury reserves, increasing stable outflows. Who bears it: gOHM/OHM holders via reduced backing flexibility and impaired liquidity credibility. Measurable indicators: circulating supply and supply dispersion plus protocol-reported “liquid backing per OHM” and treasury value trends; sustained premium compression alongside rising Cooler utilization would be the warning pattern.

  2. Governance parameter shock or capture at the treasury boundary. Trigger: concentrated gOHM voting power coordinates to change lending terms, emission thresholds, or treasury module permissions in a way that externalizes risk. Mechanism: Governor Bravo proposals pass with quorumPct and approvalThresholdPct, then execute after timelock delay, altering policy modules that touch reserves. Who bears it: passive holders and integrators depending on predictable policy. Measurable indicators: changes to quorumPct, approvalThresholdPct, proposalThreshold, or timelock parameters, plus accelerated proposal cadence under minimal review periods.

  3. Smart contract and module interaction risk in automated market ops. Trigger: an exploit or critical bug in Heart-triggered policies, Governor Bravo execution paths, or lending periphery. Mechanism: YRF is integrated into Heart with 8-hour beats and executes recurring purchase logic; Emissions Manager similarly relies on Heart triggers and auction integrations; failures can lead to unintended issuance, reserve loss, or frozen operations. Who bears it: the treasury first, then all holders via reduced backing and impaired liquidity. Measurable indicators: emergency veto usage, abrupt disabling of modules (as already seen with RBS being documented as disabled), and abnormal deviations between policy schedules and on-chain actions.

If you are designing a similar treasury-backed system, tokenomics work should start with a budget constitution and explicit reserve access controls; our tokenomics design services focus on that exact boundary. For the design building blocks behind these constraints, see our token economy components guide, and for deeper reading you can browse our crypto research reports.



This article is part of our Tokenomics Deep Dive series.