Thank you for your explanation.

If I view this web page:
https://bitaps.com/7a88c9cfda8fdab05977bfe79190218a564f2e00603bfbfade177f50c7001255

... one of the first lines on the page reads:
"Block 701953 [31]"

Is anybody able to tell me the meaning of the "[31]" in that line please?

Debian 11 user here. Apt install gradle, and git cloned bitcoinj as instructed. And then in bash...:

... yields the message:

... has anybody got a fix for the --args= problem please?

13W3BHDJKa35crkUZad6bEw4j1WnCwCXHv

Many thanks Andreas.

I can't find the source file for priv key sweeping. Can somebody give me the path to file please?

Did that glibc problem for linux users get auto-fixed with the 0.9.1 release? Yay! I feared we might be still stuck with 0.9.0's glibc headache:

 https://bitcointalk.org/index.php?topic=522014.msg5795604#msg5795604

... but I just ran the vanilla 0.9.1 in bash in debian wheezy without any trouble at all. Good work devs.

Debian Wheezy 7.4 here:

$ ./bitcoind
bitcoind: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.14' not found (required by bitcoind)

Wheezy uses 2.13 ==> https://packages.debian.org/wheezy/libc6

So I'll have to stick with 0.8.6 for the time being. I trust I'm not hurting the network if I do that, right?

Hi Jeff,

This one gives a good sig:  http://gtf.org/garzik/bitcoin/torrent-msg.txt

... but the code block in this thread's OP is still bad. Diff check shows a line break at line four in the good message (ie., the file at gtf.org), whereas line four in this thread's OP code block goes straight to the text.

Thanks for attending to this Jeff.

It may mean the message we are getting at the browser is not the message Jeff signed.

If this is the case, then there often winds up being an innocent explanation for it, such as that forum software is introducing unwanted line-breaks into the message, or something like that. But at worst, it may mean someone has altered the message.

I just imported the key at http://bitcoin.org/jgarzik-bitpay.asc and then ran:

'$ gpg --verify'

... on the January 11, 2014 pgp signed text contained in the the first post of this thread. It just gave me the output:

gpg: Signature made Sat 11 Jan 2014 19:04:44 GMT using RSA key ID A2DB9CCA
gpg: BAD signature from "Jeff Garzik <jgarzik@bitpay.com>"

Is anybody else getting this problem?

Goonie, now that I have the 3.15 release on my phone, can I be sure that new transactions will not send change back to any of the old addresses that were generated by pre-3.15 versions?

: "I want to fix this"

We should make this your middle name Mike. Busy guy.

Not sure if this belongs in this forum but when I check in Bitcoin Wallet 3.14's Network Monitor, I find all peers are showing block 249844. Bitcoind's getblockcount on my desktop computer is showing the same block number. But this peer:

pool-96-241-72-174.washdc.fios.verizon.net

... has been showing 249845 for several minutes now. What's that about then? No fork I trust :-O

: 'Dagensia Finance s.r.o. Kaprova 42/14 Prague 110 00 Czech Republic'

Isn't slush from Prague? Is slush anything to do with Dagensia?

mtgox has sucked right from the very beginning (ugly screenshot here: https://i.imgur.com/vlKihqr.jpg)

it's incredible that people just keep on using it 

same story on my box. This is the torrent that never sleeps lately.

Hi Hal,

Thanks for your story, it certainly seems to me a life lived fighting for right.

: "I can still read, listen to music, and watch TV and movies. I recently discovered that I can even write code."

Sounds like you are still a busy guy. Nice. :-)

no reason that amounts to a massive big deal really. Sometimes I just like to use gpg.

why not?