Check contract provenance

Question answered #

Does this contract satisfy the supported issuer Stock Token identity check? This panel compares exact deployment evidence with the Robinhood issuer registry. It does not assess every project token deployed on the chain.

Project tokens have a separate published identity check. The contract can have matching project evidence while this panel reports Unrecognized for the issuer-registry lookup.

Accepted inputs #

A valid contract address on Robinhood Chain mainnet, chain ID 4663. Token names, tickers and logos can help with display, but they cannot establish identity.

Evidence sources #

Every valid address gets read-only contract checks on chain 4663: deployed code, name, symbol, decimals and total supply, with a recorded block and individual metadata failures. Automatic explorer and market lookups provide separately sourced observations. The issuer method uses the current asset registry and reviewed stock-token identity mapping where available.

Explorer listings, reported source verification and DEX pairs cannot establish issuer provenance. Canonical requires the reviewed exact chain, address and UID relationship.

Deterministic rules #

The lookup compares chain 4663 and the full address against the issuer registry. Deployed code is required. Reviewed stock-token mappings add their required UID and decimal checks. A familiar symbol cannot replace an address match.

The broader report classification uses positive evidence. A matching issuer deployment with code is an issuer Stock Token; a deployed contract with both current project-source matches is a project token. If neither requirement is met, it remains unclassified. Registry absence alone cannot select a method.

A feed-directory entry or project profile cannot award Canonical in this panel. Each source only contributes to the check it supports.

A conflict in the issuer registry or simultaneous matching issuer and project identities leaves the broader classification unclassified for review. This is separate from recording the evidence each source returned.

Possible statuses #

Canonical, Unrecognized or Unknown. Canonical describes the supported issuer identity result. Unrecognized means the completed issuer lookup found no exact match; it does not label a project malicious or deny its existence onchain.

What can remain unknown #

A missing registry response, conflicting identity evidence or an unavailable required source can prevent a result. Open the details before retrying. Duplicate symbols must not cause a match.

Receipt and expiry #

The receipt keeps chain, address, deployed-code and metadata observations, token classification, check outcomes and source evidence alongside the provenance panel. It also records policy and coverage versions, timestamps and expiry.

Recheck creates a new observation under the current policy. Earlier receipts keep their original schema and interpretation.