The same text fragment can point to very different things. WALPHA keeps identity typed so that a ticker page cannot silently become a bag of every contract mentioned nearby.
Core entity types
| Entity | Stable key | Meaning |
|---|---|---|
| Account | platform + handle or account id | A social source or participant |
| Ticker | normalized symbol | A textual market symbol observed in discourse |
| Token contract | network + address | A unique on-chain asset identity |
| Project | resolved project identity | A product or community that may own one or more assets |
| Narrative | normalized topic or thesis | A theme expressed across many sources and entities |
| Evidence item | source + source id | The canonical observation supporting a claim |
Tickers are not contracts
A ticker is ambiguous by nature. The same symbol may be used by multiple contracts, while a project may migrate or launch more than one contract. WALPHA therefore treats ticker-to-contract links as evidence-backed relationships with a status and source.
A contract, by contrast, has one network-qualified identity. Its canonical metadata can contain one primary symbol at a time, while historical or conflicting labels remain observations rather than additional identities.
Relationship states
- resolved — metadata or explicit source evidence supports the link;
- candidate — evidence suggests the link but is insufficient to promote it;
- co-mentioned — both entities occurred in the same source context;
- report-only — a generated finding, kept outside canonical evidence;
- rejected or superseded — preserved for audit, no longer active.
Why entity boundaries matter
Typed identity prevents unrelated contracts from flooding a ticker dossier, keeps market snapshots attached to the correct asset and lets future Solana, Robinhood Chain and Base data coexist without accidental merging.