ProtoRadar documentation
Inspect the method behind every signal.
Start with what is measured, then follow the evidence to its source, scoring rule, operating boundary, and unresolved checks.
Start here
Each route answers a distinct research question. The screener surfaces candidates; the reference pages explain how to read them.
The research model
ProtoRadar separates project evidence, market activity, and evidence coverage. A volume event cannot automatically raise a project score, and missing critical evidence can withhold the result.
- Project evidence
- Transaction integrity, wallet quality, contract and market risk, product evidence, and social authenticity.
- Market activity
- Recent qualified volume, robust baseline deviation, effective traders, and measured volume relative to circulating market cap.
- Evidence coverage
- Source presence, freshness, and whether the evidence is direct enough to support the claim being made.
Glossary
These terms keep research states consistent across the screener, reports, watchlist, and alerts.
- ProtoScore
- How strongly the available evidence supports project quality and credibility. It is withheld when critical coverage is insufficient.
- Signal Strength
- How unusual and broadly distributed current market activity is relative to the token’s own measured baseline.
- Evidence Confidence
- How much required evidence is present, fresh, and sourced at the appropriate level. Coverage is not favorability.
- Unknown
- A required check that cannot be resolved from the evidence currently connected. Unknown never counts as a pass.
- Provisional
- An early research state that surfaced before every qualification condition was met.
- Canonical asset
- An asset identified by a valid contract-address match in the official Robinhood registry, not by name or ticker.
Operator notes
Use this checklist when sharing a token report, launch record, or market observation outside ProtoRadar.
- Confirm the evidence modeLive, fallback, and deterministic demo records have different provenance. Preserve the source label when sharing a finding.
- Verify addresses, not tickersNames and symbols can be copied. Use the network, canonical contract address, source transaction, and explorer record together.
- Treat degradation as uncertaintyA failed provider or incomplete registry lowers coverage. It does not prove a token is absent, safe, or suspicious.
- Keep the claim narrower than the evidenceDescribe the measured window and its limitations. Avoid safety, legitimacy, endorsement, or return language.
External operator references
Protocol and chain mechanics can change. Recheck the official source before acting on a launch configuration or contract call.