> For the complete documentation index, see [llms.txt](https://docs.hipersnipe.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hipersnipe.com/for-operators/operator-checklist.md).

# Operator checklist

For **self-hosting operators** before going live with real user funds. Telegram traders should read [Staying safe](/getting-started/staying-safe.md) instead.

## Environment

* [ ] `.env` created from `.env.example`
* [ ] `TELEGRAM_BOT_TOKEN` set and bot responds to `/start`
* [ ] `HELIUS_HTTP_URL` valid (test with a balance call)
* [ ] `ENCRYPTION_KEY` set or `secure_storage/encryption.key` generated
* [ ] `ADMIN_USER_IDS` includes your Telegram user ID

## Wallet safety

* [ ] Use a **dedicated** trading wallet, not your main holdings wallet
* [ ] Fund with only what you can afford to lose
* [ ] Verify withdraw destination before enabling withdrawals

## Database

* [ ] First boot creates `users.db` automatically
* [ ] WAL mode enabled (check logs for `SQLite WAL mode enabled`)
* [ ] **Never** delete or recreate `users.db` in production

## Trading smoke test

* [ ] `/wallet` — import or generate wallet
* [ ] Paste a token CA — Trading UI opens
* [ ] Small test buy (e.g. 0.01 SOL) on a liquid token
* [ ] Verify transaction on [Solscan](https://solscan.io)
* [ ] Test sell 25% or 100%

## Automation smoke test

* [ ] Set Trading Shield TP/SL on test position
* [ ] Confirm shield appears in `/limits` dashboard
* [ ] Limit engine logs show active shield subscription

## Optional features

* [ ] TG Sniper: `TG_SESSION_STRING` + admin dashboard configured
* [ ] Partner channels: bot added as admin with **Edit Messages of Others**
* [ ] `COMMUNITY_CHAT_ID` set for leaderboard broadcasts

## Go-live

```bash
python start_bot.py
```

Monitor `bot.log` for the first 30 minutes. Set `LOG_LEVEL=DEBUG` only when diagnosing issues.


---

# 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.hipersnipe.com/for-operators/operator-checklist.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.