Bitcoin Forum
December 07, 2016, 10:45:43 AM *
News: Latest stable version of Bitcoin Core: 0.13.1  [Torrent].
 
   Home   Help Search Donate Login Register  
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 [35] 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 ... 96 »
  Print  
Author Topic: [ANNOUNCE] Electrum - Lightweight Bitcoin Client  (Read 243087 times)
interlagos
Hero Member
*****
Offline Offline

Activity: 497


View Profile
June 01, 2012, 07:21:05 PM
 #681

use the -o (offline) option when working with wallets on a non-networked computer.

You can create more than 5 addresses by editing the code, but you have to remember to do that same count when/if you restore in the future. I believe the actual line/file you need to change is documented earlier in this thread.

Line 257 in wallet.py:

Quote

self.gap_limit = 5           # configuration

Or, new receive addresses get automatically created by the client as you use the existing ones.

Thanks for you comments guys, first -o option doesn't seem to affect the generation of addresses/private keys, they are not created in offline mode. Second I haven't tried it but I thought that gap_limit was the amount of addresses that could be imported without breaking the sequence, not the overall amount of addresses. Is that correct?

1481107543
Hero Member
*
Offline Offline

Posts: 1481107543

View Profile Personal Message (Offline)

Ignore
1481107543
Reply with quote  #2

1481107543
Report to moderator
1481107543
Hero Member
*
Offline Offline

Posts: 1481107543

View Profile Personal Message (Offline)

Ignore
1481107543
Reply with quote  #2

1481107543
Report to moderator
1481107543
Hero Member
*
Offline Offline

Posts: 1481107543

View Profile Personal Message (Offline)

Ignore
1481107543
Reply with quote  #2

1481107543
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
Lumpy
Full Member
***
Offline Offline

Activity: 237


View Profile
June 01, 2012, 08:52:16 PM
 #682

From here:

https://en.bitcoin.it/wiki/Electrum

To create an offline wallet, use:

electrum -o create

or if you want a specific file:

electrum -o -w walletfile create
Tuxavant
Hero Member
*****
Offline Offline

Activity: 756


Bitcoin Mayor of Las Vegas


View Profile WWW
June 01, 2012, 08:56:25 PM
 #683

Just FYI... When I say "offline" I'm literally talking like "this computer does not have a network interface"... '-o' in my experience working with an "offline" computer, generally needs the option or python will try to connect to a device that doesn't exist and explode in your face.

Generation Bitcoin | G+ | FB | Bitcoins In Vegas | CoinBus.com | TOR Exit Operator 1MVTPATVCKBMfALRHJsXpHfKJu7GyL7nAc
Lumpy
Full Member
***
Offline Offline

Activity: 237


View Profile
June 01, 2012, 10:20:09 PM
 #684

Are you making a distinction between zero network interfaces and zero connected network interfaces? The latter seems to work for me. Guess not the former?
Tuxavant
Hero Member
*****
Offline Offline

Activity: 756


Bitcoin Mayor of Las Vegas


View Profile WWW
June 01, 2012, 10:32:43 PM
 #685

hum... well, for me, it's a netbook with a wifi device, but it is unconfigured softwarically (lol)... This machine is running linux too. I wonder if that makes any difference.

In any case, when I'm using that netbook, I have no problems when I use -o, and typically get locked up or crash when I don't.

Generation Bitcoin | G+ | FB | Bitcoins In Vegas | CoinBus.com | TOR Exit Operator 1MVTPATVCKBMfALRHJsXpHfKJu7GyL7nAc
zebedee
Donator
Hero Member
*
Offline Offline

Activity: 666



View Profile
June 02, 2012, 03:19:50 AM
 #686

ecdsa.org is missing transactions again  Angry 

I'm curious what's causing this....
ThomasV
Legendary
*
Offline Offline

Activity: 1722



View Profile WWW
June 02, 2012, 06:40:41 AM
 #687

ecdsa.org is missing transactions again  Angry 

I'm curious what's causing this....

I do not know :-(
I should add a detection of this situation in the server

Electrum: the convenience of a web wallet, without the risks
interlagos
Hero Member
*****
Offline Offline

Activity: 497


View Profile
June 02, 2012, 07:05:54 AM
 #688

From here:

https://en.bitcoin.it/wiki/Electrum

To create an offline wallet, use:

electrum -o create

or if you want a specific file:

electrum -o -w walletfile create

Yes it creates the wallet file that way, but if you then type:
electrum addresses -ak
it won't print any, that's the problem for me.

I already asked Thomas about the fix and he said it should be possible, so no worries.

PS: I'm using Ubuntu 10.10 Live CD with Wi-Fi device turned off (physically)
anfedorov
Jr. Member
*
Offline Offline

Activity: 46


View Profile
June 03, 2012, 01:05:59 PM
 #689

I just started playing around with the client, and it's pretty neat!

However, after a bit of testing, there seems to be a bug in the JSON-RPC over HTTP service at ecdsa.org:8081 (and no bug over TCP on 50001). Over TCP, transactions to an account the client is subscribed to yield a nearly instantaneous message from the server of the form:

<-- {"params": ["<account>", "mempool:<len(h)>"], "method": "blockchain.address.subscribe"}

Whereas the HTTP version doesn't seem to report anything to the polling requests.

Could someone verify that this isn't me making some trivial mistake? I used "sudo ngrep -q -Wbyline '' dst host 78.47.154.42 or src host 78.47.154.42" to watch the traffic.
Xenland
Legendary
*
Offline Offline

Activity: 980


I'm not just any shaman, I'm a Sha256man


View Profile
June 03, 2012, 01:15:11 PM
 #690

I just started playing around with the client, and it's pretty neat!

However, after a bit of testing, there seems to be a bug in the JSON-RPC over HTTP service at ecdsa.org:8081 (and no bug over TCP on 50001). Over TCP, transactions to an account the client is subscribed to yield a nearly instantaneous message from the server of the form:

<-- {"params": ["<account>", "mempool:<len(h)>"], "method": "blockchain.address.subscribe"}

Whereas the HTTP version doesn't seem to report anything to the polling requests.

Could someone verify that this isn't me making some trivial mistake? I used "sudo ngrep -q -Wbyline '' dst host 78.47.154.42 or src host 78.47.154.42" to watch the traffic.

If you go up(maybe back a page or two) I read some people were getting balance mistakes from the ecdsa.org server but valid on every other server. it sounds like a mix up on the ecdsa servers only. This is a perfect example why lite bitcoin clients should always cross verify more then 2(or even 6) servers that which are owned/operated by different entities to gain confidence during transaction send/receiving, and information/balance queries.
anfedorov
Jr. Member
*
Offline Offline

Activity: 46


View Profile
June 03, 2012, 05:11:11 PM
 #691

However, after a bit of testing, there seems to be a bug [...]
If you go up(maybe back a page or two) I read some people were getting balance mistakes from the ecdsa.org server but valid on every other server. it sounds like a mix up on the ecdsa servers only. [...]

I just tried it on electrum.novit.ro and btcback.com with the same results: when the client is connected over TCP, an incoming transaction generates the appropriate server->client message in 5-10 seconds, whereas if the client is connected over HTTP, nothing happens (I waited ~2 minutes before restarting the client, at which point the transaction shows up).
flatfly
Hero Member
*****
Offline Offline

Activity: 938


View Profile
June 04, 2012, 08:44:33 AM
 #692

However, after a bit of testing, there seems to be a bug [...]
If you go up(maybe back a page or two) I read some people were getting balance mistakes from the ecdsa.org server but valid on every other server. it sounds like a mix up on the ecdsa servers only. [...]

I just tried it on electrum.novit.ro and btcback.com with the same results: when the client is connected over TCP, an incoming transaction generates the appropriate server->client message in 5-10 seconds, whereas if the client is connected over HTTP, nothing happens (I waited ~2 minutes before restarting the client, at which point the transaction shows up).

Confirmed, HTTP fails for me too. 

EDIT1: are you using the Windows build?  The issue could be specific to Windows builds. I will investigate further.

EDIT2: I have fixed this in Windows build 0.53-2 (just released) - There were some HTTP-related
libs missing following the upgrade to Python 2.7.3.1.

1111127SpvabYpoeDoiz5L7QPkfiSh2Q. Only donate if you have a reason to.
ThomasV
Legendary
*
Offline Offline

Activity: 1722



View Profile WWW
June 04, 2012, 10:32:16 PM
 #693

here is a new thread for server-related discussions and announcements:
https://bitcointalk.org/index.php?topic=85475.0

Electrum: the convenience of a web wallet, without the risks
anfedorov
Jr. Member
*
Offline Offline

Activity: 46


View Profile
June 04, 2012, 11:01:51 PM
 #694

EDIT1: are you using the Windows build?  The issue could be specific to Windows builds. I will investigate further.

No, this was on Ubuntu.

here is a new thread for server-related discussions and announcements: https://bitcointalk.org/index.php?topic=85475.0

Thanks, ThomasV!
anfedorov
Jr. Member
*
Offline Offline

Activity: 46


View Profile
June 05, 2012, 01:10:14 AM
 #695

EDIT2: I have fixed this in Windows build 0.53-2 (just released) - There were some HTTP-related
libs missing following the upgrade to Python 2.7.3.1.

Was this a problem on the client? From what I see in the traffic, the client is polling the server just fine - it's just not getting back the transaction notification.
flatfly
Hero Member
*****
Offline Offline

Activity: 938


View Profile
June 05, 2012, 08:04:16 AM
 #696

EDIT2: I have fixed this in Windows build 0.53-2 (just released) - There were some HTTP-related
libs missing following the upgrade to Python 2.7.3.1.

Was this a problem on the client? From what I see in the traffic, the client is polling the server just fine - it's just not getting back the transaction notification.

On Windows, there was a problem on the client with HTTP connections, which is now fixed. But it seems that what you are reporting is perhaps a separate issue. What is the command you are using in your tests? Do you have the same issue with the "electrum balance" command?

1111127SpvabYpoeDoiz5L7QPkfiSh2Q. Only donate if you have a reason to.
ThomasV
Legendary
*
Offline Offline

Activity: 1722



View Profile WWW
June 05, 2012, 12:30:51 PM
 #697

EDIT2: I have fixed this in Windows build 0.53-2 (just released) - There were some HTTP-related
libs missing following the upgrade to Python 2.7.3.1.

Was this a problem on the client? From what I see in the traffic, the client is polling the server just fine - it's just not getting back the transaction notification.

I confirm that there is a problem with notifications and http. I am investigating it

edit: this was a server bug. I fixed it. it should work now (at least on ecdsa.org)

Electrum: the convenience of a web wallet, without the risks
anfedorov
Jr. Member
*
Offline Offline

Activity: 46


View Profile
June 05, 2012, 06:06:20 PM
 #698

edit: this was a server bug. I fixed it. it should work now (at least on ecdsa.org)

Just re-tested it, and it looks like it's working on ecdsa.org. Thanks for the quick response!
flatfly
Hero Member
*****
Offline Offline

Activity: 938


View Profile
June 06, 2012, 11:16:18 AM
 #699

signmessage / verifymessage don't seem to work for me, verify always produces False - could someone else test as well?

1111127SpvabYpoeDoiz5L7QPkfiSh2Q. Only donate if you have a reason to.
ThomasV
Legendary
*
Offline Offline

Activity: 1722



View Profile WWW
June 06, 2012, 11:25:50 AM
 #700

signmessage / verifymessage don't seem to work for me, verify always produces False - could someone else test as well?


I am aware of the issue; there are two problems:
 - a module was mising in setup.py this is fixed in git  (see recent commits)
 - verifymessage fails with compressed keys (the new format used by the satoshi client). the result is that it will return False on a string signed by the satoshi client using a recent wallet. this was reported by nanotube. it is not fixed yet.



Electrum: the convenience of a web wallet, without the risks
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 [35] 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 ... 96 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!