DeFiSafety
- Name: DeFiSafety
- URL: https://www.defisafety.com/
- Category: DeFi process-quality ratings / transparency watchdog / public trust-intelligence infrastructure
- Summary: DeFiSafety is a public checklist-and-score shop for protocol process quality. The point is not that it audits code. The point is that it defines a visible standard for what competent disclosure, testing, admin transparency, and oracle hygiene are supposed to look like.
- What it does:
- Publishes Process Quality Reviews and protocol scores based on public documentation, repositories, contract-address disclosure, testing evidence, audits, access controls, and oracle documentation
- Uses a weighted scoring framework with sections such as code and team, documentation, testing, code security, access controls, and oracles
- Starts from public materials, then gives teams a chance to respond, correct, or improve the report before later versions are published
- Offers pre-audit reviews and tailored research products alongside the public ratings business
- Aggregates protocol-review coverage across multiple chains into a searchable public ratings surface
- Key claims:
- The homepage frames DeFiSafety as a source of quality ratings and certifications across many protocols and chains, which is a public trust-language play more than a narrow consulting pitch
- The 0.9 Process Documentation says Process Quality Reviews are quantitative tests on deployed smart contracts and documentation that yield a simple quality score for development process and associated materials
- The methodology makes the theory of safety explicit by weighting documentation quality, testing evidence, access-control visibility, code security, and oracle transparency rather than only audit badges
- The review process penalizes weak public visibility, including private repositories and poor contract-address disclosure, which shows that verifiability itself is part of the product
- The avionic-software analogy in the methodology is the tell: DeFiSafety is selling process discipline as a usable proxy for software trustworthiness
- Whitepaper: No canonical whitepaper or litepaper surfaced in this pass. The strongest primary materials were the official homepage and the public 0.9 Process Documentation; see
../whitepapers/defisafety-primary-sources-2026-05-07.md. - Sources:
Internal linkages
- Strongest public-risk peers: onchain-risk-map and metrika.
Governance / control risk
-
Practical soft power sits in how the checklist is defined, which evidence gets weighted most heavily, how missing disclosure is penalized, and which protocols receive the most visible review coverage.
-
This is not a neutral scoreboard. The framework itself helps decide what
safe enoughmeans in public. -
Last reviewed: 2026-05-27 UTC