1. Identify the asset before analyzing it
BlockAssay prioritizes a verifiable technical identity: chain, token or mint address and available provenance. A name or ticker is not enough.
BlockAssay makes provenance, limits and inconsistencies visible instead of hiding uncertainty behind a single score.
Example: a revoked Solana mint authority returned by Solana RPC is OBSERVED. “The token is safe” is not a supported inference.
Provenance: every indexed fact must carry a source valid for its fact family and an HTTPS verification location.
Freshness: observedAt describes when the fact was collected; it is not replaced by request time.
Contradictions: conflicting exact-asset sources prevent a confident conclusion and remain UNKNOWN or INSUFFICIENT until resolved.
Limits: no score, page or source guarantees safety, profit, identity, ownership, or future behavior.
BlockAssay prioritizes a verifiable technical identity: chain, token or mint address and available provenance. A name or ticker is not enough.
Prices, volumes, liquidity and on-chain data may be observations. A score or conclusion appears only when it is actually produced by a validated method.
Incomplete or inconsistent data must reduce confidence and trigger an explicit verification or insufficient-information state.
A token account is not automatically one economic holder, and a technical authority does not prove civil identity.
Creators may pay for tools, never to improve a diagnostic, remove a warning or influence Radar.
Public payloads pass shape, value, semantic-consistency and secret-leak checks. On failure BlockAssay returns a neutral state rather than internal details.
No diagnostic guarantees that an asset will rise, a project is honest or a transaction is risk-free. BlockAssay helps reduce uncertainty; it never denies it.
UNKNOWN: no source answered. INSUFFICIENT: data exists, but it is not enough to conclude.
Because absence of evidence is not evidence of absence of risk.
No. Diagnoses are independent of plans and creation tools.