​
What it watches

Most token failures are preceded by a control-plane change, not a price event: a mint authority reinstated, an upgrade admin rotated, a freeze capability restored, an ownership transfer to a fresh address. Sentry snapshots the authority configuration of monitored subjects and records changes against that baseline. Supported chains: ethereum, base, bsc, solana.

​
The three capabilities

​
There is no subscription model

Sentry has no subscriptions. There is no subscribe endpoint, no tool, and no concept of one anywhere in the codebase.Watches are configured server-side. There is nothing for a consumer to subscribe to, and no delivery mechanism that pushes authority changes to you. Reading the watch history is a poll.
If you need alerting on top of this, the delivery path is the workspace integration dispatch to Slack, Discord, Teams, or Telegram — see Webhooks for what that does and does not do.

​
Baseline semantics

A change event is meaningful only relative to a baseline that was actually captured. A subject with no prior snapshot has no changes — and that is not the same as a subject that was snapshotted and found stable. The states are kept separate for the same reason they are separate everywhere else in this system: “we watched and nothing happened” and “we were not watching” support very different decisions.

​
Availability today

The backing sentry module ships on an unmerged branch. On a master checkout, list_active_watches, get_watch_history, and check_authority_snapshot all return module_absent with a reason.

​
Access

See the Sentry alerts guide for the practical setup.
Scienter publishes impersonal market signals of general and regular circulation. Nothing here is investment, legal, or tax advice, or a recommendation to buy, sell, or hold any asset. Scienter is not a registered investment adviser or broker-dealer. Trading digital assets can result in the total loss of your funds — see Disclaimers for the full text.