How we master a score.

Every review starts with the contracts, not the deck. We read the code, replay the incidents, and run the protocol with our own capital before a score is assigned. Nothing on this site is sponsored, and we do not accept tokens from teams we cover.

A score is a single number, so we publish its parts. If a weighting changes, we re-score the affected catalogue and note it in the review.

Mechanism design

30%

Security & audit history

25%

Governance & token structure

20%

Liquidity & real usage

15%

Disclosure quality

10%