System model

STRSHP indexes supported markets and events into Postgres, enriches them with causal wallet and market evidence, evaluates durable token jobs, and publishes deduplicated alerts.

supported chain events
  → canonical market and wallet records
  → durable token evaluation
  → alert routing and research responses

Data roles

• Postgres holds canonical event, market, wallet, and decision records.
• Redis supports caches, deduplication, and delivery coordination. It is not the source of record.
• Live chain reads confirm state that cannot safely be inferred from indexed history, such as a current token balance.

Separate controls

A chain can be registered for ingestion without being admitted to ordinary alert evaluation. API admission, Telegram commands, and alert routing are also independent controls. This is why Ethereum research can be live while Ethereum push alerts remain off.

Coverage is limited to supported sources and markets. STRSHP does not claim to index every chain event or profile every wallet.

Compare network coverage →