[ANNOUNCE] Electrum - Lightweight Bitcoin Client - page 41.

flatfly

legendary

Activity: 1120

Merit: 1016

090930

Hi Thomas, congrats on the new release!

Just thought I should mention that I get the below error upon starting electrum.

Code:

type error, using default value

[edit] this error only appears the very first time (when the blockchain_headers file doesn't exist yet)

Then the header validation appears to proceed normally.
The whole download + validation process only took 7 minutes in total, great!

Also, the GUI appears to be hanging during that this initial header validation
process - perhaps a little progress dialog or status message would be more user-friendly
(as most Windows users never use the console)

ThomasV

legendary

Activity: 1896

Merit: 1353

I just released version 1.2 of Electrum.

This version includes Simple Payment Verification (SPV).
The SPV module will download blockchain headers (16Mb) and check your transactions, as described in Satoshi's original paper.
This will prevent a malicious server from showing you fake transactions; only verified transactions have confirmation icons.
(note: a malicious server could still hide some of your transactions to you, but that has much less potential for abuse)

Please note that the SPV module will only work if you connect to a server that runs recent code. Please also note that this module is new and has not been extensively tested yet. However, since it operates in an independent thread, it is not capable of crashing the rest of the client, so I am adding it to the release. If it goes wrong, you may disable it using the following command:

Code:

electrum set disable_spv True

Other new feature: Two new commands, 'set' and 'get', allow you to read/write configuration options from the command line.
For example, to display your master public key, type:

Code:

electrum get master_public_key

piuk

hero member

Activity: 910

Merit: 1005

Thanks for merging the CORS patch. However it needs a small modification since after testing browsers often add different HTTP headers.

https://github.com/spesmilo/electrum-server/pull/6

Thanks

ThomasV

legendary

Activity: 1896

Merit: 1353

Quote from: minimalB on October 25, 2012, 05:25:49 PM

Hello,

This happened several times to me recently:

Transactions get processed normally, but i'm getting "transaction rejected by network" message.

Classic mode, latest windows version, standard 0.001 fee paid.
Server used: electrum.bytesized-hosting.com (TCP)

It might be another instance of the the "cannot spent coins" bug
it is a server bug, caused by reorgs, that results in wrong histories being sent.
to fix it, use another server AND regenerate your wallet at that server.

Edit: if you use the latest git code, you can do:

Code:

electrum set history ""

minimalB

donator

Activity: 674

Merit: 523

Hello,

This happened several times to me recently:

Transactions get processed normally, but i'm getting "transaction rejected by network" message.

Classic mode, latest windows version, standard 0.001 fee paid.
Server used: electrum.bytesized-hosting.com (TCP)

flatfly

legendary

Activity: 1120

Merit: 1016

090930

Quote from: marcus_of_augustus on October 24, 2012, 06:41:17 PM

Quote from: adamstgBit on October 24, 2012, 04:22:09 PM

what devices can run Electrum?

what is a good solution for a cheep Electrum device?

Good question ... what's the smallest device known for running Electrum client? Seems like anything that squeeze a minimal python stack PyQT could do it?

You don't even necessarily need PyQT, if you want the absolute smallest footprint (such as for a portable device). I once made a fully functional console-mode Windows build, with the full Python runtime dependencies embedded, that fits in a mere 2MB.

You can also check out the very nice Android and Javascript implementations of Electrum (sorry, don't have the links at hand.)

marcus_of_augustus

legendary

Activity: 3920

Merit: 2349

Eadem mutata resurgo

Quote from: adamstgBit on October 24, 2012, 04:22:09 PM

what devices can run Electrum?

what is a good solution for a cheep Electrum device?

Good question ... what's the smallest device known for running Electrum client? Seems like anything that squeeze a minimal python stack PyQT could do it?

adamstgBit

legendary

Activity: 1904

Merit: 1037

Trusted Bitcoiner

what devices can run Electrum?

what is a good solution for a cheep Electrum device?

ThomasV

legendary

Activity: 1896

Merit: 1353

Quote from: flatfly on October 23, 2012, 12:17:06 PM

Thanks for the explanations.

Today I have updated to the latest master, and no longer have the blockchain.subscribe error message

yes, there was a bug there I fixed it this morning

Quote

but I do get "timeout" messages every 2 minutes or so while connected to ecdsa.org. I guess these are coming from the SPV thread?
Can they be ignored? The connection does seem to be stable.

I couldn't do much more testing (no BTC to play around with, currently).

No, the "timeout" thing is a debugging message from the interface. I will not include it in the final release.
As I mentioned earlier I did an almost complete rewrite of the interface, so that it can be queried by concurrent threads.
This was needed in order to add SPV, because SPV is one of those thread; the other thread interacting with the interface is the wallet synchronizer.

flatfly

legendary

Activity: 1120

Merit: 1016

090930

Thanks for the explanations.

Today I have updated to the latest master, and no longer have the blockchain.subscribe error message, but I do get "timeout" messages every 2 minutes or so while connected to ecdsa.org. I guess these are coming from the SPV thread?
Can they be ignored? The connection does seem to be stable.

I couldn't do much more testing (no BTC to play around with, currently).

ThomasV

legendary

Activity: 1896

Merit: 1353

Quote from: flatfly on October 22, 2012, 02:36:43 PM

Just gave it a try...
I'm getting the below error, as soon as the GUI shows up (using the latest master code):

Code:

Traceback (most recent call last):
  File "1.1\C_\Python27\lib\threading.py", line 551, in __bootstrap_inner
    self.run()
  File "1.1\C_\ElectrumPY\lib\wallet.py", line 1002, in run
    self.validate_header(result)
  File "1.1\C_\ElectrumPY\lib\wallet.py", line 1042, in validate_header
    assert header.get('merkle_root') == merkle_root
AssertionError

[edit:] that was connecting to uncle-enzo. If I connect to ecdsa.org, the GUI remains stuck on "Connecting..." and the following message eventually appears on the console:

Code:

received unexpected notification blockchain.numblocks.subscribe [204503]
timeout

yes, in normal time the first error will mean that the server is trying to screw you, but since I made a mistake in the first version of the server rpc that returns the merkle path of a transaction, I guess the reason is more likely to be that the server hasn't updated yet.
the second error is not important, it was caused because you switched servers within your session.

flatfly

legendary

Activity: 1120

Merit: 1016

090930

Just gave it a try...
I'm getting the below error, as soon as the GUI shows up (using the latest master code):

Code:

Traceback (most recent call last):
  File "1.1\C_\Python27\lib\threading.py", line 551, in __bootstrap_inner
    self.run()
  File "1.1\C_\ElectrumPY\lib\wallet.py", line 1002, in run
    self.validate_header(result)
  File "1.1\C_\ElectrumPY\lib\wallet.py", line 1042, in validate_header
    assert header.get('merkle_root') == merkle_root
AssertionError

[edit:] that was connecting to uncle-enzo. If I connect to ecdsa.org, the GUI remains stuck on "Connecting..." and the following message eventually appears on the console:

Code:

received unexpected notification blockchain.numblocks.subscribe [204503]
timeout

flatfly

legendary

Activity: 1120

Merit: 1016

090930

Quote from: ThomasV on October 22, 2012, 07:10:51 AM

I just merged my SPV branch with the master branch of the repo.
This contains an almost complete rewrite of the interface code.

The interface is now autonomous and separate from the WalletSynchronizer thread.
SPV is performed in a new thread called WalletVerifier.

For the moment SPV does not check difficulty, and its results are not saved to disk, which is a bit inefficient, but these issues will be resolved soon.

That's excellent news. I didn't expect to see functional SPV code so fast

Great job!

ThomasV

legendary

Activity: 1896

Merit: 1353

I just merged my SPV branch with the master branch of the repo.
This contains an almost complete rewrite of the interface code.

The interface is now autonomous and separate from the WalletSynchronizer thread.
SPV is performed in a new thread called WalletVerifier.

For the moment SPV does not check difficulty, and its results are not saved to disk, which is a bit inefficient, but these issues will be resolved soon.

ThomasV

legendary

Activity: 1896

Merit: 1353

Quote from: HostFat on October 20, 2012, 05:43:48 PM

Can you add open a translation project on http://crowdin.net or https://www.transifex.com ?

we currently use the Bitcoin wiki for translating Electrum.
see https://en.bitcoin.it/wiki/Electrum/Translation

HostFat

staff

Activity: 4270

Merit: 1209

I support freedom of choice

Can you add open a translation project on http://crowdin.net or https://www.transifex.com ?

slush

legendary

Activity: 1386

Merit: 1097

Today I updated Electrum server on electrum.bitcoin.cz to latest version. All users are welcome to use SSL transports available on port 50002 (TCP+SSL) and 8082 (HTTPS)!

ThomasV

legendary

Activity: 1896

Merit: 1353

Quote from: Tuxavant on October 19, 2012, 09:42:16 PM

What's the dillio with electrum-desktop.com?

I don't know. That site is controlled by genjix, and he has been inactive and unreachable for over a month...

Tuxavant

hero member

Activity: 784

Merit: 1010

Bitcoin Mayor of Las Vegas

What's the dillio with electrum-desktop.com?

ThomasV

legendary

Activity: 1896

Merit: 1353

Quote from: slush on October 19, 2012, 04:49:52 AM

Thomas, than you for the release! It's great to see that there's some development. I feel a bit shy that I promised some work on server, but didn't finished it yet :-(.

no problem. we will need to work on the server anyway

Quote

Btw do you have any plans with BIP 32? Although current deterministic algorithm works great and I don't have any problem with it, standardization is definitely the way to go. You're also one of few Electrum developers who is capable to implement it (safely)...

Changing the deterministic algorithm is a change that affects users heavily, so I want to minimize the number of times when it happens.
I think we should wait until BIP32 is finalized and used in the official client, so that we can have a compatible wallet. If we do it before them, there are chances the spec will still evolve.

Topic: [ANNOUNCE] Electrum - Lightweight Bitcoin Client - page 41. (Read 274569 times)