Check supported coverage

Start with the coverage page #

The scanner accepts any Robinhood Chain token contract address. It reads contract metadata and supply and looks for explorer facts and trading pairs by exact address. You do not need to find a token in PeelSignal’s coverage table before checking it.

Coverage lists the reviewed stock-token oracle pairs that receive prefetched observations. These mappings support additional feed and exposure checks. A reviewed project profile adds a separate identity comparison. Neither is required for general token discovery.

Browse recent observations #

Coverage lists 20 reviewed token-to-USD-feed pairs. Search by symbol, name or contract address, then open Details for the observed price, update time, pause state and source block. These are oracle pairs, not exchange pools or liquidity rankings.

The page prefetches real read-only observations into a shared cache. A cold cache starts a refresh; later visitors reuse the saved results. Refreshes are eligible every 60 seconds while the page is being used. The table shows observation times, and each receipt keeps its original expiry.

An observed price can be available while Price integrity is Unknown. Current coverage has no reviewed Robinhood sequencer uptime source. This missing check does not erase the feed data that was actually read.

The shared oracle sweep focuses on contract and feed observations. It does not query explorer or DEX sources for every row; those discovery checks are marked not attempted in its receipts. Select Run a new check to collect an individual receipt with the full address-based discovery method.

Find a reviewed project profile #

Optional reviewed project profiles are published in projects.json. They specify the exact chain, contract, website token section, GitHub profile and linked accounts used by the project identity method.

A profile records the sources that method may check. It must fetch current website and GitHub claims for the observation; a saved review cannot fill a failed read. See Project identity for the matching rules and limits.

Read refresh and failure states #

Refresh checks the shared cache. It cannot bypass the refresh interval or force every visitor to make a new set of upstream requests. Run a new check starts an individual observation.

If a source fails, the latest attempt shows the failure. A previous successful receipt may be offered separately with its original timestamp; its values never become the new attempt’s evidence. If storage fails, the page keeps the previous observation and reports that the refresh could not be saved.

Feed age, cache age and receipt expiry describe different things. Feed age is measured at the recorded block. The cache refresh interval controls when the page can fetch again. Receipt expiry is recorded when the observation is created and never moves forward on retrieval.

What a reviewed mapping contains #

A reviewed token-to-feed mapping connects a specific chain and token address to an identified feed and adapter. Its metadata explains the checks the service can perform.

• Canonical identity evidence for the chain and contract.
• The feed proxy and reviewed adapter where supported.
• Required price parameters and their source references.
• Linked exposure evidence and its review information.
• The checks that remain unsupported or unknown.

Read directory entries carefully #

A public feed directory can help reviewers find sources. Its entries are not automatically PeelSignal coverage. A feed with a familiar symbol still needs a reviewed connection to the token and chain.

The official oracle documentation links the current feed directory. Use PeelSignal's coverage manifest to establish what this application supports.

If the address is outside coverage #

An address outside reviewed coverage still receives contract reads, an issuer-registry lookup, an explorer lookup and a market lookup. A provider may not index the token, may have no matching pool, or may be unavailable. The report names those outcomes without discarding successful independent reads.

Without an exact reviewed project profile, the optional project identity comparison is outside coverage. Without an exact reviewed token-to-feed mapping, stock-token UID, pause and oracle checks are not attempted. A familiar ticker does not select another token’s sources.

A token can have readable metadata and market pairs while its identity remains unclassified. Discovery records what its sources returned; identity classification requires separate positive evidence. Eligibility remains Not confirmed and describes personal eligibility, not whether a product has launched.

Read Token discovery for address-based lookups, coverage.json for oracle mappings and projects.json for optional reviewed identity profiles.