1. What reaches NEAR today
Verifiable value capture: 4.53% to 15.81% of net issuance
- Three-wallet total
- 418.8K NEAR
- Share of DefiLlama's reported Intents revenue, same days
- 100.9%
- Net issuance
- 88,295 NEAR a day
Notes and sources
NEAR delivered to NEAR’s three Intents revenue wallets equalled 15.81% of net issuance; only 4.53 points trace to public fee collectors and 11.25 arrive as unshields from the Confidential Intents escrow, fee stream unattested.
What it shows: How much of NEAR’s net issuance (88,295 NEAR a day over the 30 days 2026-10-06 to 2026-11-04) was matched by NEAR delivered to the three revenue wallets, split by how it arrived: 4.53% from two recurring public fee collectors and 11.25% released from the Confidential Intents escrow, plus 0.03% from one other source.
What it does not show: Which fee stream pays for the escrow releases: the NEAR verifiably arrived, but the public chain cannot split the 11.25 points between the two candidate NEAR-side streams that fit, so, if those three are all of NEAR’s Intents revenue wallets, measured value capture is a range, 4.53% to 15.81% of issuance.
- The two candidate readings are near.com’s fees and the Confidential Infrastructure Fee. A per-stream attestation by NEAR would turn the range into one number. Nothing here alleges misconduct. This is consistent with a privacy feature working as documented, and the question is auditability.
- The rungs are not nested: collectors, escrow and one other source add up to all three wallets, and the buyback-wallet rung is a subset of the total.
- Not all of the collector rung is public settlement. Of its 4.53 points, 0.56 were fees paid by single-use accounts the escrow had funded (exploratory, every transfer into the collectors classified by sender), so 11.81 points passed through the escrow in all, and counting only publicly settled swaps the floor is 3.97%. By the last day, 96.0% of collector A’s fee value came from escrow-funded accounts.
- The total matches DefiLlama: 418.8K NEAR is 100.9% of its reported Intents revenue for the same days. DefiLlama’s adapter takes the same three wallets from NEAR’s own Dune query, so it is the same count: it checks our pricing and wallet list and gives no independent check of the wallets. Even the top of the range covers about a sixth of issuance, and the buyback wallet holds its NEAR: none of it has been burned.
- No valuation is made here. The range is the finding: 15.81% is what reached the three wallets and 4.53% is what is traced to public fee collectors. None of this feeds the rating rule.
Source:
- SQL:
sql/buyback_withdraw_sources.sql,sql/collector_inflow_funders.sql,sql/collector_funder_checks.sql - Raw snapshot:
data/raw/escrow/deliveries.csvsha256 3176231d2065data/raw/escrow/issuance_reads.jsonsha256 2e9c824b4b3ddata/raw/escrow/verify_sample.jsonsha256 3a64f2ad0615data/raw/bq/buyback_withdraw_sources.jsonsha256 e310eb0c522adata/raw/bq/collector_inflow_funders.jsonsha256 c16656a80c73data/raw/bq/collector_funder_checks.jsonsha256 15360dcfb5e6
- Code:
pipeline/compute.py,pipeline/fetch_escrow.py - Upstream: BigQuery public dataset bigquery-public-data.crypto_near_mainnet_us, table execution_outcomes (intents.near native_withdraw events); FastNEAR transaction API and NEAR archival RPC (keyless) for the funding hops and the two total_supply reads
Query
Re-check any delivery or funding transfer from the chain with no key: python3 -m pipeline.fetch_escrow verify --sample 60. The BigQuery job that traced the funding hops from 2026-10-06 is recorded in data/MANIFEST.json (bqjob_r275b038b73d7c093_000001a1af3708a8_1); its SQL is not committed in sql/, so the per-delivery table data/raw/escrow/deliveries.csv and python3 -m pipeline.fetch_escrow verify are the re-checkable evidence.
sql/buyback_withdraw_sources.sql 1,162 bytes
-- Which intents.near accounts deliver native NEAR to NEAR's revenue wallets (dip4 native_withdraw
-- events), 2026-10-06..11-04, per day, source account and wallet. Recurring sources are fee
-- collectors; single-use sources are fresh accounts that receive NEAR unshielded from the Confidential Intents
-- treasury (PRIVATE_TREASURY_ACCOUNT_ID 51e8f94d...7cbe, docs.near-intents.org) and withdraw it.
SELECT o.block_date AS day,
JSON_VALUE(d, '$.account_id') AS src,
JSON_VALUE(d, '$.receiver_id') AS wallet,
COUNT(*) AS n,
CAST(SUM(CAST(JSON_VALUE(d, '$.amount') AS BIGNUMERIC)) / 1e24 AS STRING) AS near
FROM `bigquery-public-data.crypto_near_mainnet_us.execution_outcomes` o, UNNEST(o.logs.list) l,
UNNEST(JSON_QUERY_ARRAY(SUBSTR(l.element, 12), '$.data')) d
WHERE o.block_date BETWEEN '2026-10-06' AND '2026-11-04'
AND o.executor_account_id = 'intents.near'
AND l.element LIKE 'EVENT_JSON:%native_withdraw%'
AND JSON_VALUE(d, '$.receiver_id') IN ('buybacks.multisignature.near', 'fefundsadmin.sputnik-dao.near',
'1csfundsadmin.sputnik-dao.near')
GROUP BY 1, 2, 3
ORDER BY 1, 2, 3
sql/collector_inflow_funders.sql 2,990 bytes
-- Exploratory (written 2026-11-12, after the freeze). Who funded the fees that reached NEAR's two fee collectors
-- (collector A 5880ad2b..., collector B 143f2bb4..., see sql/collector_inflows.sql), 2026-10-06..11-04.
-- Every dip4 transfer into A or B is classified by its sender (account_id):
-- escrow_direct sender is the Confidential Intents treasury (PRIVATE_TREASURY_ACCOUNT_ID 51e8f94d...7cbe)
-- escrow_funded sender received a dip4 transfer from that treasury between 2026-09-22 and the transfer's block
-- public_swap otherwise, and the same receipt emits a dip4 token_diff for the sender (a public swap intent)
-- other none of the above
-- Per day, collector, class and token: summed raw amounts, transfer count, distinct senders. Summed over class,
-- the rows equal data/raw/bq/collector_inflows.json.
WITH ev AS (
SELECT o.block_date AS day, o.block_height AS h, o.receipt_id AS rid,
l.element AS el
FROM `bigquery-public-data.crypto_near_mainnet_us.execution_outcomes` o, UNNEST(o.logs.list) l
WHERE o.block_date BETWEEN '2026-09-22' AND '2026-11-04'
AND o.executor_account_id = 'intents.near'
AND l.element LIKE 'EVENT_JSON:{"standard":"dip4"%'
AND (l.element LIKE '%"event":"transfer"%' OR l.element LIKE '%"event":"token_diff"%')
),
rows_ AS (
SELECT day, h, rid,
REGEXP_EXTRACT(el, r'"event":"([a-z_]+)"') AS event,
JSON_VALUE(d, '$.account_id') AS sender, JSON_VALUE(d, '$.receiver_id') AS receiver,
JSON_QUERY(d, '$.tokens') AS tokens
FROM ev, UNNEST(JSON_QUERY_ARRAY(SUBSTR(el, 12), '$.data')) d
),
funded AS ( -- first escrow funding of each account
SELECT receiver AS acct, MIN(h) AS first_h
FROM rows_ WHERE event = 'transfer' AND sender = '51e8f94d77b5e90dc9852ca6113771e11e8382ce69473a75e313e41665de7cbe' GROUP BY receiver
),
diffs AS (SELECT DISTINCT rid, sender FROM rows_ WHERE event = 'token_diff'),
inflow AS (
SELECT r.day, r.receiver AS collector, r.sender, r.tokens,
CASE WHEN r.sender = '51e8f94d77b5e90dc9852ca6113771e11e8382ce69473a75e313e41665de7cbe' THEN 'escrow_direct'
WHEN f.first_h IS NOT NULL AND f.first_h <= r.h THEN 'escrow_funded'
WHEN dd.rid IS NOT NULL THEN 'public_swap'
ELSE 'other' END AS class
FROM rows_ r
LEFT JOIN funded f ON f.acct = r.sender
LEFT JOIN diffs dd ON dd.rid = r.rid AND dd.sender = r.sender
WHERE r.event = 'transfer' AND r.day >= '2026-10-06'
AND r.receiver IN ('5880ad2b362620fadf759cbceb1cd5737ce8c6ed7fb8e9942881e6731f9247dd',
'143f2bb439575c286f4f585163f0e5fb4e464f8ce57ec06ae80741407d3cfb31')
)
SELECT day, collector, class, REGEXP_EXTRACT(kv, r'^"([^"]+)"') AS token,
CAST(SUM(CAST(REGEXP_EXTRACT(kv, r':"([0-9]+)"$') AS BIGNUMERIC)) AS STRING) AS amount,
COUNT(*) AS n, COUNT(DISTINCT sender) AS senders
FROM inflow, UNNEST(REGEXP_EXTRACT_ALL(tokens, r'"[^"]+":"[0-9]+"')) AS kv
GROUP BY 1, 2, 3, 4
ORDER BY 1, 2, 3, 4
sql/collector_funder_checks.sql 4,260 bytes
-- Exploratory (written 2026-11-12, after the freeze). Who funded the fees that reached NEAR's two fee collectors
-- (collector A 5880ad2b..., collector B 143f2bb4..., see sql/collector_inflows.sql), 2026-10-06..11-04.
-- Every dip4 transfer into A or B is classified by its sender (account_id):
-- escrow_direct sender is the Confidential Intents treasury (PRIVATE_TREASURY_ACCOUNT_ID 51e8f94d...7cbe)
-- escrow_funded sender received a dip4 transfer from that treasury between 2026-09-22 and the transfer's block
-- public_swap otherwise, and the same receipt emits a dip4 token_diff for the sender (a public swap intent)
-- other none of the above
-- Checks of that classification, per period (post = from 2026-10-27), collector (first character) and class:
-- n_with_diff transfers whose receipt carries a token_diff for the sender
-- n_sender_single_tx transfers whose sender sent exactly one transfer to A or B in the window
-- n_sender_single_day ... whose sender sent to A or B on one day only
-- n_funded_once ... whose sender received exactly one transfer from the treasury since 2026-09-22
-- n_no_other_inflow ... whose sender received no dip4 transfer from any other account since 2026-09-22
-- lag_blocks_q quartiles of blocks from the sender's first treasury funding to the transfer
WITH ev AS (
SELECT o.block_date AS day, o.block_height AS h, o.receipt_id AS rid,
l.element AS el
FROM `bigquery-public-data.crypto_near_mainnet_us.execution_outcomes` o, UNNEST(o.logs.list) l
WHERE o.block_date BETWEEN '2026-09-22' AND '2026-11-04'
AND o.executor_account_id = 'intents.near'
AND l.element LIKE 'EVENT_JSON:{"standard":"dip4"%'
AND (l.element LIKE '%"event":"transfer"%' OR l.element LIKE '%"event":"token_diff"%')
),
rows_ AS (
SELECT day, h, rid,
REGEXP_EXTRACT(el, r'"event":"([a-z_]+)"') AS event,
JSON_VALUE(d, '$.account_id') AS sender, JSON_VALUE(d, '$.receiver_id') AS receiver,
JSON_QUERY(d, '$.tokens') AS tokens
FROM ev, UNNEST(JSON_QUERY_ARRAY(SUBSTR(el, 12), '$.data')) d
),
funded AS ( -- first escrow funding of each account
SELECT receiver AS acct, MIN(h) AS first_h
FROM rows_ WHERE event = 'transfer' AND sender = '51e8f94d77b5e90dc9852ca6113771e11e8382ce69473a75e313e41665de7cbe' GROUP BY receiver
),
diffs AS (SELECT DISTINCT rid, sender FROM rows_ WHERE event = 'token_diff'),
inflow AS (
SELECT r.day, r.h, r.receiver AS collector, r.sender, r.tokens, f.first_h, dd.rid IS NOT NULL AS has_diff,
CASE WHEN r.sender = '51e8f94d77b5e90dc9852ca6113771e11e8382ce69473a75e313e41665de7cbe' THEN 'escrow_direct'
WHEN f.first_h IS NOT NULL AND f.first_h <= r.h THEN 'escrow_funded'
WHEN dd.rid IS NOT NULL THEN 'public_swap'
ELSE 'other' END AS class
FROM rows_ r
LEFT JOIN funded f ON f.acct = r.sender
LEFT JOIN diffs dd ON dd.rid = r.rid AND dd.sender = r.sender
WHERE r.event = 'transfer' AND r.day >= '2026-10-06'
AND r.receiver IN ('5880ad2b362620fadf759cbceb1cd5737ce8c6ed7fb8e9942881e6731f9247dd',
'143f2bb439575c286f4f585163f0e5fb4e464f8ce57ec06ae80741407d3cfb31')
)
, s AS (SELECT sender, COUNT(*) AS n_tx, COUNT(DISTINCT day) AS n_days FROM inflow GROUP BY sender),
fo AS (SELECT receiver AS acct, COUNT(*) AS n_fund FROM rows_ WHERE event='transfer'
AND sender='51e8f94d77b5e90dc9852ca6113771e11e8382ce69473a75e313e41665de7cbe' GROUP BY receiver),
oth AS (SELECT receiver AS acct, COUNT(*) AS n_in_other FROM rows_ WHERE event='transfer'
AND sender!='51e8f94d77b5e90dc9852ca6113771e11e8382ce69473a75e313e41665de7cbe' GROUP BY receiver)
SELECT i.day >= '2026-10-27' AS post, SUBSTR(i.collector,1,1) AS coll, i.class,
COUNT(*) AS n, COUNTIF(i.has_diff) AS n_with_diff, COUNT(DISTINCT i.sender) AS senders,
COUNTIF(s.n_tx = 1) AS n_sender_single_tx, COUNTIF(s.n_days = 1) AS n_sender_single_day,
COUNTIF(fo.n_fund = 1) AS n_funded_once, COUNTIF(oth.n_in_other IS NULL) AS n_no_other_inflow,
APPROX_QUANTILES(i.h - i.first_h, 4) AS lag_blocks_q
FROM inflow i JOIN s USING (sender) LEFT JOIN fo ON fo.acct=i.sender LEFT JOIN oth ON oth.acct=i.sender
GROUP BY 1,2,3 ORDER BY 1,2,3
Data
A table wider than the screen scrolls sideways.
| Rung | % of net issuance | How the NEAR arrived |
|---|---|---|
| All three revenue wallets | 15.81 | sum of the collector, escrow and other-source rows below |
| Of which the buyback wallet alone | 11.00 | a subset of the total, overlapping the rows below |
| Traceable to two recurring public fee collectors | 4.53 | fee collectors A and B |
| … of which fees from publicly settled swaps | 3.97 | the fee payer swapped publicly in the same receipt |
| … of which fees paid from escrow-funded single-use accounts | 0.56 | the escrow funded the payer moments before; all at collector A |
| Released from the Confidential Intents escrow | 11.25 | fee stream unattested |
| One other recurring source | 0.03 | recurring, unnamed |
| Net issuance, NEAR a day (denominator) | 88,295 | two archival total_supply reads, matched to the window |
2. What the price assumes
Growth the price assumes: 84.9% a year to 2031
- Captured revenue now, a year
- $19.6M
- Needed by 2031 (base)
- $424.0M
- That is
- 21.6× today
- Market cap ÷ revenue now
- 245.0×
Notes and sources
For NEAR’s price to rise 15% a year to 2031-11-04 and its market cap then to be 25 times its captured revenue, captured revenue must grow from $19.6M a year to $424.0M, 84.9% a year (54.0% to 131.7% across the grid), if Intents carried the price alone. The cross-chain venues tracked here grew 13.4% last year, all of it Intents’ own growth (×9.0): without Intents the venues’ volume changed by -53.4%. Over four years the set grew 47.1% a year, 15.4% without Intents.
What it shows: A reverse DCF: the growth in captured Intents revenue that today’s market cap implies, for a required return and a revenue multiple in 2031 (both assumptions, shown as a grid), with supply growth on the rating rule’s own path, against what the cross-chain swap market has done.
What it does not show: A valuation of NEAR as a whole. NEAR’s market cap also prices the L1 (its fees, which burn, staking and any monetary premium); here all of it is set against Intents’ captured revenue, so the growth shown is what Intents would need if it carried the price alone.
| Required return | 10× revenue in 2031 | 25× revenue in 2031 | 50× revenue in 2031 |
|---|---|---|---|
| 10% a year | 112.4% | 76.9% | 54.0% |
| 15% a year | 122.1% | 84.9% | 61.0% |
| 20% a year | 131.7% | 92.9% | 68.0% |
- The required return is on NEAR’s price. Supply grows and the buybacks burn nothing, so for the price to rise at that rate the market cap must grow faster by the supply factor, 1.094× by 2031; a holder who stakes also receives part of the new supply.
- For comparison, THORChain’s market cap is 9.8× its gross fees and Chainflip’s 1.8× (see the peer card). The grid’s multiples are on captured revenue; the peers’ multiples on what reaches their token holders would be higher and are not computed here.
- Last year’s growth of the set is all Intents’ growth, and part of it is DefiLlama’s change on 2026-09-01 in what it counts as Intents volume (docs/leg-count.md): as a measure of the market it is generous to NEAR.
- The market’s growth depends on the window: 76.9% a year over three years starts at the low of $9.6B; the annual volumes were $11.3B, $9.6B, $55.1B, $46.7B and $53.0B (oldest first). The two-year rate is negative and is drawn at zero.
- G_obs, the rule’s observed growth in captured revenue (619.0% a year), is left off the axis: it comes from a step in the share of fees captured, while gross fees and volume grew far less.
- Supply grows 1.094× to 2031-11-04 with HSP-029. Market: THORChain, Chainflip, Maya and NEAR Intents (DefiLlama, reported basis), full years to the as-of date.
Source:
- Raw snapshot:
data/raw/llama/dailyRevenue_near-intents.jsonsha256 1c07e697a9afdata/raw/llama/volume_near-intents.jsonsha256 8fcf1cdd855fdata/raw/llama/volume_thorchain-dex.jsonsha256 33f425395933data/raw/llama/volume_chainflip-amm.jsonsha256 597c6e6bd83edata/raw/llama/volume_maya-protocol.jsonsha256 fc0d9b05af6ddata/raw/coingecko/near_snapshot.jsonsha256 199d54d4131bdata/raw/rpc/epoch_issuance.jsonsha256 2937ac18000adata/raw/rpc/rating_assumptions.jsonsha256 dda808e7f742
- Code:
pipeline/investment_case.py,pipeline/model.py,pipeline/h1a.py
Query
- Model
python3 -m pipeline.compute (calls pipeline.investment_case.investment_case); offline, standard library- Metrics
ic_* in data/metrics.json
Data
A table wider than the screen scrolls sideways.
| Required return | 10× revenue in 2031 | 25× revenue in 2031 | 50× revenue in 2031 |
|---|---|---|---|
| 10% a year | 112.4% | 76.9% | 54.0% |
| 15% a year | 122.1% | 84.9% | 61.0% |
| 20% a year | 131.7% | 92.9% | 68.0% |
3. What would have to give
Take NEAR would need: 2.5× Intents’ whole gross fee
- Take needed ÷ whole gross fee
- 2.5×
- Market growth needed at the whole fee
- 35.7% a year
- Market growth, last year
- 13.4%
Notes and sources
Captured revenue = cross-chain swap volume × Intents’ share × NEAR’s take. To multiply by 21.6 by 2031, with the market growing at its last-year pace (×1.87) and Intents’ share at its twelve-month high (×1.27), NEAR’s take would have to rise ×9.1, from 4.13 bp to 37.4 bp of volume: 2.5 times the whole 15.2 bp gross fee Intents charges today. Even if NEAR kept the whole gross fee, the market would have to grow 35.7% a year.
What it shows: The required multiple from the reverse DCF (base assumptions), split into its three factors: the growth of the cross-chain swap market, Intents’ share of it, and the share of volume NEAR captures as revenue, each at a value from the data, and what is left for the take rate.
What it does not show: That the take rate cannot rise: fees are a policy choice. It shows how far the current fee structure is from what the price implies, if the market grows as it has.
- Intents’ share of the peer set over the 90 days was 61.7%; its twelve-month high was 78.6% (2026-06) and its low 48.5% (2026-04).
- Each factor is on DefiLlama’s reported volume, which counts both legs of some swaps and, from 2026-09-01, more of Intents’ volume (docs/leg-count.md). Only the full product, the revenue, is unaffected. Last year’s market growth is all Intents’ and partly that change, so it is generous to NEAR, and the take needed is, if anything, understated.
- Take and gross fee are DefiLlama revenue and fees ÷ volume, on the reported basis.
Source:
- Raw snapshot:
data/raw/llama/dailyRevenue_near-intents.jsonsha256 1c07e697a9afdata/raw/llama/volume_near-intents.jsonsha256 8fcf1cdd855fdata/raw/llama/volume_thorchain-dex.jsonsha256 33f425395933data/raw/llama/volume_chainflip-amm.jsonsha256 597c6e6bd83edata/raw/llama/volume_maya-protocol.jsonsha256 fc0d9b05af6ddata/raw/coingecko/near_snapshot.jsonsha256 199d54d4131bdata/raw/rpc/epoch_issuance.jsonsha256 2937ac18000adata/raw/rpc/rating_assumptions.jsonsha256 dda808e7f742data/raw/llama/fees_near-intents.jsonsha256 20099b72ae5c
- Code:
pipeline/investment_case.py
Query
- Model
python3 -m pipeline.compute (calls pipeline.investment_case.investment_case); offline, standard library- Metrics
ic_* in data/metrics.json
Data
A table wider than the screen scrolls sideways.
| Factor | Value |
|---|---|
| Required multiple of captured revenue | 21.6× |
| Market, last-year pace for five years | 1.87× |
| Share, twelve-month high ÷ 90 days | 1.27× |
| Left for the take rate | 9.1× |
| Take today, bp | 4.13 |
| Gross fee today, bp | 15.2 |
| Take needed, bp | 37.4 |
4. Three futures from the data
Dilution paid for in 2031: 3.5% bear, 44.6% base, 277.5% bull
Notes and sources
With every input at a value from the data and the price held flat, captured revenue on 2031-11-04 would pay for 3.5% (bear), 44.6% (base) or 277.5% (bull) of the dollar value of NEAR’s dilution. The bull case’s $228.6M a year is 53.9% of the $424.0M the price would assume at 15% and 25×; at the three-year market pace it would be 136.0%. Market growth and NEAR’s price move coverage most: from 21.6% to 163.8% and from 27.8% to 169.8%.
What it shows: Three futures for captured revenue (market growth × Intents’ share × NEAR’s take), each input at a value from the data, run against the rating rule’s supply path at its constant (flat) price; then the base case with one input at a time at its low and high value. Coverage is what captured revenue would pay for: not all of it reaches the buyback wallet, and none of it is burned.
What it does not show: Probabilities: the scenarios are not weighted (the Monte Carlo card gives a distribution). Nor a new fee stream, a partner change or a regime the data have not seen.
- Bear: market at its two-year pace, share at its twelve-month low (2026-04), take at its lowest month since the fee switch (2026-04), no HSP-029. Base: last-year market growth and the last 90 days’ share and take, with HSP-029. Bull: four-year market pace, twelve-month-high share (2026-06), highest month’s take (2026-10), with HSP-029.
- Coverage moves in inverse proportion to NEAR’s price, because each dollar of revenue buys back less NEAR at a higher price: the 365-day range, $0.96 to $5.89, moves the base case from 27.8% to 169.8%.
- Which window anchors each case was chosen after the annual volumes, monthly shares and monthly take rates were computed (PREREG-ADDENDUM.md, 2026-11-14 entries); the card on what the price assumes lists every window, so a reader can substitute another.
- The bull case grows the whole peer set at its four-year pace and also lifts Intents’ share, so it counts some of Intents’ share gains twice. Its revenue growth, 63.4% a year, falls short of what the price would assume at 25× and exceeds it only at 50× (54.0% at 10% a year, 61.0% at 15%).
- At today’s market cap, NEAR would trade at 131.1× its 2031 captured revenue in the base case and 21.1× in the bull case.
Source:
- Raw snapshot:
data/raw/llama/dailyRevenue_near-intents.jsonsha256 1c07e697a9afdata/raw/llama/volume_near-intents.jsonsha256 8fcf1cdd855fdata/raw/llama/volume_thorchain-dex.jsonsha256 33f425395933data/raw/llama/volume_chainflip-amm.jsonsha256 597c6e6bd83edata/raw/llama/volume_maya-protocol.jsonsha256 fc0d9b05af6ddata/raw/coingecko/near_snapshot.jsonsha256 199d54d4131bdata/raw/rpc/epoch_issuance.jsonsha256 2937ac18000adata/raw/rpc/rating_assumptions.jsonsha256 dda808e7f742data/raw/coingecko/near_market_chart_365d.jsonsha256 3cb5249d777e
- Code:
pipeline/investment_case.py,pipeline/model.py
Query
- Model
python3 -m pipeline.compute (calls pipeline.investment_case.investment_case); offline, standard library- Metrics
ic_* in data/metrics.json
Data
A table wider than the screen scrolls sideways.
| Bear | Base | Bull | |
|---|---|---|---|
| Market growth a year, % | -1.9 | 13.4 | 47.1 |
| Intents' share, % | 48.5 | 61.7 | 78.6 |
| NEAR's take, bp | 1.36 | 4.13 | 5.49 |
| HSP-029 in force | no | yes | yes |
| Captured revenue in 2031, $M a year | 4.6 | 36.7 | 228.6 |
| Captured revenue growth a year, % | -25.1 | 13.4 | 63.4 |
| Coverage of dilution on 2031-11-04, % | 3.5 | 44.6 | 277.5 |
| Today's market cap ÷ 2031 revenue, × | 1,041.1 | 131.1 | 21.1 |
| Share of the revenue the price assumes, % | 1.1 | 8.7 | 53.9 |
5. How uncertain it is
Monte Carlo: 31.8% of paths pay for all dilution by 2031, 3.3% without one month
pipeline/model.py, a fixed seed, 60 model months from 2026-11-04. Unit: percent. Panel A’s axis is logarithmic.- Coverage today
- 16.6%
- Median, 2031-11-04
- 38.2%
- All dilution covered by 2031
- 31.8% of paths
- Take rate held at
- 4.13 bp
Notes and sources
Captured Intents revenue covers 16.6% of the USD value of NEAR’s net new supply today. Over 10,000 paths that replay the volume and price changes of 11 months of data (price drift removed), the median reaches 19.9% by 2027-11, 26.6% by 2028-11 and 38.2% by 2031-11-04, and 31.8% of paths cover all of it by then (24.5% without HSP-029). If the price keeps its last-year trend, that falls to 0.9%; without the 2026-08 to 2026-09 month, which spans DefiLlama’s change in what it counts, to 3.3%. The bands are as wide as the data make them, so the thesis does not rest on these probabilities.
What it shows: The frozen rating rule’s question (does captured revenue reach the USD value of net new supply by 2031-11-04?) with a distribution in place of one price and one growth rate: 10,000 paths, each month drawing one of the 11 monthly changes in Intents volume and NEAR’s mean price (2025-12 to 2026-10) together, against the rule’s own supply path.
What it does not show: A forecast of NEAR’s price or a valuation. Eleven months of data cannot pin a five-year trend: the bands are as wide as the data make them, the take rate is held where it is, and no new fee stream, partner change or regime is modelled.
- The volume drift comes from one month: the 2026-08 to 2026-09 change spans DefiLlama’s 2026-09-01 change in what it counts as Intents volume. Without that month volume changed by -4.5% a month, the 2031 median is 1.5% and 3.3% of paths cover all dilution. The forecasts M1 to M4 were dated with the month in and are scored as dated; the thesis does not rest on them (PREREG-ADDENDUM.md, 2026-11-14 entries).
- Volume and price move together in the data: the correlation of their monthly log changes is 0.54, so each month’s two changes are drawn together.
- The price drift is removed because NEAR’s mean price rose 7.4% a month on average over those months; replaying that for five years would assume the trend continues. With it, the 2031 median is 0.6%: a higher price means each dollar of revenue buys back less NEAR.
- Volume keeps its sample drift, 0.8% a month. The take rate is captured revenue ÷ volume over the last 90 days, 4.13 bp, held fixed; coverage moves in proportion to it.
- P3 (frozen in PREREG.md with probability 35.0%) asks whether coverage is at least 25% on 2027-11-04. The model, built after the freeze, gives 39.6%; P3 is scored on the data alone.
- Coverage today here is computed in USD at one price, as the rating rule does; the ladder’s 15.81%-of-issuance figure counts NEAR as it arrived, so the two differ slightly.
- In Panel A, values below the axis floor are drawn at the floor. The model feeds nothing the rating rule computes.
Source:
- Raw snapshot:
data/raw/llama/dailyRevenue_near-intents.jsonsha256 1c07e697a9afdata/raw/llama/volume_near-intents.jsonsha256 8fcf1cdd855fdata/raw/coingecko/near_market_chart_365d.jsonsha256 3cb5249d777edata/raw/rpc/epoch_issuance.jsonsha256 2937ac18000adata/raw/rpc/rating_assumptions.jsonsha256 dda808e7f742
- Code:
pipeline/model.py,pipeline/h1a.py,pipeline/compute.py
Query
- Model
python3 -m pipeline.compute (calls pipeline.model.forward); offline, standard library, fixed seed- Series
fwd_fan in data/series.json
Data
A table wider than the screen scrolls sideways.
| Month | 10th pct, % | 25th pct, % | 50th pct, % | 75th pct, % | 90th pct, % |
|---|---|---|---|---|---|
| 2026-11-04 | 16.61 | 16.61 | 16.61 | 16.61 | 16.61 |
| 2027-02-03 | 10.50 | 13.07 | 16.74 | 21.54 | 26.04 |
| 2027-05-06 | 7.86 | 11.44 | 17.24 | 25.86 | 36.77 |
| 2027-08-05 | 6.79 | 10.82 | 18.69 | 31.16 | 49.12 |
| 2027-11-04 | 5.92 | 10.67 | 19.87 | 36.56 | 63.20 |
| 2028-02-04 | 5.38 | 10.30 | 21.02 | 42.29 | 78.46 |
| 2028-05-05 | 5.11 | 10.43 | 22.67 | 49.09 | 96.76 |
| 2028-08-04 | 4.81 | 10.54 | 24.71 | 56.22 | 120.74 |
| 2028-11-03 | 4.56 | 10.82 | 26.65 | 65.43 | 146.45 |
| 2029-02-03 | 4.28 | 10.80 | 28.68 | 74.60 | 182.08 |
| 2029-05-05 | 4.19 | 11.02 | 30.91 | 85.83 | 212.24 |
| 2029-08-04 | 3.91 | 10.86 | 31.24 | 92.31 | 238.83 |
| 2029-11-04 | 3.62 | 10.25 | 31.40 | 96.07 | 269.27 |
| 2030-02-03 | 3.37 | 10.09 | 32.41 | 104.92 | 298.12 |
| 2030-05-05 | 3.17 | 9.81 | 32.95 | 109.33 | 341.66 |
| 2030-08-05 | 2.96 | 9.39 | 33.30 | 116.76 | 366.11 |
| 2030-11-04 | 2.84 | 9.52 | 34.07 | 124.73 | 420.29 |
| 2031-02-03 | 2.75 | 9.32 | 35.37 | 130.57 | 470.93 |
| 2031-05-06 | 2.58 | 9.10 | 36.36 | 139.09 | 502.40 |
| 2031-08-05 | 2.46 | 8.91 | 37.65 | 147.06 | 543.04 |
| 2031-11-04 | 2.39 | 8.90 | 38.23 | 156.16 | 590.35 |
6. What to watch
Signposts: the take rate and market growth are far from what the price needs
Notes and sources
Of the lines that would favour the upside, Intents’ share is past its own (113.0% of P1’s line), revenue and coverage are close (81.0% and 71.0%), and the two that carry the price are far: market growth is 40.0% of G_req and NEAR’s take 11.0% of what the price needs. In the scoring week, though, Intents was 37.2% of the peer set’s volume (F4).
What it shows: The values a reader should watch, each against the line that would favour the upside: the pre-registered P1 to P3, the model’s M1, the rating rule’s G_req, the take the price needs, and H1a’s line.
What it does not show: A score: P1 to P3 and M1 to M4 resolve on their own dates, from the data, and are scored as written.
- For staking the line is H1a’s line (net staking outflow under half of staking rewards) divided by today’s ratio, so a full bar would mean stakers are no longer net sellers of their rewards.
Source:
- Raw snapshot:
data/raw/llama/dailyRevenue_near-intents.jsonsha256 1c07e697a9afdata/raw/llama/volume_near-intents.jsonsha256 8fcf1cdd855fdata/raw/llama/volume_thorchain-dex.jsonsha256 33f425395933data/raw/llama/volume_chainflip-amm.jsonsha256 597c6e6bd83edata/raw/llama/volume_maya-protocol.jsonsha256 fc0d9b05af6ddata/raw/coingecko/near_snapshot.jsonsha256 199d54d4131bdata/raw/rpc/epoch_issuance.jsonsha256 2937ac18000adata/raw/rpc/rating_assumptions.jsonsha256 dda808e7f742
- Code:
pipeline/investment_case.py,pipeline/compute.py
Query
- Model
python3 -m pipeline.compute (calls pipeline.investment_case.investment_case); offline, standard library- Metrics
ic_* in data/metrics.json
Data
A table wider than the screen scrolls sideways.
| Signpost | Today | Line that favours the upside | When |
|---|---|---|---|
| Coverage of dilution (P3’s quantity, 90 days) | 17.8% | at least 25% (P3, frozen; M1, exploratory, dated after the freeze) | 2027-11-04 |
| Captured revenue, 90 days | $4.84M | at least $6.0M (P2, frozen) | 2027-05-04 |
| Intents’ share of the peer set, 365 days | 62.1% | at least 55% (P1, frozen) | 2027-05-04 |
| Intents’ share of the peer set, scoring week 2026-11-06 to 2026-11-13 | 37.2% | at least 50% (F4, frozen) | scored: did not come true |
| Cross-chain swap volume, growth a year | 13.4% | 33.2% (G_req, if share and take stay where they are) | each year |
| NEAR’s captured take, 90 days | 4.13 bp | 37.4 bp (what the price would need, at last year’s market pace and Intents’ twelve-month-high share) | each month |
| Net staking outflow ÷ staking rewards (H1a) | 6.56× | under 0.5× (H1a’s line) | each quarter |
| HSP-029’s issuance cut | not yet in force | in force (a lower inflation cap) | timelock ends 2026-11-16 |
| A per-stream attestation of the escrow releases | none | published by NEAR (collapses the ladder’s range) | any time |
The view
Intents led its market over the year to 2026-11-04, but as a claim on Intents’ fees NEAR is priced for more growth than the data show at today’s fees: the bull case reaches 53.9% of the revenue the price would assume.
- Base case: captured revenue would pay for 44.6% of NEAR’s dilution in 2031.
- To close the gap in today’s market, NEAR would have to capture 2.5× Intents’ whole gross fee.
- Pre-registered: net staking outflow was 6.56× staking rewards, where H1a predicted under 0.5×; exchange flows come out as ranges the labels cannot settle, so the frozen rating rule gives no signal.
- Forward tests, scored 2026-11-14: 2 of the four frozen predictions came true and 2 did not; the Monte Carlo’s forecasts are dated in the addendum and resolve from 2027.
- Carried to 2026-11-13 with the same code: the price assumes 79.8% a year, NEAR would need 1.6× Intents’ whole gross fee, and the base case pays for 62.2% of the dilution in 2031.
Re-run it: git clone https://github.com/notveiker/near-flow-statement && cd near-flow-statement && make site. Research only; nothing here is investment advice.