v1.0 · May 2026

PrivaScan Whitepaper

Deterministic Risk Intelligence for EVM Privacy Protocols

Abstract

Privacy protocols on EVM blockchains serve a legitimate and growing purpose: they give users the same financial confidentiality that traditional bank accounts provide by default. But the protocols themselves carry technical and regulatory risks that are harder to evaluate than standard DeFi contracts. Their whole design obscures information — including, sometimes, their own vulnerabilities.

PrivaScan is an open-source risk scoring system that evaluates EVM privacy protocol contracts across six measurable dimensions — code quality, ownership structure, liquidity depth, audit coverage, regulatory compliance, and governance maturity — and computes a single deterministic composite score from 0 to 100.

The score is not a recommendation. It is a structured, reproducible data point that gives users, researchers, and builders a consistent basis for their own risk assessment. Every number is derived from on-chain data, public audit records, and automated static analysis. No black boxes. No opinions.

The Problem

When you use a privacy protocol to shield a transaction, you are trusting a set of smart contracts with more than your funds. You are trusting them with your privacy. If those contracts are exploited, you may lose both.

The challenge is that evaluating privacy protocol risk requires skills and data across multiple disciplines simultaneously:

  • Static analysis — reading the bytecode for vulnerabilities. Requires Slither, custom detectors, and understanding of ZK circuit patterns.
  • Ownership analysis — determining who controls the protocol, whether timelocks exist, and whether upgrades can happen without warning.
  • Liquidity context — understanding TVL as a proxy for protocol maturity and the financial exposure of users inside it.
  • Audit provenance — knowing which firm audited it, when, whether findings were remediated, and how the auditor’s track record holds up.
  • Regulatory screening — checking contracts against OFAC’s Specially Designated Nationals list and known exploit registries.

No single tool covers all five. Most users do none of them. PrivaScan covers all of them and surfaces the result as a single actionable grade.

Our Approach

PrivaScan treats a privacy protocol not as a single contract but as an ecosystem — every deployed contract (router, verifier, pool, vault, proxy) is scored individually, then aggregated into a single ecosystem-level grade.

This matters because risk in privacy protocols is often distributed. A clean core contract with a vulnerable peripheral contract is not a safe protocol. Our ecosystem model captures this.

The system has two tracks:

  • Curated track — 14 manually vetted protocols, automatically rescored every 6 hours via Celery beat. All contracts verified, all metadata confirmed.
  • Community track — any EVM address on any supported chain. First scan runs full Slither analysis (30–60s), then cached for 1 hour.

Scoring Methodology

The composite score is a weighted sum of six sub-scores:

composite =
0.30 × code_risk
0.25 × ownership
0.20 × liquidity
0.12 × audit
0.08 × compliance
0.05 × governance

Each sub-score is independently bounded to [0, 100]. The composite is also bounded to [0, 100]. Hard overrides can cap the composite below the calculated value — see the Hard Overrides section.

Weights reflect the relative importance of each dimension for privacy protocol risk, based on post-mortem analysis of historical privacy protocol incidents. Code risk carries the highest weight because smart contract vulnerabilities are the proximate cause of most protocol failures.

The Six Dimensions

Code Risk — 30%

Slither static analysis runs on the verified bytecode of each contract. We use the standard Slither detector suite plus 5 custom detectors written specifically for privacy protocol patterns. The code risk score starts at 100 and is reduced by finding severity: each high-severity finding reduces the score by 25 points, medium by 10, and low by 3. Unverified contracts receive a base score of 70 (a significant penalty) since we cannot analyse their bytecode. The minimum code risk score is 0. Custom detectors target: mixer reentrancy, ZK verifier bypass patterns, upgrades without timelocks, unlocked privacy pool withdrawal functions, and proxy storage collision vulnerabilities.

Ownership — 25%

Ownership analysis starts at 100 and deducts points for centralisation risk. Deductions: no multisig wallet controlling admin functions (−30), no timelock on protocol changes (−20), contract upgradeable without a timelock (−25), single EOA admin key (−15), proxy implementation pattern risk (−10). Bonuses are applied for renounced ownership where the contract is permanently immutable. The final ownership score reflects how much trust the protocol places in a single point of failure.

Liquidity — 20%

TVL (Total Value Locked) is used as a proxy for protocol maturity, user trust, and real-world financial exposure. Data is sourced primarily from DefiLlama (high confidence) with Dune Analytics SIM as a fallback (medium confidence). When both sources have data, a confidence-weighted blend is used. TVL tiers: Whale (>$100M) → 20 pts, Large (>$10M) → 40 pts, Medium (>$1M) → 60 pts, Small (>$100K) → 80 pts, Micro (<$100K) → 95 pts. The score represents liquidity risk — lower TVL = higher risk score.

Audit History — 12%

Audit coverage and quality are assessed across eight major smart contract audit firms, tiered by track record and rigour. Tier 1 (Trail of Bits, OpenZeppelin, ConsenSys Diligence, Halborn) → base score 15. Tier 2 (Quantstamp, PeckShield, CertiK) → 30. Tier 3 (others) → 50. No audit → 80. Formal verification adds a −10 bonus. Each unresolved critical finding adds 10 points, each high adds 5. Recency decay applies — audits older than 24 months are weighted down by 50%.

Compliance — 8%

Two compliance checks run on every score request. First: OFAC SDN (Specially Designated Nationals) screening against the US Treasury’s consolidated list, updated daily. Second: DeFiHackLabs exploit registry check for known attacks on the contract or protocol. An active OFAC match triggers a hard override: score capped at 10, grade forced to F. An unresolved exploit triggers a hard override: score capped at 30, grade forced to F. A resolved exploit carries a +20 point penalty without the cap. A clean record scores 0 (no penalty).

Governance — 5%

In v1.0, governance is fixed at 50 for all contracts — a neutral value pending the v1.1 implementation. Planned: Herfindahl-Hirschman Index (HHI) for token holder concentration, multisig quorum depth (what percentage of signers are needed), on-chain governance proposal history, and time-average participation rate. The 5% weight reflects that governance is a lagging indicator — poor governance becomes a code or ownership problem before it becomes measurable in token distributions.

Hard Overrides

Two conditions trigger hard overrides that cap the composite score regardless of what the six dimensions calculate. These are non-negotiable and cannot be offset by strong performance in other dimensions.

OFAC ACTIVE — Score capped at 10, grade F

Any contract matching an active entry in the OFAC Specially Designated Nationals list receives this override. The override is removed automatically when the OFAC entry is delisted. Example: Tornado Cash core contracts.

EXPLOIT ACTIVE — Score capped at 30, grade F

Any contract with an unresolved entry in the DeFiHackLabs exploit registry. Removed via the admin override API endpoint when the protocol provides documented remediation evidence (post-mortem, compensation plan, or redeployment).

Custom Privacy Detectors

Standard Slither detectors are not designed for privacy protocol patterns. We wrote five custom detectors that target the vulnerability classes most common in ZK-based and mixer-based protocols:

MixerReentrancy

Detects reentrancy vulnerabilities in withdrawal functions of mixer-pattern contracts, including cross-function reentrancy via shared state.

ZKVerifierBypass

Identifies patterns where ZK proof verification can be bypassed through calldata manipulation or missing input validation on the verifier contract.

UpgradeWithoutTimelock

Flags upgradeable proxy patterns (EIP-1967, UUPS, Transparent) where the upgrade function is not protected by a timelock of at least 24 hours.

UnlockedPrivacyWithdrawal

Detects withdrawal functions in privacy pools that lack nullifier checks, making double-spend attacks possible.

ProxyStorageCollision

Identifies storage layout conflicts between proxy contracts and their implementation contracts, a known vulnerability class in privacy protocol architectures.

Curated Protocol Registry

The curated registry contains 14 privacy protocols that have been manually vetted for inclusion. Criteria: verified source code on a block explorer, live mainnet deployment, documented architecture, and a public point of contact.

Curated protocols are rescored every 6 hours via an automated Celery beat schedule. All contracts in the ecosystem are scored individually and the results are aggregated using the same methodology as community scans.

To request addition to the curated registry, use the Add Protocol form. Submissions are reviewed within 72 hours.

PROTOCOLECOSYSTEMCONTRACTS
RailgunEthereum + L2s12
AztecEthereum12
Privacy PoolsEthereum5
HinkalMulti-chain29
Tornado CashMulti-chain41
0x0.aiMulti-chain8
iExecEthereum14
… 7 more

The API

All PrivaScan scores are accessible via a REST API. The API is free for community use at 500 requests per hour with a free key. It is designed to be embedded into wallets, DeFi frontends, research tools, and risk dashboards.

Full API documentation including endpoint specifications, request/response schemas, error codes, and code examples is available at:

View API Documentation →

The Telegram Bot

@PrivaScanBot brings risk scoring to Telegram. Users can score contracts, set up watchlists with alert thresholds, and receive real-time notifications when a protocol’s risk grade changes — without leaving Telegram.

Commands: /score · /watch · /unwatch · /mylist · /protocol

Open @PrivaScanBot ↗

Roadmap

v1.0
Live
  • 14 curated protocols
  • 6-dimension scoring
  • REST API
  • Telegram bot
  • Free API keys
  • OFAC + exploit overrides
v1.1
Q3 2026
  • Governance dimension (HHI, quorum)
  • Twitter OAuth for API key verification
  • Real-time trending feed
  • Score webhooks
  • Protocol comparison view
v1.2
Q4 2026
  • Pro tier (1,000 req/hr)
  • Score embed widget
  • Historical score database (full history)
  • Multi-chain ecosystem aggregation
  • Formal verification detection

Disclaimer

PrivaScan scores are informational tools produced by automated analysis. They are not financial advice, legal advice, or security certifications. A grade A score does not mean a contract is safe. A grade F score does not mean a contract will fail. Scores reflect the state of a contract at the time of analysis and may become stale.

PrivaScan is open source under the MIT licence. The codebase, detectors, and methodology are publicly reviewable at github.com/only1angelnath/Privascan.

Do not interact with any smart contract based solely on a PrivaScan score. Always conduct your own independent research.