I cannot be 100% sure that your problem is exactly the same as what vuce encountered.
I remember that you reported strange problems associated with your wallet on irc (inability to regenerate the same key sequence), which does not make sense with this bug.
Therefore the bug you have might be different.



I am no longer an active developer.
I do still help answer questions and diagnose bugs, in order to ensure a smooth transition, but I try not to get involved in development.
Thus I hope this bug will be fixed by the current team.

I have been talking with vuce and we have found the cause for that bug: the server sent corrupted data.
[the server sent an unspent tx output without 'raw_output_script' field, I believe this might have been caused by a reorg.]

You should be able to recover your coins by regenerating your wallet from seed on another server, different from the server that sent you incorrect data.
Please let me know if it works.

Another problem is with the current protocol, which is not robust enough. The protocol should use a hash of the complete history of each address in order to determine whether the history needs an update. It is not doing that now, which is why it is not sufficient to simply connect to another server. This was one of the things I wish I had time to fix before genjix took over. I hope this gets fixed (as well as the server issue).

might be relevant: http://localbitcoins.com

NFC is better and faster than QR code because it requires less attention/cognitive load.
You do not need to look at your screen while you aim at a QR code; you just need to bring your device close to the reader and a beep will tell you that the data were transferred. This is something that you can do it while looking somewhere else, for example if you are talking to someone.

This is important, because the act of looking at your screen while aiming at a QR code look makes you look like a nerd. These are the kind of things that can hamper widespread adoption.

Once the payment address and amount are transferred to your device, your bitcoin client will ask you to confirm and/or enter a password.
Then your device can send the transaction to the network.

To make things even faster, your device could also send the signed transaction directly to the nfc reader; this might save a few seconds of propagation time in the bitcoin network. This would require you to bring your device again near the NFC reader.

can you try to create the transaction in text mode?
this will show us if it is a gui problem or not.

to keep it reproducible, do not actually send the coins, use the 'mktx' command instead: it will dump the raw transaction on the screen

I guess this is relevant to various Bitcoin sites:

http://threatpost.com/en_us/blogs/new-attack-uses-ssltls-information-leak-hijack-https-sessions-090512

according to the article, patches should be available in the coming weeks.

how about a screenshot of the http://romneygirl.org/ video at 1'18 ? that would be a proof!

Minimal quality standard I expect from an exchange: https://bitcointalk.org/index.php?topic=83933.0

the fact that the proportion of unspent coins is higher for 2009.
I don't see why coins from 2009 would be hoarded more than coins from 2010.

I have updated the velocity graphs at ecdsa.org: http://statistics.ecdsa.org
The new graph shows the blockchain up to block 195000 (august 21th)

I have added a red "ruler" on top of the graph, in order to measure the amount of bitcoins remaining per time interval.
For example, with the ruler you can read that 1.1 million bitcoins have not moved since 2009.

Interestingly, the proportion of unspent coins decreased significantly in 2010.
This suggests that a large fraction of 2009 coins are not being hoarded, but have been lost.

As time passes, we should see some areas of the graph getting completely emptied of their unspent coins; this isn't the case yet, except in very small regions.

Because of US economic sanctions, iranian players cannot connect to WoW anymore, and Blizzard has announced that they will not be refunded:
http://eu.battle.net/wow/en/forum/topic/5168067998?page=97#1933

Could this be an opportunity for Bitcoin?
Someone could easily setup a VPN for these players, and/or let them exchange WoW gold for BTC

follow up: apparently, on Windows you need to add quotes around the signature, like this:

it means that there is a problem with the format of the signature, not that the signature itself is wrong.
try to add quotes around the signature.

btw, there seems to be a bug with verifymessage on Windows.
see https://bitcointalk.org/index.php?topic=50936.msg1135155#msg1135155

oh, I did not see that you wanted a multi line message.
you can use \n for new lines:

Example:


and to verify:

note: if the address you want to sign with is not in your Electrum wallet, you need to import it first:

I think it is reasonably easy to do.
It will increase traffic and workload on the servers, but I think that eventually server operators will find a way to handle this.

another extension that I did not have time to work on is client authentication at a server; this would open the door to commercial servers.

Here is a variant with broken arcs (as in the first image posted by slush):



not sure which one is better...

Here is a drawing I just made, reflecting my initial idea and the colors proposed by grondilu:



it is a svg file, feel free to improve it: https://ecdsa.org/electrum_logo.svg

I tend to agree with the observation that electron cloud orbitals are not popular enough to be interpreted correctly by a large audience...