Policy and product changes

10 September 2026 · Control reads, largest holders and agent access #

Policy 2.2.0 and receipt schema v4 read owner(), the EIP-1967 implementation, admin and beacon slots and ERC-165 support for ERC-721 and ERC-1155 at the same pinned block as every other contract read. A separate control check records the outcome. A non-fungible contract is now labelled rather than reported as failed ERC-20 metadata.

Token discovery gains a third exact-address source: the explorer holder index. Up to 10 largest holders, their raw balances and their share of the indexed supply are recorded with their own source outcome, retrieval time and content hash. The holder source needs the same explorer access as the address record.

Every receipt now carries a one-line summary and a fixed not-assessed list so a missing section is never read as a clean result. GET /api/check?address= creates the same stored observation as POST for tools that can only fetch a URL. llms.txt and the OpenAPI document use relative links so they are correct on any origin. Earlier v1, v2 and v3 receipts retain their original evidence.

9 September 2026 · Address-based token discovery #

Policy 2.1.0 and receipt schema v3 add total supply reads and automatic explorer and market lookups for any Robinhood Chain token address. The method does not need a manual project profile. Individual checks query exact addresses and preserve independent source failures, matching results, missing records and retrieval times.

Explorer facts, reported source verification, proxy hints, market pairs and unreviewed published links have separate evidence records. Discovered links are not fetched. Market prices do not award Fresh or establish identity. Existing issuer and optional reviewed project identity rules remain separate.

The scanner and coverage page now lead with checking an address. The 20 reviewed oracle pairs keep their shared prefetch flow, which does not query discovery providers for every row. An individual recheck runs the full discovery method. Earlier v1 and v2 receipts retain their original evidence.

9 September 2026 · Project identity and contract reads #

Policy 2.0.0 and receipt schema v2 add basic contract reads for every address, separate token classification and per-check applicability and outcomes. Name, symbol and decimals can fail independently while other evidence remains visible. The four panel vocabularies remain fixed; Canonical stays scoped to issuer Stock Token identity and eligibility remains Not confirmed.

Project coverage version 2026-09-09.1 introduces StockKit. Runtime checks compare the exact chain and contract claims on its reviewed website and GitHub profile, including the account links they publish. Source details record times, matches, conflicts and content hashes. The X profile itself is not queried. These are related project claims, not independent endorsements.

Project identity coverage is published separately in projects.json. Existing stock-token oracle coverage remains at 20 reviewed pairs. A project identity match does not add a DEX quote, oracle mapping, backing assessment or code-security audit.

At this release, new observations used schema v2. Earlier v1 receipts and versioned policies remained unchanged and readable.

9 September 2026 · Contracts outside coverage #

Policy 1.0.2 explains when a contract has no reviewed stock-token mapping. Reports show deployed bytecode evidence and distinguish checks that were not attempted from unavailable source reads. Exposure details no longer imply that a document has been reviewed for an unmapped address.

The four-panel decision rules, coverage mappings and receipt schema are unchanged. Existing receipts keep their recorded explanations and policy versions.

9 September 2026 · Coverage observations #

Coverage version 2026-09-09.1 adds 20 reviewed token/feed pairs, a searchable observations table and cached receipt links. Source reads are batched and common requests are shared within each refresh. Failures and previous successful observations remain separate.

Reports now display available oracle values, feed times and pause reads alongside the precise reason for a missing result. Policy 1.0.1 keeps the four-panel decision rules and updates the network explorer reference. Schema v1 is unchanged. Historical policy 1.0.0 receipts remain readable.

The $PEEL introduction and token documentation have been added. No token contract address has been announced.

Initial implementation versions #

The MVP begins with receipt schema v1 and deterministic policy 1.0.0. Reports use four separate panels. Eligibility is Not confirmed. Receipts are unsigned and rechecks create new observations.

These version labels identify the implementation. They do not certify launch readiness, source availability or the extent of reviewed coverage.

What a version change means #

A policy change can affect how evidence produces a result. Stock-token coverage changes supported oracle mappings; project coverage changes reviewed identity profiles. A receipt-schema change affects how observations are represented.

Use the versions stored on a receipt when interpreting its result. An older receipt remains tied to its original policy and evidence.

Read coverage separately #

Use Coverage, coverage.json and projects.json for the current review records. A product version does not establish that every token, identity source or price check is supported.

Current MVP boundary #

This documentation covers the scanner, four-panel report, public receipt, coverage, methodology and machine-readable files. A labeled demo is an example of the workflow.

Saved-token watchlists, comparison, status-change history, receipt-image export and a public scanning API are outside this MVP documentation. A feature becomes part of these docs when its implementation and limits can be verified.