read

NEM has recently had an influx of new users and Supernodes. Using block explorers like Nembex or Our NEM Explorer are great tools for keeping track of accounts and transactions, and likewise using the Node Rewards Explorer is also nice for keeping track of one's Supernode status, but the community often would like a more personalized approach, something like instant notifications to their mobile device about updates to their account(s) or status of their Supernode. To this end, the @NemNotificationsBot on Telegram has been released.

What is the Nem Chain & Supernode Notifications Telegram Bot?

The Nem chain notifications bot was created to automate the checking of supernode tests as well as nem account transactions, and harvested blocks to take the hassle out of monitoring your nodes and accounts.

If your supernode goes offline for any reason, is otherwise unreachable or fails any of the tests, you will be notified near instantly, reducing the downtime and losses to a minimum. If your node is unreachable for more than 48 hours, it will be automatically unregistered. If your node is unregistered, the deposit account associated with it will also be unregistered, and any summary data along with it. If your node comes back online, you will also be notified.

When you register a supernode with the bot, the deposit account is automatically registered to your telegram ID number, and you will begin to receive notifications about any failed supernode tests, any blocks harvested as well as any transactions in or out of the deposit account.

After registering a node or account, you have the ability to request account summaries. You can choose 1 day, 7 days, 31 days or a custom number of days up to a max of 90 days.

You can also opt out of any of the different notification types if you wish, to reduce the number of messages you receive from the bot.

How to use the bot

To begin using the bot, search @NemNotificationsBot on telegram and hit start.

The commands for the bot, and how to use them are as follows:

Help

/help

Used to provide some basic help on using the bot, as well as displaying most of the commands available to you

Registering nodes

/registerNode:

Used to register a node or list of nodes.

Example:

/registerNode: 124.3.45.119, 34.102.66.44, 10.34.22.100

You can register as many nodes as you like with one message as long as the IP addresses are comma delimited.

/unregisterNode:

The reverse of the above command.

Registering accounts

/registerAccount:

The same as the /registerNode: command, except that you include nem addresses instead of IP addresses.

Example:

/registerAccount: NBBAP4S6LEILOPYFLNLLRXQKHVVDIGTBPKWIUP76, NAOLIVENEXCVSMUUGYHAPGN43QKHXYX5QGYAZ7AY,
NBFIRDNKPDYF5ZEYS65JDQ237KEUAIWRDFAV7BHA

Addresses with hyphens are also supported. You do not need to have registered a supernode to register an account.

/unregisterAccount:

The reverse of the command above.

You're registration details

/myDetails

Returns a list of all the nodes you have registered along with their associated deposit account and some additional information, followed by a list of any accounts you may have registered that are not associated with any of your supernodes.

Notification options

/optIO

Displays a new set of commands for opting into or out of the different notifications types, e.g., notifications about blocks harvested or newly confirmed transactions.

You are automatically opted in for all notification types by default. You can opt out globally or individually for all accounts. For example, if you have ten accounts registered, you can opt out globally and then opt back in for certain accounts or vice versa.

For all accounts

/optInTxsGlobal

Use this to opt into transaction notifications for all accounts registered to you.

/optOutTxsGlobal

The reverse of the above command.

/optInHarvestingGlobal

Use this to into of harvesting notifications for all accounts registered to you.

/optOutHarvestingGlobal

The reverse of the above command.

For an individual/specific account or a list of accounts

/optInTxsAcc:

Used to opt out of transaction notifications for a single account or a given list of comma delimited accounts.

/optOutTxsAcc:

The reverse of the above.

/optInHarvestingAcc:

Used to opt into harvesting notifications for a given list of accounts. A single account or a comma-delimited list of accounts can be given.

/optOutHarvestingAcc:

The reverse of the above.

Account summaries

/summary

Displays a submenu of the following summary commands.

/dailySummary

Returns a summary of information about all your registered accounts for the previous 24 hours. This includes any accounts associated to the supernodes you have registered.

The information includes total transactions in, out and the sum of transactions both in and out, the total value of said transactions, the sum effect of said transactions on your account, the number of blocks harvested and total fees, the total supernode payout (this will always be zero if the account is not associated with a supernode), the current balance of the account and of course the address of the account the summary is for, as well as the notification types the account is registered for.

/sevenDaySummary

Returns a summary of information about all your registered accounts for the previous 7 days. Returns the same information as above.

/thirtyOneDaySummary

Returns a summary of information about all your registered accounts for the previous 31 days. Returns the same information as above.

/customSummary:

Returns a summary of information about all your registered accounts for the number of days given. Returns the same information as above.

Example:

/customSummary: 5

Will return a 5 day summary of all your registered accounts. Returns the same information as above.

Harvesting

/harvestingSpace

When you use this command, three nodes which have harvesting space are returned. The nodes are chosen from a list of supernodes nodes ordered by their uptime, implying reliability for harvesting.

Removing your information from the server

/deleteAccount

Use this to completely wipe your account from the database. Not displayed in the menu to prevent accidental deletion.

The NEM Team would like to thank Telegram user @kodtycoon for contributing this blog.

Blog Logo

A Nember


Published


Image

NEM

Official Blog of NEM/XEM

Back to Overview