Want to pay someone in STEEM or SBD without giving anyone your keys?
With Steem SafePay, your keys never leave your browser.
Steem SafePay is a single, simple HTML file that can be used straight from your PC (with no web server) or modified and served by any web server to fulfill any payment or donation scenario.
Since I'm a developer rather than a web designer, the look is currently bare -- but, if you know HTML, you can dress it up in any way that you want.
Notice that the file is being served off of *YOUR* PC . . . . so you have complete control.
So . . . . what is in this miraculous file? It must be monstrous you say . . . . Nope!
That's it.
Of course, it does have two helper files. The first is JQuery, the most popular Javascript library in use today. Since it is being served up by Google, you can be sure that it is safe.
The second helper file is Digital Wisdom's Steem-Browserify (the first fully-capable cross-browser STEEM api implementation). Since it is being served off your PC as well, you can examine it to your heart's content and be sure that it is equally safe. In the future, we will be submitting it to Steemit so that they can validate it, certify it and hopefully serve it off of their servers so that you can be positive that it is safe.
Stay tuned tomorrow when we'll introduce the Steem-Browserify project -- initiated so that we could pursue @Ned's Bounty System Bounty and @cryptojoy.com's WooCommerce Bounty. For now, you can download the two SafePay files from https://drive.google.com/open?id=0BzwddigrgTL4WTZhUk5zUXRFZ0k (SafePay.htm) and https://drive.google.com/open?id=0BzwddigrgTL4cm5GZTc1S2Rrdk0 (steem.js).
This is awesome. I've actually been trying to build on to it; however, I am getting the following error:
steem.js:34 WebSocket connection to 'wss://steemit.com/wspa' failed: Error during WebSocket handshake: Unexpected response code: 404
I attempted downloading your steem-browserify package and when I ran "node test" I get an error for data.id... id is undefined.
Do you have any advice? I'd love to work on this!
Downvoting a post can decrease pending rewards and make it less visible. Common reasons:
Submit
Cool, just for my understanding, would the Active key ever be in contact with any machine outside of my own PC? Thanks for helping make things more easy.
Downvoting a post can decrease pending rewards and make it less visible. Common reasons:
Submit
No, your keys never leave your machine. The transaction is signed on your machine and your active key goes absolutely nowhere. That is the entire point. I've been really distraught about all these people who promise not to save your key and not to leave it in cookies. I don't even want anyone trusting me because there is just too much that can happen once that key leaves your PC.
Downvoting a post can decrease pending rewards and make it less visible. Common reasons:
Submit
Interesting concept. Thanks for doing this.
Downvoting a post can decrease pending rewards and make it less visible. Common reasons:
Submit
Is this a chrome extension? If not can you make it a chrome extension.
Downvoting a post can decrease pending rewards and make it less visible. Common reasons:
Submit
Why Google Drive?
It should be on Github, where it's easier to contribute to.
Either way, great work, even if it is very basic.
Downvoting a post can decrease pending rewards and make it less visible. Common reasons:
Submit
steem-browserify is on npm and github. Google Drive was just to hold it temporarily until it was officially announced later today.
Downvoting a post can decrease pending rewards and make it less visible. Common reasons:
Submit