Crypto Trust Score

The Crypto Trust Score is a stage-aware Vartovii indicator for Web3 project review. It summarizes available market, development, security, financial, tokenomics, treasury, and community evidence into a 0-100 score.

The score is a decision-support signal. It is not a guarantee, investment recommendation, legal conclusion, or smart contract audit.

Formula

The current crypto score uses six weighted pillars:

Trust Score =
  Treasury (20%)
  + Dev Activity (20%)
  + Security (20%)
  + Financials (15%)
  + Tokenomics (15%)
  + Community (10%)

The same pillar model is shown in the crypto workspace radar and in downstream assistant/report handoffs when evidence is available.

Risk Bands

Score range	Risk language	Meaning
80-100	Low	Stronger evidence profile based on the currently available data.
60-79	Medium	Usable signal with some gaps or mixed evidence.
40-59	High	Elevated risk, thin coverage, or meaningful negative signals.
0-39	Critical	Significant red flags, very weak evidence, or severe source warnings.

Risk bands should be read together with evidence coverage. A high score with thin evidence and a medium score with broad evidence are different review situations.

Stage-Aware Coverage

Crypto projects do not all have the same evidence shape. Vartovii separates stage from quality so the score does not treat every missing market field as a negative signal.

Stage	What changes
Live token	Price, market cap, FDV, unlocks, holder context, and market chart can affect review.
Tokenless	The model emphasizes project identity, funding, development, security posture, and public traction.
Pre-launch	Missing token-market data is expected; readiness and evidence provenance matter more.

The API and UI include coverage metadata so users can see whether a project is fully supported, partially supported, or thinly covered.

Example metadata:

{
  "data_completeness": {
    "available_pillars": 4,
    "total_pillars": 6,
    "coverage_pct": 66.7,
    "is_insufficient": false,
    "missing_pillars": ["security", "community"]
  }
}

Pillars

Treasury

Treasury evaluates protocol or ecosystem financial depth where relevant. For DeFi protocols this can include TVL and market-to-TVL context. For L1/L2 networks, the model can use chain-level TVL instead of forcing a protocol-TVl interpretation.

Developer Activity

Developer activity uses public repository evidence when available. It can show commit volume, active-developer estimates, organization activity, or a truthful repo-push fallback when commit-level reads are degraded or rate-limited.

If GitHub evidence is missing or inaccessible, the workspace should label the gap instead of inventing developer activity.

Security

Security uses attached public evidence such as Dropstab security metadata, official audit links, public audit provenance, and severe warning flags when available.

An attached audit source is a signal that security evidence exists in the current Vartovii payload. It is not a statement that Vartovii performed the audit, verified every finding, or guarantees contract safety.

If no audit coverage is linked, the product should say that no current audit coverage is attached to the asset in Vartovii data. That wording is intentional: it avoids claiming the project has never been audited.

Financials

Financials review market structure and liquidity-related indicators such as market cap, FDV, liquidity ratios, and market availability. For live-token projects, these signals help explain dilution and market depth. For tokenless or pre-launch projects, they may be unavailable by design.

Tokenomics

Tokenomics reviews unlock status, vesting schedule visibility, investor quality, allocation transparency, and dilution context. When allocation or unlock details are not published, Vartovii shows the gap instead of assuming a schedule.

Community

Community reviews public traction and social visibility where supported by current sources. Social dominance can be extremely small; the UI may show <0.01% for weak-but-present signals so they are not hidden as zero.

Trust Graph Context

The Trust Graph is an additive read model that sits beside the score. It shows related entities such as investors, funding organizations, and source-family coverage when those relationships are present in project evidence.

Trust Graph edges are directional review signals, not legal ownership proof, endorsement proof, or definitive relationship claims.

Readiness Report Relationship

The assistant security readiness workflow can turn a project brief into a dedicated readiness route:

/app/crypto/:slug/readiness

The readiness route uses the same score, coverage, security provenance, and missing-evidence language to prepare a reviewer-ready handoff. It is scoped as a pre-audit readiness preview, not a formal smart contract audit.

API Reference

Project reads are available through:

GET /api/crypto/project/{slug}

Representative response shape:

{
  "project": {
    "slug": "layerzero",
    "name": "LayerZero",
    "symbol": "ZRO",
    "trust_score": 43,
    "risk_level": "HIGH",
    "stage": "live_token",
    "score_breakdown": {
      "treasury": 42,
      "dev_activity": 60,
      "security": 50,
      "financials": 36,
      "tokenomics": 48,
      "community": 44
    },
    "data_completeness": {
      "available_pillars": 5,
      "total_pillars": 6,
      "coverage_pct": 83.3
    }
  }
}

Exact fields can vary by project stage and source coverage.

How To Read The Score

Use the score as the start of the review, not the end:

1. Confirm the project stage and selected slug.
2. Review the Trust Score and risk band.
3. Check coverage metadata and missing pillars.
4. Inspect security provenance and audit-source availability.
5. Review Trust Graph context for related entities and source families.
6. Open the readiness route when the next step is a structured pre-audit or partner-review handoff.

Vartovii crypto intelligence is based on available data. It is not legal, investment, tax, employment, or security-audit advice.