> For the complete documentation index, see [llms.txt](https://docs.tallyprotocol.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tallyprotocol.xyz/product-modules/guardian.md).

# Guardian and the Telegram bot

Guardian watches the tokens in your wallet and tells you when something changes. Alerts are private to the wallet that linked them, so linking needs a sign-in.

## Rules

| Rule                   | Fires when                                                                                                       |
| ---------------------- | ---------------------------------------------------------------------------------------------------------------- |
| Paused or halted       | An issuer pauses a token you hold. Ondo's status comes from the API; bStock's from its shared pause manager.     |
| Share count changed    | A token's share multiplier changes: "Your token count is the same; your shares rose 0.6% (dividend reinvested)." |
| Grade drop             | A held token falls to a lower Radar grade.                                                                       |
| Thin liquidity (ghost) | Trading on a held token drops under $1,000 in 24 hours.                                                          |
| Price threshold        | The market price crosses a limit you set.                                                                        |
| Earnings               | A token you hold is limited around earnings.                                                                     |

Alerts are de-duplicated, respect quiet hours (set in UTC) and can be turned on and off per rule in the Guardian settings.

## Linking Telegram

1. Open Guardian while signed in and generate a link code: eight characters, valid for ten minutes, with at most five attempts in ten minutes.
2. Open the Tally bot and send `/link CODE`. The link is stored against your wallet and the chat.
3. `/unlink` removes it and stops alerts.

Saving settings is a **verified write**: the server verifies your Privy access token and checks the wallet against your own linked accounts before it accepts a change. The page cannot change another wallet's settings by naming it.

## Bot commands

| Command                      | What it does                                         |
| ---------------------------- | ---------------------------------------------------- |
| `/quote TICKER [usd]`        | Compare issuers in shares (default $25, minimum $6). |
| `/shares 0xADDRESS`          | Holdings in shares across issuers for any address.   |
| `/shield TICKER`             | Integrity grades, traps and flags for one stock.     |
| `/link CODE`, `/unlink`      | Link or unlink your wallet.                          |
| \`/alerts on                 | off\`                                                |
| `/quiet 22-07`, `/quiet off` | Quiet hours in UTC.                                  |
| `/help`                      | The list above.                                      |

The bot is **read-only**: it never builds or sends a transaction. The bot registers its command list so Telegram shows suggestions when you type `/`, and it prints wallet addresses in a form you can copy with a tap.

## Design choice

Guardian's alert history and link records live in the same snapshot store as everything else, and are among the kinds that retention never prunes.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.tallyprotocol.xyz/product-modules/guardian.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.