> For the complete documentation index, see [llms.txt](https://docs.digitaldon.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digitaldon.net/the-telegram-bot/setup.md).

# Setting it up

There is no account, no sign-up, no wallet connect and no configuration file. Setup is opening a chat, and — if you want it in a group — tapping a few switches once.

## 1. Start it in a DM

Open [@DigitalDonAnalyzeBot](https://t.me/DigitalDonAnalyzeBot) and hit **Start**, or send `/start`.

You get a short welcome, an example, and an **➕ Add me to a group** button. That's the whole onboarding.

## 2. Scan something

```
/don BONK
```

Ticker, name or contract address — all three work. A few seconds later you get a chart image and the analysis card.

{% hint style="info" %}
**In a private chat you can skip the command entirely.** Paste a contract address or a ticker on its own and the bot analyses it. `/don` is only strictly required in groups, where the bot has to know the message is meant for it.
{% endhint %}

Under the card there are two optional buttons — **📣 Social Sentiment** and **👥 Holder Analysis**. They only run when you tap them, because each one costs real upstream budget. See [Holder analysis](/the-telegram-bot/holder-analysis.md) and [Social sentiment](/the-telegram-bot/social-sentiment.md).

## 3. Add it to a group

Tap **➕ Add me to a group** from `/start`, or add [@DigitalDonAnalyzeBot](https://t.me/DigitalDonAnalyzeBot) the normal Telegram way.

The moment it joins, it **posts a setup card by itself**. No command needed, at any point.

The card is a short explainer plus a checklist:

* ✅ added to the group
* ✅ admin rights — with a `🔄 Check admin rights` button while that one is still open

Then one tap per switch.

{% hint style="warning" %}
**Why it asks for admin rights.** Under Telegram's privacy mode, a bot that isn't an admin never receives ordinary group messages — only commands aimed directly at it. Auto-scan literally cannot see a pasted address without admin. That's a Telegram rule, not a permission grab; the bot doesn't act on anything but messages containing a contract address.

Without admin, `/don` and the other commands still work perfectly. You just lose auto-scan.
{% endhint %}

## 4. The four group switches

| Setting                 | Default | What it does                                                                       |
| ----------------------- | ------- | ---------------------------------------------------------------------------------- |
| 🔍 **Auto-scan**        | on      | A contract address pasted in the group gets answered with a short card             |
| ↳ 🆕 **Fresh launches** | **off** | Whether auto-scan also answers tokens too young to have a chart                    |
| 🃏 **PNL cards**        | on      | `/pnl <contract>` renders [call cards](/in-your-group/pnl-cards.md) here           |
| 🏆 **Leaderboard**      | on      | `/lb` renders the group's [caller leaderboard](/in-your-group/leaderboard.md) here |

**Fresh launches** only appears while auto-scan is on, since it decides *how* auto-scan answers. It's the one switch that ships off: out of the box the bot answers only tokens it can actually analyse, and groups that hunt launches turn it on. Its value is remembered while it's hidden, so switching auto-scan off and back on gives you the same group you had.

Every switch is admin-only. A non-admin tapping one is told so and nothing changes.

## 5. Done

Once you're finished, the card collapses to a single **⚙️ Settings** button so it isn't taking up space in the chat forever.

Admins can reopen it any time with `/setup`. If you prefer typing, `/autoscan on|ta|off` still works (`ta` = auto-scan, but skip fresh launches).

## What "off" actually means

Every switch is genuinely off, not "off with a notice". A group that turns PNL cards off doesn't get an explanation when someone runs `/pnl` — that explanation would be exactly the bot output the admin just declined. Same for the leaderboard, same for auto-scan.

The one thing no switch touches: **`/don` always answers.** The settings govern what the bot says on its own initiative, never what it does when it's asked directly.

## Where to go next

* [Command reference](/the-telegram-bot/commands.md) — everything you can type
* [Adding it to a group](/in-your-group/groups.md) — how auto-scan behaves day to day
* [Analyzing a token](/the-telegram-bot/telegram.md) — the `/don` flow in detail


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.digitaldon.net/the-telegram-bot/setup.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.