Methodology
Every project is scored out of 10 on five pillars. The final rating is a weighted average, rounded to one decimal. Scores are revisited quarterly and after any material incident.
Technology
25%Does the code do what the documentation claims? We read the contracts, run the testnet and check whether upgrades are timelocked.
Team
20%Named contributors with verifiable history score higher than pseudonymous ones. Shipping cadence matters more than headcount.
Tokenomics
20%Supply schedule, unlock cliffs, real demand for the token, and whether growth is bought with emissions.
Community
15%Signal over volume. We look at governance turnout and developer activity, not follower counts.
Security
20%Audit recency relative to deployed code, bug bounty size, incident history and how honestly incidents were disclosed.
What we never do
- — Accept payment from a project in exchange for a review or a score.
- — Publish a score without disclosing what we could not verify.
- — Quietly edit a review; every change is logged with a date.