How to configure the Notify Bot / notification bot

Version V0.0.6

This guide helps Telegram chat admins connect the TokenOps/BEX notification bot, also called Notify Bot, notification bot, Info Bot, or @burnevent_info_Bot.

The bot can post burn updates, BEX activity, verification reports, project proof messages, test pushes, and low-frequency digests to a Telegram group, channel, or forum topic.

There are two notification modes:

• Notify Bot subscriptions: chat-admin controlled mint activity, all-burns, and BEX digest subscriptions. This is the recommended community mode.
• Project Info Bot: legacy project-linked reports and test pushes for owner-managed project workflows.

Telegram is not used as project ownership proof. Wallet access controls project ownership; Telegram chat admins only control where notifications are delivered.

1) Add the bot to your target community group/channel

• Add @burnevent_info_Bot to the target Telegram group or channel first.
• The bot must remain a member to post updates later.
• In a forum group, open the exact topic that should receive notifications before running a registration command.

2) Register Notify Bot subscriptions (recommended)

Use these commands in the group, channel, or Telegram topic where you want messages to appear:

/register mint <mintAddress>
/register all_burns
/register update
/register status

You can also run /register mint without the mint address. The bot then asks for the mint via Telegram reply before creating the subscription.

Use /start to see the command overview. Use /register status or the Status button to see current subscriptions.

The status view lets chat admins:

• pause or resume all subscriptions for the chat,
• open Unsubscribe to pause/resume or unsubscribe one individual registration,
• stop all notification settings for the chat after confirmation.

For Telegram forum groups with topics, run the registration command inside the topic that should receive the pushes. Confirmation replies stay in that topic. If the bot does not already know the topic name, it asks for a readable topic name before confirming the registration. You can skip this with -.

If you need to name or rename a topic later, run this inside the topic:

/notify topic <name>

If you register once in the main chat and once in a topic, both subscriptions can exist and both are shown in status/admin views.

3) Legacy project Info Bot registration

Legacy project-linked channels are still used by some owner workflows, especially direct verification report distribution and project test pushes.

Use this only when the project dashboard or owner flow gives you a specific project ID:

/register_info <projectId>

/register <projectId> may still be accepted as a temporary legacy alias, but it is not the preferred public setup path anymore. For normal community setup, use /register mint <mintAddress>, /register all_burns, or /register update.

If you do not have a project ID, do not guess one. Use the mint-based Notify Bot mode instead.

4) Verify that posting works

• Use the owner menu button Test push to send a simple test message.
• Use /verify to open the Verification Wizard.
• Complete Basic Checks (L1) and Safety Checks (L2).
• After Proof of Burn Capability (L3) or a real burn, you can send the latest report to the linked community channels.

If the Info Bot posts the test push or verification report, your setup is working.

5) How long messages are handled

InfoBot burn notifications are kept as one Telegram message. If a message with embedded ads would become too long, the bot first compacts the burn text:

• BURN CONFIRMED may become CONFIRMED.
• Long token, user, and transaction identifiers may be shortened in the middle.
• The FAQ line may be removed.
• Embedded ads are removed only after those compaction steps are not enough.

If a logo caption is too short for the full message, the bot sends one normal text message instead of splitting the post.

6) Keep it healthy

• Re-run verification after changing wallets, mint, or RPC.
• Proof of Burn Capability should only be started after Basic Checks and Safety Checks are green.
• Verification/report distribution is part of the verification flow and is not a paid package feature.