Valuation summary for this round: VANA’s current price is $1.0842 (verified on 2026-10-06 at 02:06 +0800); opening a new position is currently not recommended. Bear-case valuation: $0.0015; base-case valuation: $0.168; bull-case valuation: $1.559; current weighted valuation: $0.387925; weighted valuation one year from now (2027-10-06): $0.503745. Recommended entry price ranges: watch zone: $0.28–$0.32; core zone: $0.18–$0.22; panic zone: $0.08–$0.12. (Entries must meet the conditions stated in the main text; if the fundamentals thesis is invalidated, cancel the remaining tranches.)
Data as of: October 6, 2026. Amounts are in USD; spot market prices are approximated using USDT quotes and should be recalibrated if USDT depegs.
My assessment: the product is worth researching; the token still needs to prove its value
Vana does not offer a public data-download directory, but an infrastructure that lets users control their private data and allows applications to access it within authorized limits and pay for that access. The question of its value is specific: AI applications increasingly need to understand users, but users' chat, fitness, spending, and health information is spread across different platforms. If authorized data can be reused across multiple applications, those applications may be willing to pay repeatedly, and users would not have to rebuild their profile from scratch every time they switch apps.
This demand is worth tracking. But a useful product and VANA being worth buying at its current price require two separate proofs. The first is that real applications are willing to pay for data access. The second is that this money can be converted sustainably and verifiably into economic benefits for token holders, while also being enough to absorb new supply. My assessment: Vana's paid data-portability mechanism is worth following, but VANA's current price depends on strong adoption expectations. I do not recommend opening a new position at this time. First, verify genuine repeat purchases, execution of value capture, security, and supply.
This also explains why a decline from the all-time high does not automatically mean the token is cheap. A low price may reflect excessive past expectations, gradual supply releases, or commercial demand that has not reached previous expectations. Investment decisions should return to revenue, value capture, and supply—not to an old price you remember.
Why might people pay for user data?
Users store data on personal servers. An application requests access to a category of data, and the user decides what to authorize, for whom, and for how long. Identity, permissions, and data records are stored on-chain, while the private source data is primarily stored off-chain; personal servers provide access according to the authorization. A DataDAO is one type of application that can be built on this infrastructure. Not every data read should be understood as a sale of a DAO's dataset.
Repeat reads are the fee-generating activity with the greatest potential to scale. Once an application receives authorization, it can repeatedly access updated data within the permitted scope. So one data connection could serve multiple applications, and one application could continue using the same data. To prove network effects, the key is not the number of connections, but whether applications keep using and paying after receiving permission, and whether new applications can reuse existing data connections.
I also have a clear opposing view: users' own local memory, platform-specific context, and other personal data-storage protocols can solve some of these problems too. Solid already provides user-controlled data storage and application permissions, showing that “users control their data” does not inherently require a tradable token. Vana's advantage may lie in combining identity, authorization, verifiable records, and payment. But open standards also make it easier for alternatives to integrate, and adoption of a standard does not directly translate into revenue for the Vana chain.
Payment intensity is also constrained by costs. If an application reads a user's data 1,000 times a day, at one cent per read that would mean $10 in protocol fees per day, before model and application costs. The technology may allow high-frequency reads, but will buyers be willing to pay those prices continuously? Actual demand will depend on current fees, the granularity of permissions, and alternatives.
So I am not assigning this project a seemingly precise total addressable market, nor multiplying the size of the entire AI industry by an arbitrary share. For now, it is more valuable to verify the number of paying applications, repeat purchases, non-subsidized fees, and cross-application use, then assess whether this can become infrastructure.
What has happened, and what is still missing
The operating dashboard I accessed directly shows 208 registered applications, about 608,000 permission grants, about 689,000 personal servers, and about 4.441 million cumulative settled scoped reads. Total settled protocol fees are about $44,400. Multiplying the read count by the current rate of $0.01 per read corresponds to this cumulative fee total, showing that measurable fee-generating activity already exists.
But these figures cannot be combined into hundreds of thousands of paying users. A personal server may not correspond to a unique individual, a registered application may not make ongoing payments, and a permission grant may never be used frequently. The dashboard also lists 1,090 users connected to more than three data sources, a 79% repeat-access metric, and a 13% cross-application metric. These are worth monitoring, but they are not direct measures of revenue retention. The objects of repeat access, who pays, and the measurement window still need confirmation.
The most recent complete week of disclosed activity had about 1.532 million settled reads, equivalent to about 219,000 per day. If that pace continued for a full year and every read were paid at one cent, the annualized fee run rate would be about $800,000. But this is an extrapolation from one recent complete week, not $800,000 already received or annual revenue validated across different cycles. Whether the revenue is independent of ecosystem rewards and whether applications will keep paying as subsidies decline remain key unknowns.
Public deployments, development code, and historical fundraising indicate that the project has development resources. Cumulative historical funding is about $25 million, with participating capital including Polychain, Paradigm, and a venture firm affiliated with a trading platform. Capital can support development and distribution, but it cannot replace product customers. Nor should the assets of the development company or foundation be treated as equity belonging to VANA holders. The team should be assessed based on continued delivery, permission constraints, and business performance. The identities of the ultimate beneficial owners of the development company, foundation, and on-chain addresses cannot all be established from public information.
There is now mainnet evidence of permissioning, scoped reads, and fees, so the project can no longer be described as purely conceptual. On the other hand, an independent audit report for the new data-portability contracts has not yet been published. Some more complete protocol encryption and data-provenance capabilities also need to be distinguished between what is already live and what remains a future goal. The project is in a commercial validation phase, not a mature, stable operating phase.
How money flows into VANA, and why that does not mean everyone gets dividends
The current documentation prices a scoped read following one authorization at $0.01, settled in USDC. Of the fee, 60% goes to staking pools, 20% is used for buybacks and burns, and 20% supports the ecosystem. With the default 5% operating commission, the 60% staking-pool share is further divided into 57% for delegators and 3% for operators.
Three things must be distinguished here. The application pays the protocol fee; separate fees charged for commercial hosting services should not be included. A budget for buying VANA on the market does not mean every purchase has actually been executed. VANA distributed to stakers may be sold again, and only the portion actually burned permanently reduces supply. Idle holders do not automatically receive the 57% delegator share. Staking has conditions and a waiting period, and involves permission, exit, and security risks.
At the time, the operating dashboard showed a total of about 1,347.3 tokens burned across two Splitter burns. After checking all burn events in the current contracts, I also confirmed a successful burn of about 1,007.2 tokens on October 2, bringing the total across the three transactions to about 2,354.5. The dashboard has an update lag, so I use the verified on-chain total here. This is still far from proving that the network as a whole has become net deflationary. Public records list buyback allocations, actual spending, and burns separately, and include reporting caveats about the funding source for some planned amounts. Until market purchases and fund attribution are fully reconciled transaction by transaction, the entire fee budget cannot be treated as realized token value capture.
The current allocation contract's burn rate is 25% of the VANA allocation budget, not 25% of all USDC protocol fees. The three burn events alone also do not prove that the corresponding USDC fees were used to make market purchases. These two flows still need to be reconciled transaction by transaction.
Annual validator issuance remains about 441,000 tokens, and does not automatically fall to zero as fees increase. Using the current price in this analysis of about $1.08 and a 20% burn allocation, a static calculation suggests annual fees of about $2.38 million would be needed to offset this annual issuance if the entire corresponding budget were successfully used for buybacks and burns. At a one-cent fee, that would equate to about 650,000 paid reads per day. Price, fees, allocations, and execution can all change this threshold. It is a sensitivity estimate, not a guarantee of deflation.
Unlocks and new issuance must also be kept separate. Even if buybacks exactly offset validator issuance, that does not mean they can offset team, investor, and ecosystem holdings entering the market. Protocol demand growth has to contend with both distinct sources of supply pressure.
VANA also serves as the native gas token and is used for validator staking. But the number of transactions across the network is not gas revenue, and nominal collateral is not new external net buying. There is currently no sufficiently stable, attributable gas revenue or new independent staking demand to support adding a separate validator scarcity premium. To avoid double-counting data fees and staking rewards, I also discount governance utility because control currently sits with the multisig in practice, rather than capitalizing unproven token-holder control. If these sources of demand can be quantified separately in the future, the model can be adjusted.
Supply and holders: distinguish issuance, unlocking, circulation, and selling
About 112.6 million tokens were issued at genesis by the time of listing. Initial market circulation was about 30.084 million tokens, while the maximum or policy supply was 120 million. The current operating dashboard lists about 114.5 million tokens issued, while the supply section still notes an earlier data cutoff. These figures describe different things and should not be averaged together. Nor should 120 million minus the current low circulating supply be treated as inevitable selling pressure next year.
The allocation is 18.8% for the team, 14.3% for investors, 44% for the community, and 22.9% for the ecosystem. The team and investors together account for 33.1%, making vesting wallets, release pace, and selling behavior important subjects for research. Community and ecosystem tokens do not follow a simple, uniform linear release schedule. Official tables and text also differ on the lockup period, referring to both 13 months and a one-year cliff; this uncertainty should be clearly retained for verification.
The currently accessible unlock calendar lists about 1.4 million tokens each on October 16, November 16, and December 16, and about 6.1 million on January 16, 2027. So scheduled releases over the next 30 and 90 days are about 1.4 million and 4.2 million tokens, respectively. For the next 180 days, a pressure scenario that includes five regular releases of about 1.4 million each and one concentrated release of about 6.1 million totals about 13.1 million tokens. Over 365 days, ten regular releases and two concentrated releases would amount to about 26.2 million tokens. The next concentrated release within the six-month period has not yet been confirmed entry by entry in the calendar accessible for this review, so it must explicitly remain an assumption. The latter two figures are estimates based on the current pace, not established quantities of tokens verified wallet by wallet as destined for sale; they must be recalculated if the non-linear schedule changes.
Tokens being released do not necessarily enter the market immediately, and released tokens that are not yet circulating may also be sold. The next step is to link recipient addresses, lockup status, and exchange inflows to turn “scheduled unlocks” into “potentially sellable supply.” There is currently no reliable basis for stating the actual tradable circulating supply one year from now. So for valuation, I use the full 120 million policy supply as a conservative denominator, rather than relying on an unproven assumption that circulation will remain permanently low. This denominator does not mean all tokens will be circulating on the market in a year.
The largest address on the native mainnet balance list holds about 33.445 million tokens, and the top ten addresses hold about 92.961 million in total. This concentration of addresses warrants caution, but it cannot be directly described as ten independent whales controlling the same proportion: the addresses may include locked tokens, custodians, cross-chain holdings, or common beneficial owners. There is not enough evidence to label all large addresses as belonging to the foundation, exchanges, or market makers. Nor can the number of holders of bridged tokens on other chains be substituted for the holder distribution across the whole network.
Governance and security: who can actually change the rules
For this review, I checked key contracts at a fixed mainnet block. Admin roles for critical contracts covering permissions, fees, servers, application registration, and staking are concentrated in one multisig address. That address returns seven signer addresses and a three-signature threshold. The admin role controls upgrades to the permissions contract and fee settings in the fee contract. This is closer to the actual current power structure than simply looking at claims about a “governance token.” The admin, maintenance, and allocation roles for the allocation contract are also currently concentrated in the same multisig. An old candidate for authorization to an external executor has expired, and role-by-role queries confirm that the external address does not currently hold any of those three permissions.
This does not prove that the seven signer addresses are all independent entities, nor that every action goes through a token-holder vote. I also located and read the complete transaction indexes for the actual admin and maintainer multisigs, containing 79 and 17 transactions, respectively, then opened each of the seven candidates marked as unexecuted. All had transaction nonces below the current mainnet nonce and were old records superseded by other transactions with the same nonce. Some had gathered all the required signatures, but they can no longer be treated as valid pending actions. The latest three allocation and burn calls have been checked against successful mainnet transactions and events. This current execution path can be studied, but it is not a token-holder vote. The public community proposal portal remains unconfirmed, and discussions that have not been submitted are not visible. Therefore, I do not claim there are no other significant governance matters, nor do I treat future governance promises as protections that exist today.
The research conclusion here is not to find an entry point and feel reassured, but to acknowledge that the capture terms can change. Lower fees, a reduced buyback share, changes to supply policy, or a transfer of admin control could all invalidate today's valuation. The published source code allows admin actions, so general security statements alone are not enough to assume that every economic change is constrained by an unavoidable timelock. The multisig's full execution path and its constraints still need ongoing review.
Security is about more than whether an audit has been conducted. Published audits cover earlier components and do not vouch for the new protocol. User devices, browser sessions, and connectors handle sensitive data; wallet signatures and encryption materials, permission checks, proxy upgrades, and cross-chain assets each introduce different risks. Revoking data access mainly prevents future access; copies an application has already lawfully obtained do not automatically disappear when access is revoked on-chain.
Data portability, authorized access, and use for AI training are not the same right. The data source, purpose, information about other people, and applicable regional requirements must be verified separately. On-chain consent records are a traceable control mechanism, but they do not automatically prove that all subsequent use is lawful. For sensitive data such as health and genetic information, an incident could affect not only the token price, but also user trust and ongoing willingness to pay.
How I value it, and the assumptions behind the numbers
This analysis discounts three years of fee-based economic value and includes a terminal value at the end of year three. Each year's economic benefit equals annual protocol fees multiplied by the effective economic capture rate. I discount each year's benefit and the year-three terminal value to today, then divide by the 120 million token supply. This estimates the economic value the token might capture; it is not a company equity valuation or a guarantee of the market price.
The effective capture rate does not rewrite the current 60/20/20 allocation. The bearish scenario counts only the 20% burn channel. The base case uses 50%, reflecting partial staking participation and execution conditions. The bullish case counts at most 57% in delegated rewards after the default commission, plus 20% for burns. This models conditional economic benefits; it does not mean every idle token is legally entitled to the same cash flow. Operating costs, permissions, eligibility to participate, exit conditions, and execution risk call for a high discount rate and a cautious capture rate.
Bearish scenario, 35% weight: annual protocol fees over the next three years are $300,000, $200,000, and $200,000, respectively, with no sustained expansion in demand. The capture rate is 20%, the terminal value is 8 times year-three economic benefit, and the annual discount rate is 45%. The model gives a value today of about $0.0015 per token, close to a failure scenario with very little residual value. This is not a risk-free price floor.
Base scenario, 45% weight: annual fees over the three years are $800,000, $2 million, and $5 million, respectively, as existing usage gradually turns into repeat-purchase business. The capture rate is 50%, the terminal multiple is 18x, and the annual discount rate is 35%. Year-three fees of $5 million imply about 500 million paid reads annually, not $5 million in company profit. The model gives a value today of about $20.15 million, or about $0.168 per token.
Bullish scenario, 20% weight: annual fees over the three years are $2 million, $8 million, and $20 million, respectively, as cross-application data use reaches a clearly larger scale. The capture rate is 77%, the terminal multiple is 25x, and the annual discount rate is 30%. Year three would require about 2 billion paid reads annually, or about 5.48 million per day, far above the pace in the most recent full week disclosed. The model gives a value today of about $187.1 million, or about $1.559 per token.
The three scenarios are mutually exclusive and their weights total 100%. Based on the displayed prices, the weighted value today in this analysis is about $0.388. However, about 80% of the weighted value comes from the bullish scenario, which has only a 20% weight, and terminal value accounts for most of the value in the base and bullish models. This means the weighted figure still depends heavily on expectations of long-term adoption and should not be understood as a firm support level.
To reproduce the calculation, take the base case: year-one economic benefit of $400,000 is discounted by 1.35; year-two benefit of $1 million is discounted by 1.35 squared; and year-three benefit of $2.5 million plus a $45 million terminal value is discounted by 1.35 cubed. The total is about $20.15 million, which is then divided by 120 million tokens. All future fees, capture rates, multiples, probabilities, and discount rates are assumptions in this analysis, not facts that have already occurred.
Sensitivity also directly affects what to do. If the base-case capture rate falls from 50% to 20%, with all other assumptions unchanged, the base-case value drops to about $0.067. If 10 percentage points of probability shift from the bullish scenario to the base case, the weighted value falls to about $0.249. Conversely, using 60 million rather than 120 million tokens as the denominator would double the price, but until future circulation is fully accounted for, I do not treat this more optimistic denominator as fact.
How to calculate value one year from now
The one-year date is October 6, 2027. I do not multiply today's market price by an expected gain or simply relabel the year-three target price as the price one year from now. Instead, conditional on year-one business performance, I count only the economic benefits from years two and three that have not yet been generated, plus the year-three terminal value. Earnings already generated in year one are not counted again in the future price.
The bearish, base, and bullish scenarios require year-one annual fees of about $300,000, $800,000, and $2 million, respectively; paying applications, repeat purchases, and risk conditions must each materialize. The corresponding residual model values one year from now are about $0.0017, $0.223, and $2.014. Applying the same weights of 35%, 45%, and 20% gives a weighted value of about $0.504. The model still uses the conservative 120 million token denominator; it does not quietly substitute an unverified, smaller market circulation figure.
A higher weighted value one year from now does not mean the price will necessarily rise. If year-one payments or repeat purchases fail to materialize, capture terms change, supply policy does not hold, or security risks increase, the analysis should be redone based on the facts at that time. The original probabilities and future prices cannot simply be carried forward. Even under the current assumptions, the weighted value one year from now is still below the current price in this analysis. There is no support in the model for the idea that simply waiting a year guarantees a return to breakeven.
What to do at the current price, and what conditions must be met at lower prices
At about $1.08, the current price in this analysis is well above the weighted valuation of about $0.388, so I do not recommend opening a new position. The three price tiers are conditional plans for after the fundamentals are delivered, not price triggers or orders to place now and then stop researching.
Observation zone: $0.28–$0.32, allocating 20% of the expected total investment in this token. First, require four consecutive weeks of verifiable repeat purchases by real paying applications, fee attribution, and funding for market purchases and burns; also verify security updates and supply changes. Then check order-book depth and execute using split limit orders. If any condition is missing, continue to observe.
Core zone: $0.18–$0.22, adding 50% to reach 70% cumulatively. In addition to maintaining the observation-zone conditions, revenue and capture execution should be stable for at least two months, with no admin action, economic parameter change, or unlock change that alters the assessment. Enter the core allocation only if a fresh valuation still shows a margin of safety.
Panic zone: $0.08–$0.12, adding 30% to reach 100% cumulatively. At this tier, confirm that the decline is mainly due to market or liquidity risk, not a failure of demand, value capture, supply, or security fundamentals. Cancel the remaining tiers if fundamentals fail. Keep any untriggered tiers uninvested; these three ranges are not a commitment to buy the full amount.
Existing holders should first check whether they can withstand a permanent loss. Positions that exceed their loss tolerance should be reduced gradually using limit orders to lower risk. Do not mechanically average down just because the price has fallen below your cost basis, and do not use leverage to wait for a rebound. If evidence of a major failure emerges, prioritize managing risk rather than waiting for the price to return to your entry point.
A single snapshot of the accessible spot order book showed a spread of about 0.2%, with only about $10,000–$20,000 of executable volume within 1% of the price on one side. This is a momentary snapshot from one venue, not a picture of all markets. Daily volume of more than $40,000 does not mean you can exit the same amount all at once. Before executing, recheck both sides of the book, slippage for the planned order, and the ability to trade continuously.
What would change my assessment
An upgrade in rating would require evidence that independent applications continue paying after incentives decline; paid reads and repeat purchases are growing steadily and verifiably; fee attribution, market purchases, delegated rewards, and permanent burns can be reconciled transaction by transaction; the new audit covers the actual deployment; permission changes can be detected promptly; and supply releases can be distinguished from actual sales. If these conditions are met, the fee trajectory, capture rate, risk discount, and scenario probabilities should be reassessed rather than simply carrying forward the old price.
The strongest opposing view is that personal AI context becomes a high-frequency foundational need, open standards lead to large-scale adoption, and actual fees far exceed the base case. Another opposing view is that supply holders do not sell for a long time, keeping the short-term price above the full-supply model for an extended period. Both could happen, but they require different evidence: the first improves economic value, while the second mainly improves trading supply and demand. They should not be conflated.
Signals for a downgrade or exit include stagnating payments and repeat purchases, growth that depends on rewards, changes to allocation that harm holders, buyback funds that cannot be reconciled, or incidents involving contracts, connectors, keys, privacy, or cross-chain operations. There is no reliable historical sample to support objective probabilities for these risks, so a neat percentage should not be used to downplay the possibility of permanent loss.
Next, check the paid activity and paying applications for a complete week, then examine the next buyback and burn. Before October 16, verify release addresses and exchange inflows, and update the rolling 30-, 90-, 180-, and 365-day windows. The migration deadline for the old staking pool is midnight UTC on October 31, which is 08:00 on November 1 Beijing time; holders should check the terms of their own pool. The larger unlock on January 16, 2027, is a scheduled monitoring date. No release date has been confirmed for the new audit or the complete governance portal.
These follow-up checks will determine whether Vana has built a sustainable fee-generating network or remains primarily driven by incentives and expectations. My current choice is to wait: remain interested in the project's utility while requiring a sufficient margin of safety between the token price and actual economic benefits.