hunch.Loading current observations…
What these numbers mean.
This view selects configured periodic observers from the service status, compares each timestamp with the current clock, and links to the retrievable evidence. Fresh means a successful observation no more than three scheduled intervals old. It is not a transaction approval or finality guarantee.
Hunch operations generate these observations. They are not customer trades, active users, TVL or revenue. The broader route catalogue includes entries checked on demand; its size is not the number of monitored or executable markets. Successful on-demand checks are not counted in this table.
Independent usage requires independent evidence.
We have not yet published a verified independent operator case study. There is no public active-user, protected-volume or earned-revenue claim. We are inviting builders to produce reproducible evidence with us.
For an opt-in case study, we will agree the methodology: distinct workflow checks, outcome denominators, phase latency, repeated use on separate days and—only with the operator’s consent—receipt-linked settlement. Revalidation calls will not be counted as new trades. Operator identity and wallet or strategy details will not be published by default.
The SDK example records phase timings and outcomes locally. It does not send those measurements to Hunch. Share a redacted summary through the builder review when you want feedback.
Inspect the boundary yourself.
Integration and coverage · Release evidence · Source bundle · Trust disclosures.