Pages:
Author

Topic: [BOUNTY] Electrum Firefox Extension (Read 7065 times)

newbie
Activity: 44
Merit: 0
August 25, 2012, 01:52:50 PM
#44
Sent!

Got it, thanks again!
newbie
Activity: 44
Merit: 0
August 25, 2012, 12:57:43 PM
#43
Hey, I'd like to send you a little (0.512 BTC, the most I can afford) donation for your chrome extension. Even though I'm not using it other than for testing, I think you made a great job there?

Where do you want the donation sent? Smiley


Sweet, thanks!

Feel free to send it to 1D2qX2bu7uxKbCbTBvGRrx5ctfwrXYFdDM
legendary
Activity: 1120
Merit: 1016
090930
August 25, 2012, 06:29:44 AM
#42
Thanks for the explanation. I agree the one-time seed stretching delay is reasonable (about 45 seconds on this old laptop).

45 seconds! It's only once, but still, that's stretching it... I'll look into speeding up the SHA256 implementation I'm using, but can't promise anything.

The screenshot helped a ton, thanks! It's the window width: Twitter bootstrap (the UI library I'm using) tries to render a different layout below width 980px that I didn't test, and it breaks everything!

Thanks again for all of the feedback!

Hey, I'd like to send you a little (0.512 BTC, the most I can afford) donation for your chrome extension. Even though I'm not using it other than for testing, I think you made a great job there?

Where do you want the donation sent? Smiley
donator
Activity: 674
Merit: 523
August 16, 2012, 05:02:19 AM
#41
Got it, tnx!
legendary
Activity: 1896
Merit: 1353
August 16, 2012, 02:39:50 AM
#40
I pledge 5btc.


the delay has expired, and nobody proposed an extension that matches the requirements (although a chrome extension has been developed).
I will therefore return your plegde of 5 btc (see PM).
legendary
Activity: 1120
Merit: 1016
090930
August 01, 2012, 03:14:48 AM
#39
I'm surprised this isn't getting more love.
legendary
Activity: 1120
Merit: 1016
090930
legendary
Activity: 1120
Merit: 1016
090930
July 16, 2012, 03:48:23 PM
#37
But... I did just run into another thing Smiley

Suddenly, the seed stretching when creating a new wallet doesn't start at all.
Progress bar stays on 0 and nothing happens. Not sure if this is something
with my browser data or something, I couldn't further investigate yet.

Ah, that was because I got a little too eager deleting code from lib/bitcoinjs. Should be fixed with 0.1.6. I'll go through it (and other parts) more carefully to cut down the size of the package.

Yep, fixed!
I'll be sure to make a small donation when I get some BTC.
newbie
Activity: 44
Merit: 0
July 16, 2012, 03:43:52 PM
#36
But... I did just run into another thing Smiley

Suddenly, the seed stretching when creating a new wallet doesn't start at all.
Progress bar stays on 0 and nothing happens. Not sure if this is something
with my browser data or something, I couldn't further investigate yet.

Ah, that was because I got a little too eager deleting code from lib/bitcoinjs. Should be fixed with 0.1.6. I'll go through it (and other parts) more carefully to cut down the size of the package.
legendary
Activity: 1120
Merit: 1016
090930
July 16, 2012, 03:35:17 PM
#35
Oops, didn't realize I needed to hit "Publish changes" in the developer dashboard for it to go live. Should be upgrading to 0.1.5 now, where it's fixed.


Oh ok Wink v0.1.5 working fine indeed!

But... I did just run into another thing Smiley

Suddenly, the seed stretching when creating a new wallet doesn't start at all.
Progress bar stays on 0 and nothing happens. Not sure if this is something
with my browser data or something, I couldn't further investigate yet.
newbie
Activity: 44
Merit: 0
July 16, 2012, 03:25:03 PM
#34
Oops, didn't realize I needed to hit "Publish changes" in the developer dashboard for it to go live. Should be upgrading to 0.1.5 now, where it's fixed.
legendary
Activity: 1120
Merit: 1016
090930
July 16, 2012, 03:15:58 PM
#33
Also, unless I'm missing something, I guess you can make your package almost 50% smaller
by removing the 'node_modules' folder from bitcoinjs. At first sight, your code doesn't appear
to depend on it.

The jake script which builds lib/bitcoinjs/build/bitcoinjs-min.js depends on it, although the extension doesn't use anything it lib/bitcoinjs except that file. I'll remove it when I make the package, but I'll keep it in github, since I want people to be able to see the code they're running.

I've released a fix to the Options page, so that should be all better now.

Thanks for the quick update!

It seems that the issue with the options page is not totally solved, though:
 (items missing in the black menu bar, vertical positioning of the bar)



But if I maximize the window, then I confirm that it shows perfectly indeed.
newbie
Activity: 44
Merit: 0
July 16, 2012, 02:25:31 PM
#32
Also, unless I'm missing something, I guess you can make your package almost 50% smaller
by removing the 'node_modules' folder from bitcoinjs. At first sight, your code doesn't appear
to depend on it.

The jake script which builds lib/bitcoinjs/build/bitcoinjs-min.js depends on it, although the extension doesn't use anything it lib/bitcoinjs except that file. I'll remove it when I make the package, but I'll keep it in github, since I want people to be able to see the code they're running.

I've released a fix to the Options page, so that should be all better now.
legendary
Activity: 1120
Merit: 1016
090930
July 15, 2012, 04:22:15 PM
#31
Thanks for the explanation. I agree the one-time seed stretching delay is reasonable (about 45 seconds on this old laptop).

45 seconds! It's only once, but still, that's stretching it... I'll look into speeding up the SHA256 implementation I'm using, but can't promise anything.

The screenshot helped a ton, thanks! It's the window width: Twitter bootstrap (the UI library I'm using) tries to render a different layout below width 980px that I didn't test, and it breaks everything!

Thanks again for all of the feedback!

Glad I could help!

Also, unless I'm missing something, I guess you can make your package almost 50% smaller
by removing the 'node_modules' folder from bitcoinjs. At first sight, your code doesn't appear
to depend on it.
newbie
Activity: 44
Merit: 0
July 15, 2012, 03:14:21 PM
#30
Thanks for the explanation. I agree the one-time seed stretching delay is reasonable (about 45 seconds on this old laptop).

45 seconds! It's only once, but still, that's stretching it... I'll look into speeding up the SHA256 implementation I'm using, but can't promise anything.

The screenshot helped a ton, thanks! It's the window width: Twitter bootstrap (the UI library I'm using) tries to render a different layout below width 980px that I didn't test, and it breaks everything!

Thanks again for all of the feedback!
legendary
Activity: 1120
Merit: 1016
090930
July 15, 2012, 12:52:37 PM
#29
Now I'm getting the issue with the Options page again.
Here's a screenshot.

legendary
Activity: 1896
Merit: 1353
July 15, 2012, 12:09:31 PM
#28
very nice.
legendary
Activity: 1120
Merit: 1016
090930
July 15, 2012, 12:08:50 PM
#27
Real nice!!
I like the streamlined foolproof GUI.
Great initial version.
 
2 things I've noticed:

- Options page is blank for me, not sure why... (I only see the "Options" heading and that's it)

- Initial seed stretching is much slower than in Python... I was hoping that Chrome's awesome JS engine would be faster at this, but well.  Or perhaps you're generating more than 5 addresses?

Thanks!

I'm saw the Options page show up blank once as well when testing on my older laptop (with SC2 running in the background for slowness). Not sure what's causing it, but I'll refactor the JS on the Options page to fix it ASAP.


Hmm... Can't post a screenshot as it's now working fine, after uninstalling / re-installing the extension! Very nice and clearly laid-out option page, by the way.


Quote
The initial stretching doesn't include generation of the addresses (which is relatively quick). It's applying SHA256 to the seed 100k times to get the master private key (which is used to generate the private keys of addresses). I think this is slower because Python uses SHA256 implemented in a C library, whereas the extension uses a JS implementation. I don't think there's anything I can do to speed it up, since I want to be compatible with the Electrum client, so I tried to make the UI as clear as possible. Since this only needs to be done once when a wallet is set up, I think I'm satisfied with the current implementation.

Thanks for the explanation. I agree the one-time seed stretching delay is reasonable (about 45 seconds on this old laptop).
newbie
Activity: 44
Merit: 0
July 15, 2012, 04:59:16 AM
#26
Real nice!!
I like the streamlined foolproof GUI.
Great initial version.
 
2 things I've noticed:

- Options page is blank for me, not sure why... (I only see the "Options" heading and that's it)

- Initial seed stretching is much slower than in Python... I was hoping that Chrome's awesome JS engine would be faster at this, but well.  Or perhaps you're generating more than 5 addresses?

Thanks!

I'm saw the Options page show up blank once as well when testing on my older laptop (with SC2 running in the background for slowness). Not sure what's causing it, but I'll refactor the JS on the Options page to fix it ASAP.

The initial stretching doesn't include generation of the addresses (which is relatively quick). It's applying SHA256 to the seed 100k times to get the master private key (which is used to generate the private keys of addresses). I think this is slower because Python uses SHA256 implemented in a C library, whereas the extension uses a JS implementation. I don't think there's anything I can do to speed it up, since I want to be compatible with the Electrum client, so I tried to make the UI as clear as possible. Since this only needs to be done once when a wallet is set up, I think I'm satisfied with the current implementation.
legendary
Activity: 1120
Merit: 1016
090930
July 15, 2012, 04:16:34 AM
#25
Real nice!!
I like the streamlined foolproof GUI.
Great initial version.
 
2 things I've noticed:

- Options page is blank for me, not sure why... (I only see the "Options" heading and that's it)

- Initial seed stretching is much slower than in Python... I was hoping that Chrome's awesome JS engine would be faster at this, but well.  Or perhaps you're generating more than 5 addresses?
Pages:
Jump to: