Token brief / 02 — Model mechanics
A fixed supply, a known float and the limits of both
ORV's supply design is narrow in what it promises. It fixes the token count at 50,000,000, disables minting, and publishes when the remainder is scheduled to appear. Everything else, including demand, has to be earned.
A cap, not a dial
In a conventional monetary design, supply is a policy variable: a protocol can mint new units to fund growth or react to shocks. That flexibility has a cost. Holders cannot know future supply, so every projection carries an assumption about governance behaviour. ORV removes that assumption by treating supply as a constant: 50,000,000 tokens, with minting disabled.
The immediate benefit is legibility. Percentages map to fixed amounts, and amounts map to fixed release terms. The ecosystem fund is 15,000,000 ORV, not 30% of a supply that may change. The team's 15% is 7,500,000 ORV on a stated schedule. Analysts can reconstruct the float without modelling issuance policy.
The trade-off is equally clear. A hard cap gives up the ability to mint out of a funding shortfall. If the ecosystem needs more resources, it must rely on revenue, partnerships or governance decisions about existing supply. Fixed supply is a commitment to constraint, and constraints only look wise if the plan is sound.
What disabling minting is meant to prove
Disabling minting is a credibility device: no administrative decision can dilute holders without changing the contract itself. For a token that markets itself on a hard cap, that is the difference between a policy and a property.
The design also implies discipline on spending. The ecosystem fund's 15,000,000 ORV is a finite budget, as are the 10,000,000 ORV for community incentives, the 3,000,000 ORV for liquidity and the 2,000,000 ORV for marketing. When supply cannot be expanded, a community cannot approve inflation; it can only decide which existing bucket funds a programme. None of this makes the token valuable; it makes the supply rule legible.
Demand is the variable the cap cannot fix
The white paper does not base ORV's value on price appreciation or fixed returns. Demand is expected to come from AI-powered services, platform features, governance, ecosystem contributions and Web3 applications.
Each of those is a usage channel rather than a yield promise. A user might need ORV to reach an advanced analytical module, to stake behind a governance position, or to pay for a service from a partner application. If those channels grow, demand has a functional base. If they do not, the fixed cap is a number without a market.
This is where the model is most exposed. Supply mechanics can be audited and scheduled; demand cannot. The white paper says any tokenomics design ultimately requires validation through market conditions and platform development. User growth, technology, regulation and competition all sit outside the supply table.
Secondary market access is a separate layer, governed by venue rules and jurisdictional restrictions. Infrastructure such as NPX Exchange, a digital asset trading platform, belongs to that market layer, not the supply design; liquidity is a service, not a contract guarantee.
The case for a 35% initial float
The 35% figure is a compromise between two failure modes. Launch with too little and the ecosystem cannot fund liquidity, early participation or partnerships. Launch with too much and the market absorbs an overhang that suppresses the participation the float was meant to encourage.
At 17,500,000 ORV, the float is intended to support market liquidity, early community growth, incentives, partnerships and brand promotion. Those launch-phase jobs require tokens in hand. The remaining 32,500,000 ORV is distributed through locks, roadmap-aligned releases and reward schedules, keeping long-horizon supply tied to the people building the ecosystem.
Whether 35% is right is a judgement call. A higher float might improve early liquidity at the cost of a longer overhang; a lower float might support price discovery while starving the ecosystem of resources. The white paper picks a middle path and publishes the terms: more than many models offer, less than a guarantee.
The 35% figure describes tokens available at the token generation event. It does not describe trading volume, holder count or price. Those depend on demand and market conditions, and no supply schedule can promise them.
Buyback and burn: possible, not promised
The white paper raises the possibility of a buyback and burn mechanism, contingent on operating performance and governance. Potential funding sources include AI service revenue, platform operations, corporate partnerships and ecosystem activity.
The operative word is possible. Buybacks and burns are described as potential tools for future ecosystem optimisation, not a firm commitment. Specific timing, scale and execution methods would be determined by platform development and governance rules. There is no published schedule, no guaranteed budget and no promise the mechanism will ever be used.
A burn can reduce circulating supply if funded and executed, but it is discretionary policy layered on a fixed cap. It is not a yield, a floor or a redemption right.
The durable test remains usage.
What the model can and cannot prove
The model can prove that supply is capped, that minting is disabled, that allocations are published, and that major locks have stated durations. It cannot prove that the ecosystem will attract users or that AI services will find a market. Those are execution and demand questions, and they remain open.
The useful discipline is to separate the auditable from the aspirational. The cap and the release schedule belong to the first category; the demand thesis belongs to the second.