Observe
Monitor supported transactions, contract state, market conditions, holder structure, and versioned data—recording source, network, timestamps, collection time, and detector version.
Method
How Heist turns activity into an answer.
Heist is designed to move from reproducible market evidence to a clear, amount-aware explanation without hiding the steps in between.
Check a published condition
Deterministic rules evaluate whether a supported condition changed. A language model does not decide whether a critical event occurred or set its severity.
Add context
Where supported, compare the event with dated declarations, wallet attribution, historical behavior, connected-wallet evidence, and relevant facts. Context cannot erase the observed event.
Separate the conclusion
Present the observed fact, attribution and confidence, best-supported explanation, credible alternatives, known unknowns, and evidence that could change the conclusion independently.
Calculate impact at your amount
When supported data is available, estimate what buying or selling may return through a checked path—including timestamp, amount, fees, price impact, freshness, assumptions, and limits. It is not a live quote.
Apply your approved rule
Identify which approved condition triggered the alert. Future rules can change; the evidence behind an earlier event cannot.
Deliver and record
Record event time, eligibility, delivery attempt, provider acceptance, corrections, outcome, detector version, and coverage state under a published latency definition.
What the method cannot establish
Public activity does not always reveal identity, intent, offchain agreements, every trading path, or what will happen next. Heist may observe an event correctly and explain it incorrectly.
That is why facts, attribution, explanations, confidence, unknowns, and later corrections remain separate.