HOW TO READ HEYNOMUS

Evidence first. Gaps included.

Identity before activity

Tokens are identified by chain4663 and contract address. A matching name or ticker does not establish project ownership. Factory discovery records a launch; project-to-token and repository associations are reviewed separately. A verified domain proves DNS control only.

A counted development event

A published release from an associated repository counts as a release. A commit counts as code activity only when its file list includes changes outside documentation, tests, static assets, and lockfiles. Code activity does not prove a deployed product. Website hash changes and token launches are recorded but are not automatically counted as product development.

Build activity

Shipping means a counted event in seven days. Active means a counted event in the preceding thirty days; quiet means within ninety days. Without an observed event, activity is unknown. These labels summarize the collected record, not everything a team may have done.

Heynomus radar v1

Development is min(100, twelve times counted seven-day events plus twice counted thirty-day events). The overall radar uses65% development,20% chain observation,15% source coverage. Source coverage is min(100,25 times successfully read linked sources). A chain observation contributes20 points to that dimension. Market prices and volume are excluded. Ordering is a research aid, not a quality verdict.

Coverage and reorganization

Block indexing records explicit start/end checkpoints and block hashes. Only transactions to watched contracts within scanned blocks are counted. Recent source failures retain their last successful observation time. Usage remains partial until complete coverage can be established; address counts are not people. Block reorganizations rewind observations for replay.

Market history

Market data is read directly from Dexscreener. The displayed reading uses the highest-liquidity observed pool where the tracked token is the base asset; it is not total token liquidity. FDV and circulating market cap are distinguished. Daily history starts with actual collected readings; no historical line is invented.

Imported directory records

An optional one-time directory import uses HEY Research Lab’s public CC BY4.0 export, with source release and checksum retained. Imported verification labels, research scores, ships and market measurements are not imported as Heynomus observations. Ongoing collection does not depend on the HEY research API.

AI answers

InferHub receives the question, bounded conversation history, and the selected project’s public evidence. The server supplies numbered evidence and rejects unknown citation IDs. AI output can still be wrong; inspect the linked source, observation date, and coverage. Private research notes are not supplied to the model.