The NobleBot started its journey on STEEM Blockchain 28 days ago with a view to protecting users funds and accounts who mistakenly broadcast their private keys into the blockchain.
I haven't put out any stats yet until today. So, in this post, I am going to discuss some of the development updates and changes along with some statistics.
Development Update
NobleBot will comment on victim's latest root post if it was able to save the account in case of MASTER PASSWORD or if the user posted PRIVATE posting key. NobleBot will not comment in case of private memo key but will send transfer memo to warn the user.
In the past, I manually notified victims via transfer memos but as mentioned above this now will be an automatic process. NobleBot will comment and send transfer memo too, because a victim may not have any root post. This may change in future though.
Why this change you may ask. I noticed most people do not usually check small transfers carefully because of so much wallet spamming. So, I have decided to comment. There is a risk of getting downvoted by the victim to hide the comment and take a hit in reputation but I am willing to test this out.
Statistics
I am keeping track of things from this month. So, all the numbers you will see are from the month of June 2018.
Accounts Saved
| Master Password Detected | Accounts Updated | Success Rate | Accounts Recovered |
|---|---|---|---|
| 9 | 4 | 44.4 % | 66.7% |
* Accounts missed by NobleBot had less than 1 SBD and STEEM, so thankfully no funds were lost.
Funds Protected
| SBD | STEEM |
|---|---|
| 92.006 | 2.002 |
Apart from these, NobleBot also warned many users who used PRIVATE momo keys in transfer memos. In the time of writing, the bot has not detected any private active keys.
If you have any suggestion or question, please comment below.
The development of this bot is kindly supported by 
Cover photo credit Pexels.com. Edited.