Introducing SteemData Notify
Email and Telegram Notifications
SteemData Notify is a free blockchain monitoring service, that sends you (the account owner) Email and Telegram notifications when Payments and critical Account Changes occur.
Example use case
Alice has $10,000 SBD in her savings wallet. Unfortunately, Alice trusted a 3rd party app with her Active key in the past, and this app got hacked recently.
Alice is on her summer vacation, and doesn't monitor her Steemit web wallet on a daily basis. Meanwhile, the hacker triggers a 3 day process of withdrawing the $10,000 SBD from savings, with the intent of stealing it.
Fortunately Alice uses SteemData Notify, sending her immediate notification, which alerts her to cancel the withdrawal, and change her keys, locking the hacker out.
Dust payment based Authentication
Every change of settings on your account in SteemData Notify is authenticated by a dust payment to @null, containing an unique hash as a memo.
The memo hash is derived from a cryptographic signature of the serialized settings object. This ensures that the account owner has authorized a precise and verifiable change. Furthermore the integrity of settings in the SteemData Notify database can be verified at any time. Your private keys are never exposed to any 3rd party in this process.
Try it: notify.steemdata.com
Please note that SteemData Notify is a free service, provided on an as-is basis, with no guarantees of uptime or correctness. Source code is available on github.
This is a great idea.
Unfortunately, it seems like it isn't working right now. I tried using it and haven't gotten a Telegram message confirming my settings even though I sent the correct memo to @null.
Looking through the code I found the likely issue. (Also please consider enabling Issues on the forked GitHub repo so there is an official place to submit these bugs. Furthermore, I noticed there is no license specified in either your repo or flowfree's repository from which it is forked.)
In this line of the code, you require that the memo be exactly 24 characters long, but the memo generated by the service is always 40 characters long.
I have also discovered another issue when experimenting with the service. I first saved settings with some set of options. Then I changed it again with another set of options. In both cases I am pretty sure they are still in an unconfirmed state in your database because of the above bug. But when I try to change the settings back to the earlier configuration, I get an internal server error. My guess is that it is because of this line. I believe it tries to insert a document with the exact same
_idas a previously inserted document and that causes an error.I think what it should do is if it finds an existing item with the same
_id, it should first check to make sure that the_iddoes not match the_idfield offind_user_settings(username)(i.e. you are not trying to set the settings to the currently active one), and if those_ids do not match then it should replace the existing found object in the database with the new one (most of the fields would of course be the same but it would have a newercreated_attime andconfirmedwould be set toFalse). On the other hand if the_ids do exactly match, then it should return a user-friendly error message letting the user know that the settings they want to save are exactly already the currently active settings.Finally, I think your service should warn users that their settings are completely public. Since they are potentially entering in email addresses and/or Telegram public channel links that could be used to find Telegram handles, it is important users are aware of this fact before entering in any data.
The bugs have been fixed.
As far as privacy goes, the server now sends garbled email/telegram id's.
I appreciate the time and effort you've put into catching bugs and making this report. Thank you @arhag.
I think that the service should never, under any condition expose emails or telegram handles, except for the first and last character. This means that the user would have to re-enter their email/telegram with each setting change. This minor inconvenience however is well worth the privacy.
Thanks for you contributio and observation. With people like you,steemit will survive
And the author of this post may God bless you. For trying to create a grate way of notification for we steemit users.
As for me below is the post about my believe for steemit.
https://steemit.com/steemit/@callistus/steemit-the-next-big-social-media-revolution
Wow, good looking out. This was a good article but the bug-checking and warnings you've provided have been at least as helpful as the article. These guys should be paying you hahaha. Thanks again!
very useful,,, thanks,,, follow me @musliadialasyi
Dang. That is a detailed follow-up comment
Well done
I think its' going to take me a while to understand this platform, but I find the information very useful and interesting
It is good Steemit has voluntary developers like you, @arhag, however if Steemit Inc doesn't stepup to do more of the development and management of Steemit, it might fall to a new potential killer > https://steemit.com/steemit/@blockrush/is-wildspark-the-steemit-killer-blockrush
Would you like me to add your app to Steemtools.com ? Would just use that as the desctiption, unless you want to suggest something more succinct.
Sounds good to me. Thank you :)
Telegram Guide
@steemnotifyfurionsteem_notifybot to the channel AdministratorsThanks for the useful app @furion!
But I still could not figure it out ((
I feel stupid)))))
What i did wrong?
Goog luck!
@furion thanks for sharing this would helping me so much. Really appreciated!!
I didnot know how to do ....Can u explain more about this in simplified way
Nice post thank
Amazing work. Free service from reputable author! Thank you @furion!
You want more votes?
Just send any amount higher than 0.5 Steem or 0.5 SBD to @getvotes und you'll receive an 100% upvote from @getvotes
Or you want a vote from a big fish?
For receiving a big surprise just send minimum 3 Steem or 3 SBD to @getvotes
More details: https://steemit.com/vote/@getvotes/want-more-upvotes-click-here
This post received a 4.5% upvote from @randowhale thanks to @getvotes! For more information, click here!
Nice info. Thanks :)
This is great but can I ask you @furion, why would Alice hold that much money in SBD? If she kept it in steem power the hacker would have to request a power down, which I would imagine would be much more common and much more difficult to pull off without Alice eventually noticing. Can you tell me why it seems like my wallet balance is constantly dropping? These types of hacker transactions all show up on the blockchain correct?
Your wallet balance is constantly dropping because the price of Steem is fluctuating. The wallet has an estimated value on it based on multiple things, including the Steem pool and the prices over the past 7 days. Also, maybe Alice just got paid for multiple posts that paid out 50/50 in SBD and Steem Power. Obviously $10K is a lot, but it was just an example.
thanks. You have introduced something useful and very good. Glad to be able to visit your blog. I am very interested dwngan your posting this. I think it's very good and deserves a vote. congratulations guys, hopefully we can become good friends here. On this platform
Amazing. Truely amazing feature for the steemit platform.
This will be extremely beneficial for the old users that have a lot of funds and investments here on the platform.
Tanks for sharing this with the community and i would like to wish you all the best my friend :)
Goldie
@furion this is great info you have sheared here on @steemit with us ,we are so lucky that people like you shear such a nice thing on this great platform. The sucess you have achieved on @steemit u deserve it and you keep shearing such articles you will have an enormous sucess over here. I wish you all the best for your future on steemit . Thanks
Follow me at @naseerbhat upvote and ,resteem