How to configure the Notification Bot

This guide shows how to test burn notifications safely using the @burnevent_info_Bot. The recommended approach is to first verify the pipeline with a dryrun, then (optionally) execute a real burn.

What the Notification Bot does

The Notification Bot (Info Bot) posts burn events into a Telegram group/channel so your community can see what happened.

Key idea: if the Info Bot correctly shows the /dryrun event, it will also show the real /burn event.

Status check: Dryrun visible ✅ → Burn visible ✅

Recommended test setup

We recommend creating a dedicated Telegram group for testing. This avoids spamming your public community during setup.

Create a new private group (e.g. “Project XYZ – Burn Events (Test)”).
Add @burnevent_info_Bot to this group.
Ensure the bot is allowed to post messages (basic member rights are usually enough).

Tip: You can keep this group permanently as your “staging” environment for future changes.

Step-by-step: Register the Info Bot for your project

1) Add the Info Bot to your test group

Add @burnevent_info_Bot to the Telegram group you created.

2) Register the group with the Burn Bot

In the same group (or in your admin chat, depending on your bot’s setup), run:

/register_info <projectId>

Replace <projectId> with your project identifier (exactly as configured on the server).

3) Confirm registration

The Burn Bot will typically respond with a confirmation flow. Complete the confirmation so the group becomes an authorised notification target.

Expected result: The project is now linked to the Info Bot notification group.

Test the pipeline with a dryrun

Next, run a dryrun burn to verify everything end-to-end without executing a real burn transaction.

/dryrun <projectId> <amount>

The exact parameters depend on your project configuration. Use a reasonable test amount for your setup.

Pass condition: If the Info Bot posts the dryrun event in your test group, your notification setup is working.

Optional: Execute a real burn

Once the dryrun notification works, you can proceed with a real burn (if and when you are ready):

/burn <projectId> <amount>

Important: A real burn is irreversible. Only do this after your team has verified the parameters and the connected burn wallet.

Reminder: If the Info Bot correctly displayed the dryrun event, it will also display the real burn event.

Troubleshooting checklist

Make sure @burnevent_info_Bot is actually inside the group.
Verify the group allows messages from bots (permissions).
Double-check the projectId used in /register_info.
If you have multiple chats, ensure you registered the correct one for the correct project.
Run a dryrun again after any change (it’s your safe end-to-end test).