Telegram mining tracker

Use the web mining tracker whenever the bot is unavailable.

The Telegram interface provides reports when you send a command in a private chat. It accepts public Cyprus-1 QUAI mining/deposit addresses and supports English and Turkish. It has no wallet, signing, payment, trading or miner-control capability. From bot 1.1.0 (quaiaxe.com 1.14.0) it can also send opt-in alerts (see Alerts). Group and channel messages are unsupported.

#Save and select an address

After activation, use the dedicated tracker identity published by QuaiAxe. The tracker must use its own bot identity, separate from the owner assistant and buyback notification bot.

1. Send /start or /help in the bot's private chat.
2. Send /track YOUR_PUBLIC_ADDRESS My rig, replacing YOUR_PUBLIC_ADDRESS with your public Cyprus-1 QUAI deposit address. The label is optional.
3. Send /list to see the saved addresses and their numbers, then /use 1 to select the first.
4. Send /status for the selected address.

You can save up to three addresses per chat. /use and /remove take the number shown by /list. Saving an address already in your list updates its label. If you have not selected an address, reports use the first saved address.

For a lookup without saving, paste a public address on its own or send /status YOUR_PUBLIC_ADDRESS. Address checks checksum all-lowercase or all-uppercase inputs and reject an incorrect mixed-case checksum, Qi addresses and addresses outside Cyprus-1.

#Commands

Use the web tracker for the full worker table and chart. The bot's hashrate sparkline is a small summary of reported samples, not a measurement of your device. Workshare counts are not block wins.

#Alerts

Send /alerts to get two checkboxes. Tap one to switch it on or off; the message updates in place. Both are off until you tick them, and alerts start from the moment you do, with no backlog.

The two are always separate messages. Buyback burns are never added to mining burns. A mining block alert is what the pool reports, not a payout receipt. Untick a box, send /forget or block the bot to stop alerts; blocking the bot removes your alert settings. While the bot is not active, or while the operator's alert switch is off, nothing is sent.

#Read a report

Worker statistics, workshares and hashrate history come from the pool. Locked/unlocked balances and the mining burn-vault counter come from public Quai RPC reads. A pool report does not prove that a particular physical device mined, that a rig is reachable or compatible, or that a payout occurred.

Balances retain exact amounts to the underlying 18 decimal places without floating-point rounding; unnecessary trailing zeros are omitted. Unlocked balance is the queried address's balance, not a promise that a payout has been sent to your personal wallet.

Next unlock · window estimate uses the earliest workshare reported in the seven-day window plus 14 days. It does not examine every earlier reward or guarantee a payout date, amount or receipt. With no usable workshare in that window, the estimate is unavailable.

Mining burn vault · global is the entire mining vault's QAXE burn counter. It is not the selected address's personal burn total. Company buybacks and other burns are separate and are never combined into this figure.

Checked is the report's request/cache as-of time in UTC. Repeated requests can reuse a source snapshot for up to 30 seconds, preserving that timestamp. The hashrate Last sample timestamp belongs to the pool measurement itself; a freshly checked report can still contain an older sample.

A missing, failed or malformed source appears as unavailable, while a valid zero remains zero. Other valid source results remain usable. If the network cannot be verified, balance and burn reads remain unavailable. Pool data can be delayed or change independently of this interface.

#Privacy and deletion

Saved settings link your private-chat identifier to your public addresses, labels, selected address and language. The bot does not store message history or wallet credentials. Telegram still receives your messages; the pool and RPC see queried public addresses. The hosting provider processes requests and stores the saved settings, so public addresses do not make the chat-to-address link public consent.

• /remove number removes one saved address.
• /forget immediately deletes the chat's saved addresses, settings and alert choices. It does not erase Telegram's chat history, platform records or existing backups.
• Inactive settings expire after 30 days, except while an alert is ticked. Records of which alerts were already sent are kept for 7 days to prevent duplicates. Cleanup happens when later requests arrive, so physical deletion is not promised at an exact deadline while the service is idle.
• Unlinked update receipts support duplicate protection for 24 hours. They do not contain a chat identifier, address or label; their physical cleanup is also opportunistic.
• Source snapshots may be cached for 30 seconds by public address and report type, without a chat association. Deleting saved settings does not delete those short-lived public-data snapshots.

#When a reply is missing

Leave a few seconds between commands. The bot enforces a per-chat cooldown and a daily service request limit. If either limit is reached, use the web tracker or try again after the indicated wait; a daily limit resets on the next UTC day.

Chat replies are best effort. A failed delivery can lose a reply, and automatic retry or exactly-once delivery is not promised. After an outage, send a new command. An unavailable section does not mean your mining or balance is zero. A successful bot response alone does not establish current hardware operation, payout delivery or on-chain execution.