Josh_Hamon - Nito - a Telegram Bot for push notifications

Push notifications are now live!

(Use /notify to turn them off or back on.)


I’m going to make a Nito command to ping the node the app is using. Is /ping the right command? Open to suggestions.


/ping is live

This will check the response code of, which the incognito app uses to interact with the chain. If it gets a 200, then your app experience should be normal. If it doesn’t get a 200 back, then it checks the mainnet fullnode. If mainnet gets a 200, then the network itself should be fine and Nito should work as expected, even if the app doesn’t. If mainnet doesn’t get a 200 the recommendation is to come to the forum to investigate.

This gives non-tech users and even non-validators an easy way to check if there is a problem and if it’s just with app or something larger.

Let me know your thoughts and future improvements that will help make Incognito more accessible and powerful.



Hi @Razia, yes Nito is a telegram bot at


What’s work this bot, Sir?


Hi @anon87021727, Sorry, I don’t understand the question. There’s also a FAQ in the original post.


What is work telegram incognito bot?


Ok I will check FAQ.


As of a few minutes ago:

Nito is now watching 10% of the validators! :partying_face::partying_face::partying_face::partying_face:

Wow! I am awed to be able to chip in to the project this way. :pray:


Congrats, that’s an amazing accomplishment!


\o/ congrats @Josh_Hamon! Great work. Long live Nito!


/price is live

/price will return the price as shown on


Voting is here!

Please take time to vote for your favorite product!

(Yep I’m still working on getting PRV to show up as well as node status, I should be able to complete by the end of the month, though maybe not much sooner.)


/status has a minor update

/status will now tell you which vNodes have PRV on them


  • Doesn’t work for pNodes
  • Isn’t part of push notifications (yet)
  • In beta some users have sometimes seen very long run times.

Push now includes PRV!

… well some of the time

:laughing: :crazy_face:

What does that mean?

Most of the time, when your node goes from Earning to Waiting, Nito will correctly report the amount of PRV on your vNode. Due to the inelegant way I’m polling, sometimes Nito polls because the update has happened on the chain.

Adding PRV into notifications has caused me to hit service limits on the # of API calls per month I can make. So while I do plan to create a more robust and flexible notification system* I have to take care of some tech debt and switch platforms so my API call limit goes away. This will great increase the speed of Nito as well. I have updated my roadmap in the OP to reflect this plan.

In the meantime, I hope this is helpful
… some of the time. :wink:

NOTE: Still doesn’t include pNodes

* Robust and flexible notifications: Some users want a notification every time their PRV changes, some just at the end of the cycle. I plan to give users the choice based on their preferences.


Excellent work on this bot. The /status feature is awesome. However, sometimes it will run 20 times in a row before stopping. Anyone else experiencing this bug?

Can you DM me some screen shots if its happened recently?

That would be a lot of screenshots. It’s just the same thing over and over again. It’s like this:

I type /status, and then:

I have found # of nodes, one moment please.
Here’s what I found:
(All nodes listed)

This same thing is repeated. This last time was 26 times before it stopped. Not the end of the world, still worth the value of the tool.

I went to give it a try and yep, I’m now in a similar loop. I’ll have to go digging because I’m seeing in the logs /status being sent, and then sent again two minutes later and again.

1 Like

I had the same issue when hosting a bot in AWS and tried to load Firebase. What I did was stop using AWS.

1 Like