Evidence & limitations
Understand source review
Trace a supported check to its evidence and review record.
What review establishes
Review connects a source to a specific check. An oracle mapping needs the exact chain, token, feed relationship, units and parameters. A project profile needs its exact chain and contract plus the website section and account links the scanner will compare.
Review establishes the accepted method. Each observation still fetches the current sources. A saved review timestamp cannot replace a failed read.
Read automatic discovery sources
The explorer and market adapters query fixed providers using the exact Robinhood Chain address. These lookups do not need a reviewed token profile. Onchain responses, explorer records and market pairs remain separate source observations.
Blockscout’s indexed metadata and reported source verification do not establish code safety or project ownership. DEX Screener’s pairs and published links do not establish identity or endorsement. The scanner records discovered links as unreviewed and never follows them to collect identity claims.
A market record must match the configured chain and include the exact requested token address. A familiar name or symbol cannot substitute for that match. Read Token discovery for source gaps and timestamp limits.
Follow the evidence chain
Start with deployed contract evidence and the classification. For issuer Stock Tokens, follow the registry, mapping, adapter and price metadata. For project tokens, follow the exact published chain and contract claims and the links between reviewed accounts. Exposure evidence needs its own supported document relationship.
- Issuer identity: Robinhood token contracts and current Stock Token API evidence.
- Project identity: reviewed website and GitHub sources recorded in projects.json, fetched for the observation.
- Feed mechanics: Robinhood oracles and price feeds .
- Exposure context: Robinhood Stock Tokens and the linked issuer documents.
When evidence conflicts
Conflicting addresses, chains, account links, units or parameters remain visible in the relevant check. The service cannot choose whichever source produces a favorable label. Project identity needs both current reviewed sources to match; an unavailable source prevents a complete match.
Source details include retrieval times and content hashes when a response body was read. A hash identifies the retrieved content; it does not prove who published it or make the contents trustworthy.
Fetched source endpoints are reviewed configuration. Discovered website and social links are unreviewed output, and the scanner does not follow them. The public address input cannot supply an arbitrary URL for the server to fetch.
Read the version
Stock-token coverage, project identity coverage and policy each have their own version. A source or rule change can alter future checks. Older receipts retain the evidence and versions recorded when they were created.
See Changelog for changes and Receipts for historical observations.