How to configure the notification bot

Version V0.0.5

This guide helps you connect the Telegram notification bots so burn updates, proof updates, and BEX activity can be posted to your community channel.

There are two notification modes:

• Project Info Bot: legacy project-linked reports and test pushes.
• Notify Bot subscriptions: chat-admin controlled mint, all-burns, and BEX digest subscriptions.

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 Info 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.

2) Register a legacy project Info Bot channel

• In the target group/channel, run:

  /register <projectId>
  

• The bot will create or confirm the project/channel binding.
• Legacy /register_info <projectId> can still work, but /register is the current command.

3) Register Notify Bot subscriptions

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.

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.