You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Every other data provider lists a single mNAV number per DAT, but we believe that this can lead to incorrect assumptions, so instead we provide 3 numbers that define a range.
4
4
5
-
### Why one mNAV number can mislead you 
5
+
### Why one mNAV number can mislead you
6
6
7
7
Look at Greenlane Holdings on November 30th, 2025:
Looking at this mNAV number you would conclude “Greenlane trades at 0.29 times its crypto treasury. This looks extremely cheap.”
17
+
Looking at this mNAV number you would conclude “Greenlane trades at 0.33 times its crypto treasury. This looks extremely cheap.”
18
18
19
-
However, the company has many active contracts (that filings indicate are effectively certain to dilute over time / that are very likely to result in future share issuance), and when you account for this future dilution, the total share count that will have a claim on the treasury will be \~32.6m shares, resulting in an mNAV of 2.1. So you might buy thinking you're getting a heavy discount to the crypto treasury and you're protected when in reality you're buying at 2x premium over the crypto treasury value, very expensive and exposing yourself to a 50% loss.
19
+
However, the company has many active contracts (that filings indicate are effectively certain to dilute over time / that are very likely to result in future share issuance), and when you account for this future dilution, the total share count that will have a claim on the treasury will be ~35.4m shares, resulting in an mNAV of ~2.42. So you might buy thinking you're getting a heavy discount to the crypto treasury and you're protected when in reality you're buying at ~2.42x premium over the crypto treasury value, very expensive and exposing yourself to a ~60% loss.
20
20
21
21
To help investors avoid falling into this pitfall, and to provide more accurate metrics on the market, we created 3 versions of mNAV, each using a different share count:
22
22
23
-
***Realized mNAV**: The ratio of marketcap to crypto treasury value where marketcap = share price \* currently issued shares.
24
-
***Realistic mNAV**: The ratio of marketcap to crypto treasury value where the marketcap is calculated by multiplying the share price by the realistic share count, which is calculated by taking realized share count (outstanding shares) and adding dilution that is unavoidable under GAAP, such as diluted EPS share count, prefunded warrants, triggered convertibles, earnouts, and mandatory conversions.
25
-
***Maximum mNAV**: The ratio of marketcap to crypto treasury value where the marketcap is calculated by multiplying the share price by the the maximum share count, which simulates the max dilution if we assume that every single outstanding option, warrant and other contracts that can lead to share dilution gets executed. Covers the case of the maximum number of shares that could be minted based on the current active contracts.
23
+
***Realized mNAV**: The ratio of marketcap to crypto treasury value where marketcap = share price × currently issued shares.
24
+
***Realistic mNAV**: The ratio of marketcap to crypto treasury value, where marketcap uses the economically most probable share count multiplied by the share price.
25
+
***Maximum mNAV**: The ratio of marketcap to crypto treasury value, where the marketcap is based on the fixed-count contractual dilution ceiling times the share price. Covers the case of the maximum number of shares that could be minted based on the current active contracts.
26
26
27
27
### Definitions
28
28
@@ -34,31 +34,31 @@ Includes all completed share events after the latest filing using the outstandin
34
34
35
35
It answers:
36
36
37
-
“How is the market valuing the crypto treasury on the shares that exist right now?”
37
+
> “How is the market valuing the crypto treasury on the shares that exist right now?”
38
38
39
39
#### Realistic mNAV
40
40
41
-
The ratio of marketcap to crypto treasury value where the marketcap is calculated by multiplying the share price by the economically most probable share count.
41
+
The ratio of marketcap to crypto treasury value, where the marketcap uses the economically most probable share count multiplied by the share price.
42
42
43
43
Builds on the fully diluted realized share count, also known as outstanding shares, and adds dilution that is unavoidable under GAAP, such as diluted EPS share count, prefunded warrants, triggered convertibles or earnouts and mandatory conversions.
44
44
45
45
Uses basic instead of diluted if the company reports a net loss.
46
46
47
47
It answers:
48
48
49
-
“What does valuation look like once unavoidable dilution is priced in?”
49
+
> “What does valuation look like once unavoidable dilution is priced in?”
50
50
51
51
#### Maximum mNAV
52
52
53
-
The ratio of marketcap to crypto treasury value where the marketcap is calculated by multiplying the share price by the fixedcount contract dilution ceiling.
53
+
The ratio of marketcap to crypto treasury value, where the marketcap is based on the fixed-count contractual dilution ceiling times the share price.
54
54
55
55
Covers all fixed share contracts such as options, warrants, RSUs, PSUs, fixed convertibles, and fixed share earnouts.
56
56
57
-
Excludes dollarbased programs such as ATMs, shelves and equity lines because these are not fixed share counts, are not guaranteed to be used and are highly price and path dependent.
57
+
Excludes dollar-based programs such as ATMs, shelves and equity lines because these are not fixed share counts, are not guaranteed to be used and are highly price and path dependent.
58
58
59
59
It answers:
60
60
61
-
“What does valuation look like under the full fixed share contractual scenario?”
61
+
> “What does valuation look like under the full fixed share contractual scenario?”
62
62
63
63
### Why this three line system is better
64
64
@@ -67,3 +67,215 @@ It answers:
67
67
* It maintains one clear numerator and one clear denominator.
68
68
* It provides consistent comparability across issuers.
69
69
* It prevents errors caused by stale share counts, ATM capacity, ADS ratio drift and vague “fully diluted” claims.
70
+
71
+
---
72
+
73
+
### Exact methodology and sourcing to replicate DefiLlama's mNAV
74
+
75
+
The sections above explain the intuition and definitions behind the three mNAV lines. This section specifies the exact data inputs and calculations used so that DefiLlama’s DAT mNAV can be replicated.
76
+
77
+
#### 1. mNAV formula and notation
78
+
79
+
For each dilution bucket `B` (Realized, Realistic, Maximum):
DefiLlama uses authoritative, up-to-date sources in the following priority order:
134
+
135
+
1. SEC filings.
136
+
2. Company IR pages.
137
+
3. Treasury dashboards.
138
+
4. Custodian disclosures.
139
+
5. Verified wallets.
140
+
6. Official press releases via PR Newswire, GlobeNewswire, Business Wire, Accesswire.
141
+
142
+
**Handling vague language**
143
+
144
+
When disclosures are not precise:
145
+
146
+
- “At least 10,000 BTC” → recorded as **10,000 BTC**.
147
+
- “Around $1m of ETH” → converted into ETH units using DefiLlama pricing at the reference date.
148
+
- “Substantial amount” → ignored unless a quantifiable range can be derived.
149
+
150
+
If only USD values are disclosed, DefiLlama uses that USD figure directly as part of **Crypto Treasury Value**.
151
+
152
+
**Token pricing**
153
+
154
+
DefiLlama uses aggregated, volume-weighted exchange pricing that is consistent across all DefiLlama products.
155
+
156
+
#### 3. Fully diluted share buckets (FD)
157
+
158
+
For a given date, **Crypto Treasury Value** is the same across all buckets. The difference between the three mNAV lines comes from the **FD share count used in the numerator** through `Marketcap_B`.
159
+
160
+
All buckets:
161
+
162
+
- Adjust for stock splits.
163
+
- Adjust for reverse splits.
164
+
- Normalize ADS structures and ADS ratio changes.
165
+
166
+
##### FD realized (Shares Outstanding, used for Realized mNAV)
167
+
168
+
FD realized corresponds to the **currently existing shares** that have legal claim today.
169
+
170
+
The FD realized share count is composed of:
171
+
172
+
- Shares outstanding from the latest filing.
173
+
- Plus **completed** corporate actions after that filing:
174
+
- New issuances (including ATM settlements).
175
+
- Executed conversions.
176
+
- Option and warrant exercises.
177
+
- Repurchases and cancellations.
178
+
- Splits and reverse splits.
179
+
- ADS ratio changes.
180
+
181
+
This FD share count is used as the `FD shares` input when calculating the **Realized mNAV** line.
182
+
183
+
##### FD realistic (GAAP likely dilution, used for Realistic mNAV)
184
+
185
+
FD realistic incorporates dilution that is effectively unavoidable under GAAP, starting from FD realized.
186
+
187
+
The FD realistic share count is composed of:
188
+
189
+
- FD realized shares.
190
+
- Diluted weighted average shares from GAAP EPS.
191
+
- Prefunded warrants.
192
+
- Earnouts or conversions that filings indicate are certain or already triggered.
193
+
- For issuers with a **net loss**, diluted EPS share count is replaced by basic (GAAP rule).
194
+
195
+
This FD share count is used as the `FD shares` input when calculating the **Realistic mNAV** line.
196
+
197
+
##### FD maximum (fixed share contractual dilution, used for Maximum mNAV)
198
+
199
+
FD maximum captures the full fixed-share contractual ceiling, starting from FD realistic.
200
+
201
+
The FD maximum share count is composed of:
202
+
203
+
- FD realistic.
204
+
- All fixed-share instruments, whether in- or out-of-the-money:
205
+
- Options.
206
+
- Warrants.
207
+
- RSUs.
208
+
- PSUs.
209
+
- Fixed convertibles.
210
+
- Fixed-share earnouts.
211
+
212
+
Explicitly **excludes**:
213
+
214
+
- Dollar-denominated ATM capacity.
215
+
- Shelf registration capacity.
216
+
- Equity lines and similar dollar-based facilities.
217
+
218
+
These are excluded because they:
219
+
220
+
- Are not fixed share counts.
221
+
- Are not guaranteed to be used.
222
+
- Are highly price- and path-dependent.
223
+
224
+
This FD share count is used as the `FD shares` input when calculating the **Maximum mNAV** line.
225
+
226
+
#### 4. Equity prices
227
+
228
+
Share prices are sourced from Yahoo Finance:
229
+
230
+
- Last traded price.
231
+
- On the primary listing exchange.
232
+
- Matched as closely as possible to the treasury valuation date used for token pricing.
233
+
234
+
#### 5. How mNAV is calculated
235
+
236
+
For each bucket `B`:
237
+
238
+
1.**Compute Crypto Treasury Value.**
239
+
Aggregate all directly held tokens at their USD prices.
240
+
241
+
2.**Compute `Marketcap_B`.**
242
+
`Marketcap_B = FD shares_B × Share price`.
243
+
244
+
3.**Compute `mNAV_B`.**
245
+
`mNAV_B = Marketcap_B ÷ Crypto Treasury Value`.
246
+
247
+
DefiLlama then publishes three lines:
248
+
249
+
-`mNAV_realized`
250
+
-`mNAV_realistic`
251
+
-`mNAV_maximum`
252
+
253
+
#### 6. Why mNAV may differ from other sources
254
+
255
+
mNAV values shown on DefiLlama may differ from other dashboards or broker data because:
256
+
257
+
- DefiLlama **excludes** equity stakes in other DATs from Crypto Treasury Value.
258
+
- Token counts can vary across IR pages, filings, custodians and PRs; DefiLlama reconciles and prioritizes sources as described.
259
+
- Vague PR language is interpreted **conservatively**.
260
+
- Some platforms include ATM capacity in their “fully diluted” share counts; DefiLlama does **not**.
261
+
- Some platforms do not normalize for ADS structures or historical splits.
262
+
- Pricing sources and reference times can differ.
263
+
- Disclosure dates can differ across data vendors.
264
+
- The method of calculating “mNAV” or “NAV multiple” can vary by platform and by company.
265
+
266
+
#### 7. Acronyms
267
+
268
+
-**DAT**: Digital Asset Treasury
269
+
-**Crypto Treasury Value**: USD value of directly held tokens
270
+
-**FD**: Fully Diluted
271
+
-**FD realized**: Completed events only (shares outstanding plus completed actions)
0 commit comments