Score methodology
The 0–100 score compares published projects with one formula. It describes a project's profile, not its code quality, security, or expected return. Formula version: 2.0.
How the score is composed
| Component | Calculation | Maximum |
|---|---|---|
| Project role | A core protocol or purpose-built blockchain earns 35, infrastructure 30, an application 26, a peripheral feature 12, and an out-of-scope project 0. The role follows the classification methodology. | 35 |
| Verified categories | Each Stack tag adds 3 points and each Technique tag adds 2. Unsupported claims do not count. | 25 |
| GitHub | Followers: 4 × log10(count + 1), capped at 12. Public repositories: 0.5 each, capped at 8. Without data, this component is zero. | 20 |
| Market | USD market cap: 2 × (log10(cap) − 6), clamped to 0–12. 24-hour volume / cap × 40, capped at 8. Both parts are zero without positive market cap. | 20 |
Worked example
A hypothetical infrastructure project has two Stack tags and one Technique tag, 99 GitHub followers, and 10 repositories. Its market cap is $100 million and 24-hour volume is $10 million.
| Component | Substitution | Points |
|---|---|---|
| Role | Infrastructure | 30 |
| Categories | 2 × 3 + 1 × 2 | 8 |
| GitHub | 4 × log10(100) + 10 × 0.5 | 13 |
| Market | 2 × (log10(100,000,000) − 6) + (10,000,000 / 100,000,000) × 40 | 8 |
| Total | 30 + 8 + 13 + 8 | 59 / 100 |
This is a calculation example, not a real coin's score. Coin pages display the result as a whole number.
Limits of the score
Only published projects with a CMC ID and classification are scored. Projects with a peripheral AI feature or no substantive AI role are capped at 45 when GitHub data is unavailable. A new score is not applied if the market snapshot fails completeness or freshness checks. Sources are described in the data catalog.