What we measure — and what we refuse to
This site rates crypto services through one lens: Open-data scorecard. The question behind every score is “What do public, checkable sources say about how much this is trusted, how proven it is, and whether it stays up?” Not how many features it has, not how big it is. The failure mode we care about is the one that costs you money: Looks polished, but thin on the things you can actually verify — little value locked, unaudited, brand-new, or invisible when it breaks.
Last collection 2026-08-25: probed 252 services, measured 233, over a 90-day window.
The criteria we publish
Weights sum to 100%. When a criterion is n/a for a given service, its weight is redistributed proportionally across the ones we could measure — so a score is always out of what we actually looked at, and the card tells you how much of the total that was.
Scale of value trusted
Total value locked (DeFi), on-chain reserves (exchanges) or circulating market cap (stablecoins), from DefiLlama. Capital is the market voting with its money: a protocol holding billions has been trusted and stress-tested in a way a $2M one has not. Scored on a log scale — the gap from $10M to $100M means more than $10B to $20B. n/a where the service holds no measurable on-chain value (most wallets, tools, cards).
Security audits
Number of published security audits with links, from DefiLlama's audit field. Not a guarantee — audited protocols still get exploited — but an unaudited contract holding funds is a red flag, and audit links let you read the findings yourself. n/a for services with no smart-contract surface to audit.
Track record
Time the service has been live and continuously operating, from DefiLlama's listing date or the documented launch. Survival is signal: most failures happen young, so a protocol that has run through a full market cycle has cleared a bar a three-month-old one has not.
Multi-chain reach
Number of chains the service is deployed on, from DefiLlama. Breadth is resilience and adoption — but only a minor factor, since a focused single-chain protocol can be excellent. Never the main event, only a tie-breaker.
Latency
Median time to first byte from a public endpoint, our own probe, slowest sample discarded, single location. Scored within a category against peers timed the same way, never across categories.
Status transparency
Whether a public, machine-readable status page exists (statuspage / incident.io / instatus). A service you can audit from outside beats one you cannot — even if the opaque one happens to be reliable.
Incident repair time
Median minutes from published report to published resolution across the incidents a service logged, from its own status feed. n/a where no incident feed is published.
Peg stability
Absolute deviation of the live price from the intended peg, from DefiLlama's stablecoins feed. Stablecoins only: a coin trading at 0.94 is failing at its one job. n/a for everything else.
The weights move by category
One set of weights across eighteen categories would be a single method wearing eighteen hats. A DEX lives or dies on liquidity, so value locked leads there. A bridge is the biggest exploit target in crypto, so audits edge out even the value it carries. A hardware wallet has no on-chain value at all — age is the trust signal. A stablecoin is judged first on market cap and then on whether it actually holds its peg. Arrows show the move against the site default.
| Category | SCALE | AUDIT | TRACK | REACH | PERF | STATUS | INCID | PEG | Why |
|---|---|---|---|---|---|---|---|---|---|
| Crypto exchanges | 28%↑ | 0%↓ | 20%↑ | 0%↓ | 16%↑ | 18%↑ | 18%↑ | 0% | Centralized venues: how much they demonstrably hold, how long they have run, and whether they are transparent and stay up. |
| Decentralized exchanges | 30%↑ | 25%↑ | 18% | 12% | 8%↓ | 7%↓ | 0%↓ | 0% | On-chain venues live or die on liquidity and code safety, so TVL and audits lead. |
| Perpetual DEXs | 30%↑ | 26%↑ | 18% | 10% | 8%↓ | 8%↓ | 0%↓ | 0% | Perp venues need deep liquidity backing the book and audited engines. |
| Instant exchangers | 0%↓ | 0%↓ | 34%↑ | 0%↓ | 24%↑ | 22%↑ | 20%↑ | 0% | No on-chain value to weigh, so this rests on track record and whether the service is reliable and transparent. |
| Trading tools | 0%↓ | 0%↓ | 32%↑ | 0%↓ | 26%↑ | 22%↑ | 20%↑ | 0% | Tools hold no funds on chain — judged on longevity and service uptime. |
| Hardware wallets | 0%↓ | 0%↓ | 40%↑ | 0%↓ | 20%↑ | 22%↑ | 18%↑ | 0% | A device in a drawer has no TVL and no uptime; age is the trust signal, plus the reliability of its companion service. |
| Crypto wallets | 0%↓ | 0%↓ | 30%↑ | 0%↓ | 26%↑ | 22%↑ | 22%↑ | 0% | Clients over someone's backend: judged on longevity and how the backend behaves. |
| Staking platforms | 30%↑ | 18%↓ | 22%↑ | 0%↓ | 14%↑ | 16%↑ | 0%↓ | 0% | Value staked and audits matter, alongside the uptime that protects rewards. |
| Liquid staking | 32%↑ | 26%↑ | 22%↑ | 10% | 0%↓ | 10% | 0%↓ | 0% | LSTs are TVL-and-audit instruments: the peg rests on the value locked and the code holding it. |
| Liquid restaking | 28%↑ | 30%↑ | 22%↑ | 12% | 0%↓ | 8%↓ | 0%↓ | 0% | Newer and riskier than LSTs — audits and how long it has survived carry extra weight. |
| Yield aggregators | 28%↑ | 30%↑ | 22%↑ | 10% | 0%↓ | 10% | 0%↓ | 0% | Vaults route other people's money through many protocols; audits and value locked lead. |
| Lending platforms | 30%↑ | 28%↑ | 20%↑ | 12% | 0%↓ | 10% | 0%↓ | 0% | Oracle and liquidator risk make audits nearly as decisive as the value locked. |
| DeFi protocols | 34%↑ | 24%↑ | 22%↑ | 12% | 0%↓ | 8%↓ | 0%↓ | 0% | Blue-chip DeFi: the scale of value trusted is the headline, with audits and longevity behind it. |
| Crypto bridges | 28%↑ | 32%↑ | 20%↑ | 12% | 0%↓ | 8%↓ | 0%↓ | 0% | Bridges are the single biggest exploit target in crypto, so audits edge out even the value they carry. |
| Stablecoins | 34%↑ | 0%↓ | 22%↑ | 12% | 0%↓ | 10% | 0%↓ | 22%↑ | Market cap is the trust vote; live peg deviation is the one job; backing longevity and reach follow. |
| NFT marketplaces | 0%↓ | 0%↓ | 34%↑ | 0%↓ | 24%↑ | 22%↑ | 20%↑ | 0% | No on-chain TVL to weigh — track record and operational reliability carry it. |
| NFT & AI tools | 0%↓ | 0%↓ | 34%↑ | 0%↓ | 26%↑ | 22%↑ | 18%↑ | 0% | Young, fast-moving tools — longevity and service uptime are what we can check. |
| Crypto cards | 0%↓ | 0%↓ | 34%↑ | 0%↓ | 22%↑ | 22%↑ | 22%↑ | 0% | Payment services: track record plus the uptime of the authorization path. |
What we don’t publish
We only score what a public source can back. Two things a rankings page usually leads with, we leave out — because we cannot get them honestly from open data. We would rather show you the hole than fill it with something plausible.
Fees and real cost
Not published: honest all-in cost (fees + spread + slippage) needs a live seat and repeated real trades on every venue. We have not done that, so we do not score it rather than copy a headline fee that hides the spread.
UX and support
Not published: product feel and support quality are subjective and cannot be read from open data without opening accounts everywhere. Left out rather than faked.
Where this method is weak
- TVL rewards size, not safety. Value locked is the market voting with its money, and it is the best open proxy we have for adoption — but big protocols get exploited too, and a new one can be excellent. We score it on a log scale so it dominates less than raw dollars would, and never let it stand alone.
- An audit is not a clean bill of health. We count published audits with links, not their quality. Audited protocols still get drained. The score rewards having been looked at and letting you read the findings — not a guarantee the code is safe.
- Age is a floor, not the truth. For on-chain protocols we use the DefiLlama listing date, which can be later than the real launch, so it understates age for some old names. For off-chain services we use documented founding years. Either way it is a lower bound.
- Latency is measured from one place. One location, a handful of samples, slowest discarded. Real, and our own, but not global — a service can be quick for us and slow for you. Scored only within a category, against peers timed the same way; where the surface differs it drops to context.
- A missing status page is scored, not excused. If a service publishes no status feed we score STATUS low. That is a judgment: a service you cannot audit from outside is worse than one you can, even if it happens to be reliable. A page we simply failed to find would read as “publishes nothing”, so a blocked or unreadable one scores n/a instead of a mark against them.
- Redistributing n/a rewards opacity, so we cap it. Spreading an unmeasured criterion’s weight across the rest is the fair rule, but it has a sharp edge: points are docked on the criteria that need the most data, so the less we know about a service the less there is to hold against it. Left alone that floats the least-measured service to the top. A place in a ranking therefore needs at least a quarter of the category’s weight measured; below that a service is listed, with its numbers, outside the order.
- A missing status page may be our blind spot. We read three status platforms. A service on a fourth, or one whose bot filter turns our probe away, is not marked down for it — that case scores n/a and says so. But a page we simply failed to find at the conventional host would read here as “publishes nothing”, and that would be our error wearing their name.
- Coverage is thin and every card admits it. The heaviest criterion is n/a everywhere, so no verdict here rests on more than about two thirds of its category’s weight, and many rest on a third. The percentage next to each score is the honest size of the claim.
The scale
| 9–10 | Best in class, and we can show it |
| 7–8 | Matches best practice |
| 5–6 | Acceptable, with a shortcoming we measured |
| 3–4 | Worse than average |
| 1–2 | Red flag |
| 0 | Doesn’t do it at all |
| n/a | We didn’t measure it — weight redistributed, not counted as zero |
Absolute disqualifiers
A service is excluded from every rating, whatever else it scores:
- user funds never returned after an incident;
- a confirmed pattern of obstructing withdrawals (not a single complaint);
- a custodial service with neither proof-of-reserves nor a licence;
- volume falsification, by independent metrics;
- an anonymous team running a custodial model.
Exclusions are published on the category page — who, and why. Any service owned by or affiliated with this site’s owner does not appear in the ratings at all: not scored, not listed, not compared.
Check it yourself
Every number on this site is collected by scripts/collect-health.ts, carries the timestamp it was taken at, and links to the source it came from. Nothing here is typed in by hand, which is exactly why nothing here can be quietly adjusted to suit anyone. If a figure looks wrong, open its evidence link — it goes to the provider’s own page, not to ours.