Building Your Foundation: How to Verify Digital Asset Project Claims
A project’s whitepaper reports growing usage, a functioning lending product and an attractive token economy. The numbers look coherent. Yet its published dashboard may count the same deposits twice, its fee statement may omit who receives the money, and its roadmap may describe features not deployed. An investor or institutional reviewer needs more than a plausible story. The first job is to establish what can be checked and what remains an assertion.
This article sets out an evidence-first preliminary screen. It is not a valuation model or a prediction of future returns. It converts project statements into a record of sources, observations, contradictions and follow-up decisions. Readers looking for a fuller assessment of a project’s competitive position should use Kenson’s long-term blockchain project viability analysis; this page addresses the verification work that must come before it.
What a credible research foundation must establish
A fundamental research file separates seven things that promotional material often blends together: the project’s stated purpose, the deployed product, observed use, protocol economics, tokenholder rights, supply and control, and the assumptions behind any investment thesis. A protocol can be genuinely useful while holders of its token have no contractual claim on fees or treasury assets. Conversely, a disclosed token entitlement does not show that the business generating those entitlements is sustainable.
For every important claim, preserve the source, date, exact wording and evidence needed to test it. An original whitepaper is appropriate evidence of what the project said, not proof that the promise came true. EU MiCA Article 6 whitepaper requirements, where applicable, specify disclosures about rights, risks and technology, while explicitly requiring a statement that competent authorities have not approved the whitepaper. That regime does not cover every instrument or jurisdiction, and compliant disclosure should not be mistaken for independent certification.
A seven-stage claim-verification workflow
1. Record the claim before judging it
Start a claims register with a specific, falsifiable statement: for example, ‘the lending market has $120 million deposited’ rather than ‘adoption is accelerating.’ Record the original URL or file, publication date, asset and network, reporting period, claimed units, and the type of evidence required. Label roadmap commitments separately from features described as operational. If the claim changes across presentations, keep both versions rather than quietly substituting the newest one.
Free educational tool
How healthy is your hypothetical portfolio?
Seven questions about how a hypothetical portfolio is structured, with three sub-scores and an overall Health Score out of 100.
Educational tool. Results are not investment advice.
The test also needs a defined scope. ‘One million users’ could mean registered accounts, unique addresses or monthly active people. Those are not equivalent populations. Ask the project to define the denominator before assessing the apparent scale.
2. Establish what has actually been deployed
Locate the official application, supported networks, deployments, upgrade information and relevant release history. For an Ethereum-based system, source-code verification guidance from ethereum.org explains how published code can be compared with deployed bytecode. A verified match supports code identification; it does not prove that the protocol is safe, that the relevant function is enabled or that the economic description is accurate. Review proxy implementation addresses and upgrade authority where relevant.
Compare claimed features with current user-facing behavior, contract states and the project’s published release history. Record which functionality can be observed and which would require specialist technical testing. An unpublished build, open-source repository or past security audit is not by itself evidence that a production system operates as advertised.
3. Test adoption with fit-for-purpose metrics
Select indicators that reflect the claimed product. A lending market may need deposits, outstanding borrowing, utilization, repayments and repeat borrowing activity; a payments network may require completed transfers and the cost and reliability of settlement. Treat raw transactions and addresses as imperfect indicators of distinct customers. Bots, airdrop campaigns, internal transfers and incentives can inflate activity without demonstrating durable demand.
Total value locked (TVL) is especially sensitive to definitions, asset prices, repeated positions and the contracts included in a count. The Bank for International Settlements’ May 2025 study examined how DeFi TVL was measured and identified inconsistent methodologies and verification gaps. Compare dashboards with disclosed contract and token lists, consistent valuations and independent calculations where feasible. A time series drawn from a changing methodology needs an explicit warning.
Do not substitute market trading volume for protocol use, or fees paid by users for net operating revenue. Kenson’s separate investment-performance metrics discussion addresses asset performance measures; this screen asks only whether the project’s underlying activity claims are evidenced.
4. Trace the link from protocol activity to tokenholder economics
Identify precisely what the token enables or entitles its holder to receive. Is it needed for network execution, required for a service, used to vote, eligible for a defined redemption, or given a contractual payment right? Look for governing contracts, terms and executed governance proposals rather than relying on statements such as ‘holders share in growth.’ Protocol fees can be paid to liquidity suppliers, service providers, a treasury or no tokenholders at all.
Document who may change fee routing, distributions and token privileges, and whether changes take effect immediately or through a formal process. For the underlying supply-and-demand mechanics, link to Kenson’s tokenomics analysis instead of reproducing the full model. Where the project describes a novel issuance or incentive design, its dedicated token-economy discussion provides the adjacent context.
5. Verify supply, team activity and control rights
Free educational tool
Test a hypothetical allocation against history
Choose assets and weights, set contributions and costs, and review historical outcomes, volatility and drawdowns. Historical data, not a forecast.
Educational tool. Results are not investment advice.
Reconcile circulating, unlocked, vested and maximum supply using the project’s stated definitions, contract observations and dated allocation schedules. Identify treasury or insider holdings and any known right to mint, freeze or modify supply parameters. A headline supply cap does not itself reveal near-term transferable supply. Verify which administrators control upgrades, emergency functions and treasury movements, especially where digital asset internal controls depend on independently approved permissions.
For development, look at relevant releases, maintenance history, issues and documentation, not simply the quantity of commits. GitHub’s contributor documentation describes what its graphs count and omit, so those metrics must be read with care. Contributor graphs can omit activity outside their reporting rules, including some non-default-branch commits. Open-source activity may demonstrate ongoing work; it does not establish staff identity, code quality, security or operational readiness. Check repository security advisories for disclosed issues and remediation, while recognizing that the absence of an advisory does not prove that no vulnerabilities exist.
6. Classify the strength of the evidence
Every high-impact claim needs a dated assessment. Use Verified when suitable direct evidence supports its precise scope; Partially corroborated when only some elements can be confirmed; Unsupported when available material cannot substantiate it; and Contradicted when reliable observations conflict with it. These are internal research labels, not standardized ratings or findings of wrongdoing. Keep an ‘unresolved’ field to distinguish unavailable records from negative evidence.
Assess source independence, recency, reproducibility and incentives. On-chain logs can confirm a transaction but may not reveal who controlled an address or whether activity represents independent customer demand. A security audit speaks to the reviewed system and scope, not all possible failures. The SEC staff’s investor bulletin on proof-of-reserves reports explains why those reports are not equivalent to audits of financial statements. Source quality matters more than the number of links in the file.
7. Record an outcome with explicit conditions
A preliminary reviewer should recommend Advance for deeper diligence, Hold for specified missing evidence, or Exclude under the institution’s screening policy. Link each outcome to claims and thresholds actually considered. Do not use a universal percentage score to offset an unverified ownership claim or a critical unresolved permission. The next review date, document owner and requested follow-ups should be recorded. Advancing a project is not permission to execute a trade; separate pre-trade eligibility and exposure controls govern that decision.

Worked screening file: a hypothetical DeFi lending project
Assume a fictional DeFi lending project that publishes a $120 million TVL figure and $2 million in monthly protocol fees. It also advertises active development, a favorable unlock schedule and a token that supposedly benefits from platform growth. No figures or events below describe an actual protocol.
| Published claim | Evidence reviewed | Assessment | Next question |
|---|---|---|---|
| $120M TVL | Dashboard; checked balances for listed contracts; incomplete coverage | Partially corroborated | Are assets double-counted or priced consistently? |
| $2M monthly fees | Fee-event records but no recipient breakdown | Partially corroborated | What reaches treasury, lenders or tokenholders? |
| Active development | Repository releases and contributor graph | Verified as public activity only | Do releases match production deployments? |
| Limited dilution | 25M unlock vs 100M circulating | Unsupported as stated | What makes the expected increase “limited” and when are tokens transferable? |
| Holders gain from growth | Governance language, no direct fee right | Unsupported as stated | What governing term creates a financial claim? |
An analyst would attempt to reproduce the TVL calculation instead of copying $120 million into a memo. In this hypothetical check, available on-chain balances support part of the figure, but the incomplete contract list prevents verification of the total. The deposit list might include positions recycled through another protocol, and a different price timestamp could change the dollar total. Fee records may show $2 million collected, but the reviewer must distinguish gross borrower charges, lender distributions, treasury receipts and expenses. Even verified monthly fee collections cannot establish tokenholder entitlement without applicable terms or implemented distribution rules.
The hypothetical unlocking of 25 million tokens against an initially circulating 100 million units represents a 25% addition relative to that starting circulating amount if all 25 million become transferable and no other supply changes occur. It does not mean token price falls 25%, nor establish when recipients may sell. The file should retain the underlying vesting contract, tranche schedule and definition of ‘circulating’ used at each date.
Suppose repository releases document ongoing maintenance but the rights document identifies governance voting only, with no direct holder payment. The defensible decision is Hold, pending a reproducible TVL method, fee-recipient reconciliation and a corrected tokenholder-benefit statement. Neither a positive product metric nor an unsupported claim alone justifies a price conclusion. This is a screening decision, not a finding of fraud.
Free educational tool
Are you ready for digital assets?
Seven quick questions on knowledge, mindset and goals, with one honest answer about where you stand.
Educational tool. Results are not investment advice.
How to avoid false confidence in the evidence
Three recurring mistakes deserve a final check. First, an impressive dashboard may display derivative or self-reported data whose coverage changes silently. Second, a technically true claim can invite a false inference: fees collected are not necessarily earnings retained, much less income payable to tokenholders. Third, a project’s disclosed risks do not disappear because its contracts were reviewed or its founders have strong credentials. Evidence and suitability remain separate questions.
Some early-stage products have limited operating history through no misconduct. Record the missing observation period and explain why it matters. In parallel, identify where third-party dependencies could distort evidence: price oracles, custodians, indexers and external reporting vendors. Kenson discusses this wider issue in third-party dependency risk. For assets that appear actively traded, liquidity metrics are another specialist topic; a quoted price does not establish an executable exit size.
A research dossier should be updated when material deployments, token unlocks, governance powers or data methodologies change. Maintain dated screenshots or exported records where lawful and appropriate, and preserve contradictory evidence rather than deleting it when narratives improve. This supports digital asset risk management without confusing research documentation with actual portfolio control.

Twelve questions before advancing a project
- What claims are central to the project, and which are statements about future plans?
- Which live deployment, contract and observed function support the claim that the product operates?
- Can the usage figures be reproduced, and what activity is excluded?
- How are addresses, transactions, TVL and recurring users defined?
- What produces the reported fees, and who actually receives them?
- Which rights, if any, attach to the specific token under review?
- Which circulating-supply definitions and unlock schedules are documented?
- Who controls minting, upgrades, emergency permissions and treasury funds?
- What do independent audits, advisories or incident records actually cover?
- Which data vendors or counterparties could compromise observed metrics?
- Which material claims remain unsupported or contradicted, and why?
- Is the evidence sufficient for further diligence under the reviewer’s policy?
A stronger foundation is a record, not a prediction
Fundamental research starts when a reviewer can tell verified facts from untested claims and explain what is still unknown. A concise claims register, documented evidence quality and explicit screening decision can prevent an attractive narrative from becoming an unsupported investment thesis. Kenson Investments’ educational research on digital assets and market infrastructure provides further context for this discipline. Any subsequent valuation, legal review or investment decision requires its own analysis. Get in touch with us today.
Disclaimer: The information provided on this page is for educational and informational purposes only and should not be construed as financial advice. Digital assets involve significant risk, including the possible loss of principal, and past performance is not indicative of future results. Always conduct thorough research and consult a qualified financial advisor before making investment decisions.
Digital asset regulation in the United States is still developing. Some areas, such as payment stablecoins, now have a federal framework, but comprehensive market-structure legislation has not yet been enacted. None of the information provided by Kenson LLC should be considered financial investment advice. Please consult your Registered Financial Advisor for guidance. Kenson LLC does not offer any products regulated by the SEC, including equities, registered securities, ETFs, stocks, bonds, or equivalents.









