Today, most ownership coin Net Asset Value ("NAV") analysis asks the question “is the token trading above or below the treasury value?” Below NAV, there may be a liquidation opportunity. Above, the market is paying a premium for future growth. That comparison is useful, but it is only one use of a metric that can do more. NAV can be used as a balance sheet signal, a price reference, a dilution tool, and a proposal input.

Doing that work means keeping the two versions of NAV from Understanding NAV in Ownership Coins distinct:

  • Total NAV = Non-Native Treasury Assets − Liabilities
    • The project-level number, used for treasury size, runway, and capital allocation. 
  • NAV/AS = Total NAV ÷ Adjusted Supply
    • The token-level number, used for premium and discount analysis, dilution, and liquidation analysis.
    • Adjusted Supply starts with total native token supply and subtracts tokens that do not represent a live claim on the treasury value.

A snapshot of either Total NAV or NAV/AS is a useful starting point. The real work is turning NAV into a maintained analytical system for each project with a historical series, a forward projection, a consistent supply and valuation methodology, and periodic reconciliation.

1. Analyzing NAV as a Signal

A lot of NAV's analytical value is in its direction and showing direction can be accomplished by having three lines on a chart: Total NAV, NAV/AS, and spot price, overlaid with the events that moved them. Such events include monthly allowance draws, decision markets, raises, unlocks, mints, buybacks, etc. Understanding those three lines together is what the rest of this section is about.

Know the shape of an early-stage curve - most early-stage ownership coins hold their treasury in stablecoins. So Total NAV should be relatively stable, and move in steps down from monthly allowances and market approved spend and up from new investment, revenue, yield, etc. 

The impact of dilution and burn - take a project with $2M of Total NAV and 10M tokens in adjusted supply, so NAV/AS is $0.20. 

  • The project spends $100K with token supply unchanged. Total NAV falls to $1.9M and NAV/AS to $0.19. That decline is burn. 
  • The project spends nothing but adjusted supply rises to 12M from a new mint. Total NAV stays at $2M while NAV/AS falls to about $0.167. That decline is dilution. 

Both show up as a lower per-token number but mean different things. This is why every NAV/AS chart should be paired with the Total NAV and adjusted supply series.

Separate NAV growth from price growth - a way to read the three line series. 

Total NAV

NAV/AS

Price

What the market is likely saying

↑

↑

→

Balance sheet improved, market hasn't priced it in

→

→

↑

Move is expectations, not a balance sheet improvement

↓

↓

→

Market accepts the burn as productive

↓

↓

↓

Confidence in both the balance sheet and the team is weakening

None of these are automatic as each has to be analyzed against product progress, treasury composition, and token supply changes.

Projected NAV - total NAV and NAV/AS can also be projected forward using known inputs:

  • Monthly Allowances - program enforced and on a fixed schedule.
  • Team Performance Packages - program enforced, on time cliffs and price milestones. 
  • Raises - require decision market approval, but can be modelled in. 
  • Revenue - can be modelled via forecast. 

A NAV snapshot doesn’t show a step-down from an approaching unlock, and a weak one can improve on an approved raise and revenue.

Read volatility against treasury composition - volatility only means something once you know what the treasury holds. For a stablecoin treasury, low volatility is expected, and large moves with no spend, raise, or unlock are a reason to check the methodology. For a treasury holding volatile investments, volatility may be normal but changes the risk profile.

2. NAV/AS as an Invisible Floor and Ceiling

NAV/AS does not appear on CoinGecko/CMC price charts, but it has an invisible pull on price from both sides.

The floor - when the spot price falls below NAV/AS, the treasury behind each token is worth more than the token costs. A persistent discount makes a liquidation proposal a rational thing to put forward, and the prospect of one pulls the spot price back toward NAV/AS.

Whether the floor holds depends on: 

  • Treasury liquidity - illiquid assets (for example RWAs) are harder to sell/wind-down.
  • Decision market coordination - holders have to agree to act, if they don’t act a discount can persist.
  • Confidence in the NAV estimate - a debated number cannot anchor a decision market.

When a token trades below NAV/AS, the size of the discount signals how likely a liquidation actually is. Some discounts compress quickly when liquidation is possible. Other times a discount persists when certain holders want the project to continue. A token price sitting near NAV/AS means the market is valuing it at roughly its treasury backing, with no premium for the operating business. 

If the project weakens, one of two things happens. Holders coordinate around a liquidation and the discount closes, or holders sell their tokens and the discount widens and persists.

The ceiling - when spot trades well above NAV/AS, the market is paying for something beyond the balance sheet. This includes anticipated revenue, product development, user growth, distribution, and narrative. Early projects can trade above NAV/AS for any of the previous reasons. But the higher the premium, the more the valuation rests on expectations, and the more it can compress if those expectations weaken.

Premium and discount bands - plotting historical NAV/AS against spot price turns "above" and "below" into something measurable. 

  • The NAV/AS Premium or Discount to Spot = (Spot Price ÷ NAV/AS) − 1

A project's own historical range becomes a valuation reference point. If a token has traded between a 20% discount and a 150% premium, a move to the deepest discount may signal liquidation pressure or an overreaction while a move to the highest premium may signal excessive confidence. These bands can break historical trends, but they help serve as a guide for how far price has moved from treasury backing.

3. NAV as a Decision Market Input

NAV should be part of ordinary reporting and decision making, instead of assembled in a rush when there is a proposal discussion. Below are some examples of how it can be used.

Budget and spend proposals - Imagine a project with $2M of Total NAV spending $100K per month, they have ~20 months of runway. If there is a proposal for an $300K spend, that is 15% of the treasury and about three months of runway. The framing is important for decision makers to price the spend against the remaining funds and the milestone it is meant to reach.

Minting proposals -  A mint changes both sides of NAV/AS. Take a project with $2M of Total NAV and 10M tokens in adjusted supply so NAV/AS = $0.20. A proposal to mint 2M new tokens has different impacts on NAV depending on what happens to the tokens. If tokens are minted without raising cash (ie. team performance package), Total NAV stays at $2M, adjusted supply rises to 12M, NAV/AS falls to ~$0.167. If newly minted tokens are sold OTC at a 25% discount, Total NAV rises and NAV/AS falls slightly. Newly minted tokens sold above NAV/AS would actually raise NAV/AS. 

Buyback proposals - If a token trades below NAV/AS, a buyback can be value accretive to remaining holders, because the project buys back tokens at a discount to the treasury value. But at the same time the cash spent reduces Total NAV and shortens runway. For an early-stage project a buyback large enough to move price may also be large enough to damage a treasury the team still needs to build with. For a mature project with recurring revenue and a large treasury, the same buyback is more defensible.

Liquidation proposals - A NAV reconciliation showing the assets actually available, the liabilities, the liquidity of the treasury, and the adjusted supply that would share in any distribution. A rough or stale estimate can change the outcome of a decision.

4. NAV is an Estimate Without Accurate Books

Externally calculated NAV is a good estimate, and should be treated as such, unless the project's bookkeeping supports a more accurate number. From an accounting perspective many things can change the estimate and this becomes even more complex as a project's operational surface expands (think of offchain or custodial accounts, illiquid assets, market making agreements, etc). 

The gap between estimate and source of truth closes when teams maintain regular books, publish an account registry, classify wallet movements, disclose liabilities, and attest to their offchain holdings. 

5. NAV Needs Growth Metrics Beside It

Without supporting operating metrics, an investor may see NAV falling but cannot see whether the product is gaining users or growing revenue. A project that shows credible progress can justify a premium to NAV/AS but a project that spends treasury without showing progress invites the market to value the treasury above the operating business, which is when persistent discounts to NAV/AS become a liquidation target.

Checklist for NAV Analysis

Teams and Data Providers:

  • Publish Total NAV with a reconciliation table - non-native assets, liabilities, net value.
  • Publish NAV/AS separately, with adjusted supply shown in full and exclusions broken out (protocol-controlled, locked, unvested).
  • Report native token holdings separately, not as treasury backing.
  • Maintain a historical series for Total NAV, NAV/AS, adjusted supply, and spot price, with major events labelled.
  • Regularly publish operating metrics that show what treasury spend is producing.

Analysts and Investors:

  • Use Total NAV for treasury and runway questions; use NAV/AS for per-token valuation questions.
  • Never infer burn from NAV/AS alone. Check whether Total NAV moved, supply moved, or both.
  • Use a moment in time snapshot for an immediate read and use a time series for trend and event driven changes.
  • Plot NAV/AS against spot to measure premium and discount bands.
  • Project the curve forward using allowances, expected spend, scheduled unlocks, liabilities, and expected revenue or raises.
  • Read volatility against treasury composition. A stablecoin treasury should not behave like a volatile portfolio.
  • Before trusting a proposal, check wallet scope, liabilities, asset pricing, and the adjusted supply methodology.
  • Read NAV beside growth metrics. A falling treasury with improving traction is not the same as one with no progress.

Conclusion

Total NAV shows the organization's asset base which is the number for runway and capital allocation. NAV/AS shows the treasury backing per live token which is the number for price comparison, dilution, buybacks, and liquidation analysis.

What the category still needs is a maintained time series, forward projections, consistent supply methodology, reliable tracking, and public growth metrics. And the teams whose books help ensure those numbers are accurate. 

Once holders can see what the organization has, what each token is backed by, how those numbers are moving, and what the spend is producing, ownership coin decision making becomes much easier to analyze.