CryptoSlate lays out a step-by-step framework for analyzing cryptocurrency
CryptoSlate publishes full framework for analyzing a cryptocurrency
CryptoSlate has published an intermediate-level guide that explains how to analyze a cryptocurrency before making a decision. Written by Andrej Gjorgievski and updated on September 16, 2026, the guide describes analysis as a process for testing claims rather than a way to guarantee returns.
The guide says no single score can replace a chain of reasoning. That chain links what a network or application does, how usage could create demand for its token, how supply is controlled, what activity can actually be observed, how secure and liquid the asset is, and what evidence would disprove the whole thesis.
Key takeaways
- Cryptocurrency analysis combines project research, token economics, technical design, governance, on-chain evidence, market structure, valuation and risk.
- A written process separates verifiable facts from assumptions, forecasts and promotional claims.
- Public data can be incomplete, token incentives can distort activity, and a successful project may not create value for its token.
Start with a specific research question
The guide advises defining exactly what is being analyzed: whether it is a native network coin or an application token, what role the token plays, its official contract address and chain, and its current circulating and total supply. Tokens sharing the same ticker can exist on different chains or have no relationship to each other.
It also says to write the question, time horizon and decision before collecting evidence. The guide gives an example: instead of asking whether a token is good, ask whether network usage creates recurring token demand that can outpace scheduled supply over the next two years. A short-term liquidity question needs different data than a multi-year adoption thesis.
Trace the path from usage to token value
The guide recommends describing the product without price language, then tracing the token's role through a value path: user activity leads to protocol action, which creates required token demand or fees, which leads to distribution or burning, which may produce holder value. Every step in that chain needs evidence.
It warns that a network can attract users while fees are paid in another asset, that a governance token can carry voting rights without a claim on cash flow, and that a protocol can earn revenue while rewards dilute holders by more than the revenue retained. Project success and token value are separate questions.
Check supply, distribution and dilution
Readers are told to record circulating, total and maximum supply and to explain why they differ. Items to check include issuance schedules, burns, vesting and release dates, allocations to team, investors, treasury and community, staking rewards, bridge accounting, holder concentration, and who has the authority to mint or change supply.
The guide suggests dilution scenarios rather than forecasts. If supply grows by 20 percent, it notes, demand measured in value must grow roughly 20 percent for the same price to hold. It frames the question of what adoption would produce that result as a sensitivity test.
Identify who actually controls the project
The guide says a project may describe itself as decentralized while a small multisignature wallet, which requires several approvals to act, can upgrade contracts, pause transfers, change fees or move treasury funds. Things to review include named contributors, legal entities, administrator and upgrade keys, multisignature signers and thresholds, governance voting rules, treasury reports and incident history.
It cites Ethereum's documentation on smart-contract upgrades to show how access controls, multisignature approval and timelocks, which delay changes to give notice, alter trust assumptions. A timelock provides notice but cannot make a harmful change impossible. It also cites Ethereum's public roadmap, which describes future plans as changeable, and says shipped code is evidence, a dated plan is an intention, and a marketing statement is a claim.
Review technology and security evidence
This part of the guide covers system design rather than price charts. It lists questions about the consensus or settlement system, which assumptions could cause loss or halt the network, whether contracts are upgradeable, which external oracles or bridges are required, whether audits are public, scoped and recent, whether findings were fixed, and how earlier incidents were handled.
An audit, the guide says, is evidence about a defined code version and scope, not insurance, and does not cover later changes unless the report says so. It also cites an Investor.gov bulletin warning that a proof-of-reserves report, which shows an exchange holds the assets it claims, does not replace a financial-statement audit under the standards that apply to registered public accounting firms. Repository activity needs context too: many code changes can reflect automation, while few can be normal for stable code.
What the guide confirms
The guide is explicit that analysis cannot guarantee returns. It frames the work as a way to test claims, and it lists known limitations: public data can be incomplete, token incentives can distort activity, and a widely used application does not automatically create value for its token.
Its table of contents shows the guide continues into measuring usage and on-chain activity, assessing volume, liquidity and market access, evaluating valuation claims, writing an evidence memo, defining failure conditions for a thesis, and common analysis errors. The published text provided for this article ends partway through the security section, so those later sections are indicated by the guide's own outline but are not detailed here.
Why a written process matters
The guide's central practical argument is that writing down the question, the evidence and the failure conditions reduces the temptation to keep searching until one source supports a preferred answer. It separates what can be verified from what is assumed, forecast or promotional.
What happens next
The guide presents the framework as a repeatable process rather than a one-time verdict. Readers are told to record the evidence that would disprove their thesis and to treat scheduled supply changes, governance controls and audit scopes as things to re-check over time. It does not set out a further publication timeline.