How to evaluate a crypto project long-term

Most crypto "analysis" is a mixture of price charts, enthusiasm and fear. A long-term evaluation asks different questions: does the technology work, does anyone really use it, who owns the supply, who controls the network, who is building it, what is its legal position, and who else is competing for the same job? Those are seven questions, and they are the seven categories of the scorecard.

Every coin page ends with a scorecard (chapter 13) and the comparison page shows all eight side by side. This page explains how to read both.

How the scorecard works

Each coin gets a whole-number score from 1 to 10 in each of seven categories. Every score comes with a short written rationale and at least one primary source, so a reader can check the reasoning rather than trust a number.

Four general rules keep the scores comparable across coins:

• Score what is verifiable today, not promises. Roadmaps can add at most +1, and only in Technology.
• Anchors define the scale. The tables below describe what earns a 2, 5, 8 or 10. A 7 for one coin must mean the same as a 7 for any other.
• Odd scores are allowed. A 3, 7 or 9 is used when a project sits between two anchors, and the rationale explains why.
• Hype and market cap do not move the score in any category except where a category says otherwise. Size is not quality.

1. Technology

What it covers: architecture soundness, finality, throughput under real load, fees, uptime history, developer tooling and security record.

Notice what is not here: a claim of "transactions per second" from a marketing page. Lab figures are not the same as measured behavior under load, which is why the rubric asks for throughput under real conditions. Finality matters because a payment you cannot rely on is not a payment; different consensus designs trade finality, openness and simplicity differently, as the basics page explains. The only forward-looking element is a roadmap bonus of at most one point.

2. Real adoption

What it covers: verified on-chain usage by real users or institutions - transactions, active addresses, stablecoins or tokenized assets issued, enterprises in production. Announcements and pilots do not count.

Why announcements do not count

An announcement costs a press release. A production deployment costs engineering, compliance review and ongoing operations, and it leaves evidence: transactions on a ledger, an audit, a regulator filing, or a customer who says so by name. A memorandum of understanding, a "collaboration", a pilot or a proof of concept can be real and still change nothing about who uses the network on a normal Tuesday.

For this reason each coin page separates adoption into three labelled blocks: verified usage with evidence, announced partnerships and pilots, and unverified narratives. A useful test is to ask four questions. Can I see the activity on a public ledger or in a filing? Is the user named and independent of the project? Is it live, or is it "planned", "exploring" or "testing"? Would the activity stop if this network disappeared? The ISO 20022 guide applies the same test to a famous narrative and shows how far "compatible", "announced" and "in production" can be from each other.

3. Tokenomics

What it covers: supply clarity, inflation, emission schedule, distribution fairness, large-holder concentration, lockups or escrow transparency, and token utility that drives demand.

Two things are easy to confuse here. A cap is not the same as fairness: a capped supply that is mostly held by insiders can score lower than an uncapped one with broad distribution. And utility is not the same as price: the question is whether the token is required for something the network needs, such as fees or securing the chain, not whether it is traded. The basics page explains max supply, total supply and circulating supply with a worked example; read it first if the terms are new, and check the supply chapter.

4. Decentralization

What it covers: who can produce blocks or validate; validator count and independence; client diversity; who controls upgrades; geographic and entity distribution; dependence on one company.

Decentralization is a spectrum, and it is measured on several axes at once: the number of validators, whether they are independent of each other, whether more than one software client exists, and who decides on upgrades. A council of large organizations, a fixed committee of masternodes, a trust-list design and an open staking network all sit in different places, and the rubric scores the practical outcome rather than the label. More decentralization is not automatically "better" for every purpose; it trades off against speed, simplicity and accountability. The score simply reports where a network stands.

5. Team and funding

What it covers: track record, transparency, treasury runway (public reporting), key-person risk, and delivery versus roadmap history.

A project that depends on one company or one charismatic founder has key-person risk: if that party leaves, runs out of money or loses interest, development stops. The strongest signal is not a famous name but a delivery record, meaning past roadmaps compared with what shipped, and public financial reporting that shows how long the money lasts. Multiple independent organizations building the same protocol, as in the 10 anchor, is rare.

6. Regulatory standing

What it covers: clarity of legal status in major jurisdictions (US, EU, UK), active litigation, licenses held by the main entity, MiCA readiness, and exchange listing breadth in regulated markets.

The EU's Markets in Crypto-Assets Regulation is a main reference point for the EU. ^[1] In the US, the question of whether an asset is a security has been argued through the SEC and the courts, using the Howey test; an SEC staff framework applied that test to digital assets, though the SEC has since withdrawn it and replaced it with a newer document dated 17 March 2026. ^[2][3] Regulatory scores change when facts change, such as a ruling or a new licence, which is why each page dates its legal chapter. This category describes legal clarity, not legal opinion, and it is not legal advice.

7. Competitive position

What it covers: how well the project competes with others solving the same problem, including non-crypto incumbents; defensibility; network effects; developer and liquidity share.

The inclusion of non-crypto incumbents is deliberate. A cross-border payment network does not only compete with other coins; it competes with banks, card networks and fintech apps, and many people never need a coin at all. A moat is something that is hard to copy: a liquidity pool, developer ecosystem, licences or an installed base. The rubric rewards a moat that exists today, not one that is planned.

How to read a coin page scorecard

Each coin page includes seven category scores with a rationale and links to sources. A sensible reading order is:

1. Read the rationale before the number. The 2-3 lines explain what moved the score.
2. Open at least one source for any category you care about. If it does not support the claim, trust the source.
3. Look at the date. The "last updated" date shows when the evidence was checked.
4. Compare categories within a coin. A project can score high in Technology and low in Decentralization, which is a profile, not a contradiction.
5. Compare across coins on the comparison page, where the same rubric applies.

Using /compare and the weight sliders

By default the scorecard shows the unweighted average: the seven scores added up and divided by seven, which treats every category as equally important. That is rarely how anyone actually thinks.

On the comparison page you can drag a slider for each category to say how much it matters to you. The weighted score is each category score multiplied by its weight, summed, and divided by the sum of weights. For instance, if Technology has weight 3 and every other category weight 1, then the divisor is 9, and Technology contributes one third of the result instead of one seventh.

If you are a developer, you might push Technology and Decentralization up. If you care mostly about legal clarity, you might push Regulatory and Team up. If you hold for the very long term, you might care most about Tokenomics and Competitive position. The sliders do not tell you what to value; they make your own priorities explicit. Use the reset button to return to equal weights.

The limits of scoring

Be sceptical of any single number, including ours.

• Scores compress. A whole project becomes seven integers. Nuance lives in the rationale, which is why it exists.
• Judgment is involved. Anchors reduce subjectivity but do not remove it. Reasonable people could score a project one point differently, and the odd-score rule exists for that reason.
• Evidence ages. A score reflects the facts at the time of writing and will become stale. Re-check the date and the sources.
• Equal intervals are an illusion. The step from 8 to 10 is much harder than the step from 2 to 5, and averaging whole numbers hides that.
• A high score is not a prediction. Scores measure quality of verifiable facts. They say nothing about price, and a well-scored project can fall while a poorly scored one rises. Markets are driven by many things the rubric deliberately ignores.
• Missing categories. Security audits, community culture, and your own tax or legal situation are not scored here.

This is why the right use of a scorecard is to structure your own research, not to replace it. Read the sources, form your view, and decide with your own risk tolerance, ideally after reading the basics page on volatility. Nothing on this site is investment advice.

Your own checklist

A short version you can apply to any project, on or off this site:

1. What does it do, in one sentence, and who needs that?
2. Can I verify real usage on a public ledger, from named independent users?
3. Who holds the supply, and on what schedule can it reach the market?
4. Who can change the rules or stop the network?
5. Who builds it, with what money, and what did they deliver last time?
6. What is its legal status where I live?
7. Who else does this job, and why would users stay?

Then open the full guides for XRP, XLM, ALGO, HBAR, ADA, IOTA, XDC and QNT, and use the comparison page to view them together.