[offtopic]
EZ PAY words appeared on a South Park episode (S16E02)! haha xD
Topic: [ANNOUNCE] EZWallet a thin client wallet for BTC (Read 2141 times)
Looks really nice but i'm not able to understand functions properly. :/
Ps: saw your linkedin profile.
Principle Software Engineer at Zynga
Principle Architect at Yahoo!
Computer Engineer at NASA Glenn Research Center
wow
Ps: saw your linkedin profile.
Principle Software Engineer at Zynga
Principle Architect at Yahoo!
Computer Engineer at NASA Glenn Research Center
wow
This wallet looks interesting, but how having to remember Email, Name, Password and Pin; all together, would be easier rather than a seed. Sometimes I cant even remember the email I used to register on a site.
I haven't been getting much time to work on this. I'm looking for someone to help me finish this up. I can pay you in BTC. Send me a PM if you are interested.
You will need to know HTML5, JavaScript and Python. Also you should have a deep understanding of how transactions are created by the original bitcoin program. If you have worked on the original bitcoin client or another client such as Electrum that would be a big plus.
You will need to know HTML5, JavaScript and Python. Also you should have a deep understanding of how transactions are created by the original bitcoin program. If you have worked on the original bitcoin client or another client such as Electrum that would be a big plus.
> Why an *email field?
It doesn't have to be email; it could be any string. Using your email will help to make sure the seed for the deterministic wallet is unique. The email or any other form fields are not sent anywhere; they are just used locally within your browser.
> Why does it have that much content in the placeholders?
Since the fields on the form to open the wallet are critical to recovering the wallet later, I was a bit verbose on how the fields are used.
It doesn't have to be email; it could be any string. Using your email will help to make sure the seed for the deterministic wallet is unique. The email or any other form fields are not sent anywhere; they are just used locally within your browser.
> Why does it have that much content in the placeholders?
Since the fields on the form to open the wallet are critical to recovering the wallet later, I was a bit verbose on how the fields are used.
Not even the form is Easy. Why does it have that much content in the placeholders?
Why an *email field? Thats useless.
Didn't know about this site. I'll change the name to something else.
Changed the name to EZWallet.
Changed the name to EZWallet.
Here's another wallet for bitcoin
What does http://EasyWallet.org think of the name you chose for this?
I developed this browser based wallet for bitcoin. It is completely HTML5 and Javascript based. It works well in FireFox, Chrome and Opera browsers so it can be used on PC, Mac, Linux, iPhone, and Android without having to install any additional plugins or software. It also does not need to download the blockchain to get started. It even supports QR codes.
Source: https://github.com/osyed/ew
demo here: http://arimaa.com:9696
It uses a deterministic wallet so there is no need to store any wallet file. Transactions are created and signed in the local browser so the private keys never leave the browser. It can also be used as an offline wallet to generate and sign the transaction and then send the transaction through an online client. The 'Backstage' tab of the wallet shows the raw transaction and other details.
The browser makes AJAX calls to a Python based web server to get unspent outputs and to send the transaction. The web server can be configured to use either blockchain.info, blockexplorer or electurm to get the unspent outputs and to send the transaction.
I hope that a browser based wallet like this will make it easy for the non-technical folks to safely store, send and receive bitcoins. The wallet even supports a "Send by Email" feature.
Source: https://github.com/osyed/ew
demo here: http://arimaa.com:9696
It uses a deterministic wallet so there is no need to store any wallet file. Transactions are created and signed in the local browser so the private keys never leave the browser. It can also be used as an offline wallet to generate and sign the transaction and then send the transaction through an online client. The 'Backstage' tab of the wallet shows the raw transaction and other details.
The browser makes AJAX calls to a Python based web server to get unspent outputs and to send the transaction. The web server can be configured to use either blockchain.info, blockexplorer or electurm to get the unspent outputs and to send the transaction.
I hope that a browser based wallet like this will make it easy for the non-technical folks to safely store, send and receive bitcoins. The wallet even supports a "Send by Email" feature.
Jump to: