FOLLOW THE REASONING
Every status has a reason.
PeelSignal reads any token contract on Robinhood Chain and looks for explorer and market evidence by its exact address. Identity and oracle checks use their own reviewed sources. No language model decides a status.
Read the contract
Check chain 4663 and deployed code. Read name, symbol, decimals and total supply at one recorded block; a missing field does not stop the other reads.
Find address-based evidence
Query the configured explorer and market index for the exact chain and address. Keep indexed facts, market pairs, source times and missing data separate from onchain reads.
Apply the relevant checks
Compare issuer and reviewed project identity sources, then apply supported oracle and exposure rules. Market listings and copied tickers cannot establish identity or award Fresh.
Keep the receipt
Store the result with its evidence and expiry. A recheck gets a new URL.
Every address gets the same discovery method.
A token does not need a reviewed profile to receive contract reads, an explorer lookup or a market lookup. Explorer facts can include indexed token metadata, holder count and reported source verification or proxy information. Market results can include exact-address pairs, prices, liquidity, volume and published links when the provider has them.
Explorer verification describes the explorer’s source-code record. Market data describes the provider’s indexed pools. Neither establishes code safety, project identity or an executable price. Discovered website and social links remain unreviewed; PeelSignal does not fetch them. A source failure and a successful lookup with no matching record have different outcomes.
Read the token discovery guideIdentity needs its own evidence.
A deployed contract with an exact issuer-registry match is classified as an issuer Stock Token. A deployed contract whose reviewed project website and GitHub profile both publish matching chain, address and account links is classified as a project token. Other contracts remain unclassified, with the evidence collected so far visible in the report. Conflicting registry entries or overlapping issuer and project matches also remain unclassified for review.
Project sources are fetched for the observation. A changed address, broken account link or unavailable source prevents a complete identity match. Website and GitHub claims controlled by the same project are related claims; they do not establish an independent endorsement. X links are compared in those sources, but the X profile itself is not queried.
Read the reviewed identity methodThe status vocabulary
The four panel labels are fixed. Canonical refers to the supported issuer Stock Token check. A project identity match appears separately; it does not supply backing, oracle integrity or personal eligibility. Open a check’s documentation for its evidence and rules.
| Check | Possible results | Read the rules |
|---|---|---|
| Contract provenance | Canonical · Unrecognized · Unknown | Details |
| Price integrity | Fresh · Stale · Paused · Sequencer unavailable · Unknown | Details |
| Exposure evidence | Documented · Unsupported · Unknown | Details |
| Eligibility | Not confirmed | Details |
Price rules and incomplete evidence
Paused or observed sequencer downtime takes precedence. Missing or conflicting required evidence stays Unknown. A complete, valid observation exceeding the reviewed age bound is Stale. Fresh requires all supported checks, including reviewed sequencer evidence. Current coverage has no reviewed sequencer adapter, so live checks do not award Fresh. A missing uptime source does not establish that the sequencer is down.
No session calendar adapter. Age bounds are conservative and do not assert issuer failure during market closure.
A receipt has a time limit.
Policy 2.2.0 uses a maximum lifetime of 300 seconds from the observation, capped by the recorded feed timestamp plus its reviewed age bound. An already stale feed can produce an already expired receipt. Reading a receipt never extends its expiry.
RPC blocks older than 120 seconds are rejected. Other sources have separate retrieval times. A market retrieval time does not tell you when its quoted price last changed or a trade occurred. Pinned blocks are rechecked for consistency; they are not a finality guarantee. New receipts use schema v3; earlier receipts keep their original schema, policy and evidence.
Questions this scanner leaves open
- Whether reserves or backing are independently established.
- Whether a trade has enough liquidity or a fair execution price.
- Whether issuer operations or all token code are secure.
- Whether you are legally eligible to hold or trade a token.