How to set up mining alerts on Telegram? (Bot Setup)

Creating a Telegram Bot for Mining Notifications

1. Open the Telegram app and search for “BotFather”, the official bot creation tool provided by Telegram.

2. Start a chat with BotFather and send the command /newbot to initiate the bot creation process.

3. Follow the prompts to assign a name and username to your new bot — the username must end with “_bot”.

4. Upon successful registration, BotFather returns an API token — this is a unique string of characters essential for programmatic access.

5. Store the token securely; it grants full control over the bot’s behavior and must never be exposed publicly or committed to version-controlled repositories.

Integrating the Bot with Your Mining Rig

1. Identify the mining software you are using — options include T-Rex, GMiner, NBMiner, or PhoenixMiner — each supports different notification mechanisms.

2. Locate the configuration file or startup script used to launch the miner — typically a .bat file on Windows or a .sh script on Linux.

3. Add logic to detect critical events: hash rate drops below threshold, GPU temperature exceeding safe limits, or connection loss to the mining pool.

4. Use curl or Python requests to send HTTP POST requests to Telegram’s Bot API endpoint: https://api.telegram.org/bot/sendMessage.

5. Format the payload with chat_id (obtained by messaging your bot and inspecting updates via https://api.telegram.org/bot/getUpdates) and a text message containing real-time metrics.

Formatting Real-Time Mining Data for Telegram

1. Extract live stats from the miner’s API — many modern miners expose a local HTTP port (e.g., 4067 or 4068) returning JSON with hashrate, accepted shares, and temperature.

2. Write a lightweight parser in Bash or Python that polls this endpoint every 30 seconds and computes deviations from baseline performance.

3. Structure messages to include time-stamped values: “[14:22] ETH | HR: 62.4 MH/s | Temp: 78°C | Shares: 142 (–3)”.

4. Apply emoji indicators for quick visual recognition: 🔥 for overheating, ⚠️ for stale shares, ✅ for recovery events.

5. Avoid flooding — implement rate limiting so no more than one alert per minute is sent unless severity escalates (e.g., rig offline).

Securing and Maintaining the Alert System

1. Restrict bot visibility — set privacy mode to “Disable” in BotFather so the bot receives all messages sent to it, but only respond to authorized chat_ids.

2. Rotate the API token immediately if any suspicious activity is observed — BotFather supports /revoke to invalidate old tokens.

3. Log all outgoing alerts locally to track false positives and refine thresholds based on historical behavior.

4. Run the alert script under a dedicated system user with minimal permissions — never root or administrator privileges.

5. Validate SSL certificates when calling Telegram’s API — disable insecure HTTP fallbacks to prevent man-in-the-middle interception.

Frequently Asked Questions

Q: Can I receive alerts without exposing my mining rig to the internet?A: Yes. Deploy the alert script on the same machine as the miner and use localhost-only communication. Only outbound HTTPS calls to Telegram are required.

Q: Why does getUpdates return empty results even after I’ve messaged my bot?A: Ensure you’ve sent at least one message to the bot’s @username and that privacy mode is disabled via BotFather’s /setprivacy command.

Q: Is it possible to trigger alerts from multiple rigs using one bot?A: Absolutely. Each rig can send messages to the same bot using its own chat_id. Just ensure each rig identifies itself in the message body (e.g., “Rig-Alpha: …”).

Q: Do Telegram bots support image attachments like GPU utilization charts?A: Yes. Use the /sendPhoto method with a valid image URL or multipart/form-data upload — though most users prefer compact text summaries for speed and clarity.