Silence is not a statement.
Nothing changed, not re-observed, and not notifiable are indistinguishable.
Be told when a token's evidence changes
A dossier is a point in time. Evidesa re-observes watched tokens on a schedule and records what moved between one observation and the next — and the watch is how that record reaches you without your having to come back and look.
One message when a saved observation records a qualifying change. The watch has two channels — a Telegram bot, and a delivery destination you register — and this deployment runs only the second: no Telegram bot is configured here, so the commands below describe the channel rather than open it. Re-observation itself runs either way, and the record it advances is what every timeline and incident is read from.
A quiet week is not evidence that a token is behaving, and nothing here certifies that it is.
What reaches you
Every class below is recorded for every watched token. The difference is only whether a recorded change is delivered.
Sent by default
No request neededA change to the mint or freeze authority, to the metadata update authority, to the token program or its extensions, to the recorded risk band, or to whether the evidence behind a category could be read at all. These are the changes that alter what a holder is exposed to without any trade taking place.
Sent on request
+holders · +liquidityHolder-concentration movement across the top accounts and their owner authorities, and movement in the selected pair's liquidity. Recorded for every watched token either way; delivered only if asked for, because they move often enough that sending them by default would train a reader to ignore the messages that matter.
Never sent
Not available on requestPrice movement. A message about a named token's price is advice whatever its wording, and there is no opt-in for it. It is recorded in the dossier's change timeline, where a reader has chosen to look, and it stays there.
The watch's own receipts
Every delivery attempt writes an append-only receipt the runtime cannot edit. This is the last 24 hours of them, in aggregate — counts and latencies, never a token and never a chat.
No delivery was attempted in this window.
A window with zero receipts can mean no watched token recorded a qualifying change; it is not a failure record. A transient failure is retried by the next sweep, and the retry writes its own receipt — nothing is dropped silently, and nothing here can be rewritten after the fact.
How to start
These are the Evidesa bot's commands. This deployment does not publish the bot's Telegram address, so there is nothing here to start it from — the commands are documented, the door is not. Up to 5 tokens per chat once you are in a chat with it.
- /watch <mint address>
- Start watching a token.
- /watch <mint address> +holders +liquidity
- Also deliver holder-concentration and liquidity movement.
- /unwatch <mint address>
- Stop watching one.
- /list
- What this chat is watching.
- /stop
- Delete the chat reference, the encrypted identifier and every watched token.
Availability. The watch runs only where this deployment has been configured with a bot and the keys needed to encrypt a chat identifier. Partial configuration is treated as off rather than as a degraded mode: a watch that accepts subscriptions it cannot deliver is worse than one that is plainly unavailable.
What Telegram sees. Telegram keeps its own copy of the conversation under its own policy. Evidesa cannot delete that; /stop removes everything on this side and you can clear and block from yours.
Evidesa is not financial advice and does not certify safety.