Crypto Token Security Signals

A plain-language risk lens for scam exposure, control risk, holder concentration, and liquidity resilience.

TL;DR

The Security Lens helps you quickly decide whether a token looks reasonably safe to research further or too risky to touch. It combines scanner findings, contract control signals, holder concentration, and liquidity quality into one deterministic score, then enforces hard-stop NO-GO rules for major red flags.

How to use it (Web UI)

The Security Lens workflow is simple: pick a token, run analysis, and review the score and flags top-down.

Open dApp →

1) Pick a token

Search or paste a contract address and select the chain/network.

2) Run the analysis

Generate a report. The lens gathers best-effort security and market-structure signals from multiple data providers.

3) Share or revisit

Each run produces a shareable analysis link so you can compare risk changes over time.

4) Read the report top-down

  • Summary: Plain-English risk view and confidence level.
  • Final Score: A 0-100 score plus risk label (low / medium / high / no-go).
  • Risk Flags: Concentration, admin-control, or suspicious scanner signals.
  • Liquidity Context: Lock coverage, depth quality, and maturity context.

What the Security Lens does (high level)

The lens turns raw security and market-structure data into a consistent due-diligence signal with transparent, deterministic rules.

1) Data ingestion (multi-source)

We collect best-effort security and market context from providers such as CoinGecko, DexTools, De.Fi, EVA, and Nansen.

2) Three-pillar deterministic scoring

Protocol Security (60%)
Scanner and trust-signal inputs for contract-level risk context.
Holder Power (25%)
Ownership concentration and dominance risk checks.
Liquidity Resilience (15%)
Liquidity depth, lock coverage, and lock-duration quality.

3) Hard-stop NO-GO gate

Some red flags are non-negotiable. The lens forces a no-go result if severe honeypot/scam behavior appears or dangerous early-stage unlocked liquidity risk is detected under strict conditions.

4) Maturity-aware liquidity logic

Unlocked liquidity is interpreted with project maturity context, distinguishing early unlocked liquidity (higher risk) from mature unlocked liquidity (still risky, but not always a hard stop).

5) Confidence and missing-data handling

If key inputs are missing, the report still returns a result but lowers confidence and clearly marks partial analysis to avoid fake precision.

Disclaimer

The Security Lens uses best-effort data retrieval and automated analysis. Data may be incomplete or delayed, and interpretations can be wrong. This is for educational purposes only and is not financial advice.