.

[Xenland]

This might help my Pseudo Bitcoin Client Documentation project I'll be looking into this code shortly

[1714785389]

1714785389

[1714785389]

1714785389

[1714785389]

1714785389

[runeks]

The reason I ask is because I got curious over whether people have used insecure passwords to create brain wallets. For this purpose I've created 1.5 GB worth of addresses in that 20 byte raw format, out of a word list made by John the Ripper.

So, that same list in ASCII will be 3GB ... BFD, if you'll pardon my french.

When the block chain is loaded into memory, the operation will mostly be memory-bound. Loading an additional 3 GB into memory is not an option.

I've just ordered more RAM, to bring my machine up to 6 GB though. Although it hurt a bit to see that the same amount of DDR3 RAM was half the price of the DDR2 RAM my machine supports

So the reason is that even though there are only ~300 megs of different addresses in the block chain, there are (2^160)*20 bytes of possible addresses using the raw 20 byte format. Having the addresses lined up on 20 byte-boundaries also increases performance, I imagine, since I don't have to do any string parsing on the data.

IMO, the time it'll take to parse the ASCII will be dwarfed by
the time taken to chew through the blockchain while hammering
in a completely cache-incoherent manner at that 1.5GB hashtable
of restricts you just forced the parser to load and work with.

I'm currently working with 50 MB chunks (~2.6 million addresses) at a time, because of the aforementioned memory-restriction. How long do you think blockparser would take to parse that amount of addresses? Armory's Python tools does it in 120 seconds (not including the time it takes to load the block chain into memory).

Also ... I'm hoping you're planning to Do The Right Thing (tm) with
that attempt of yours. Nuff said.

Of course. I'm not a thief. Just curious.

[Buffer Overflow]

Code:

info: Starting command "simpleStats"
fatal: No such file or directory: failed to open block chain file /home/buffer/.bitcoin/blocks/blk00000.dat
Aborted (core dumped)

I don't have the blocks/ directory?

I only have:

blk0001.dat
blkindex.dat
db.log
peers.dat
blk0002.dat
database/
debug.log
wallet.dat

Using Bitcoin 0.7.1 & latest version of blockparser.

[Buffer Overflow]

Ok, thank you very much.

How do I change over to the new style blockchain files? I'm using 0.7.1.

[Buffer Overflow]

Oh dear more problems. Just cloned latest commit and tested with ./parser simpleStats and this appears:

warning: at depth 20221 in chain, failed to locate parent block 000000000000040167c69f7a835d124214316b72d9a9fc2ec2413a238b6ab6da
warning: at depth 12432 in chain, failed to locate parent block 000000000000040167c69f7a835d124214316b72d9a9fc2ec2413a238b6ab6da
warning: at depth 4315 in chain, failed to locate parent block 000000000000040167c69f7a835d124214316b72d9a9fc2ec2413a238b6ab6da
warning: at depth 14255 in chain, failed to locate parent block 000000000000040167c69f7a835d124214316b72d9a9fc2ec2413a238b6ab6da
warning: at depth 2975 in chain, failed to locate parent block 000000000000040167c69f7a835d124214316b72d9a9fc2ec2413a238b6ab6da
warning: at depth 13760 in chain, failed to locate parent block 000000000000040167c69f7a835d124214316b72d9a9fc2ec2413a238b6ab6da
warning: at depth 15626 in chain, failed to locate parent block 000000000000040167c69f7a835d124214316b72d9a9fc2ec2413a238b6ab6da
warning: at depth 15844 in chain, failed to locate parent block 000000000000040167c69f7a835d124214316b72d9a9fc2ec2413a238b6ab6da
warning: at depth 629 in chain, failed to locate parent block 000000000000040167c69f7a835d124214316b72d9a9fc2ec2413a238b6ab6da
warning: at depth 3965 in chain, failed to locate parent block 000000000000040167c69f7a835d124214316b72d9a9fc2ec2413a238b6ab6da
warning: at depth 3249 in chain, failed to locate parent block 000000000000040167c69f7a835d124214316b72d9a9fc2ec2413a238b6ab6da
warning: at depth 13269 in chain, failed to locate parent block 000000000000040167c69f7a835d124214316b72d9a9fc2ec2413a238b6ab6da
warning: at depth 8480 in chain, failed to locate parent block 000000000000040167c69f7a835d124214316b72d9a9fc2ec2413a238b6ab6da
warning: at depth 16582 in chain, failed to locate parent block 000000000000040167c69f7a835d124214316b72d9a9fc2ec2413a238b6ab6da
warning: at depth 18383 in chain, failed to locate parent block 000000000000040167c69f7a835d124214316b72d9a9fc2ec2413a238b6ab6da
warning: at depth 6801 in chain, failed to locate parent block 000000000000040167c69f7a835d124214316b72d9a9fc2ec2413a238b6ab6da
warning: at depth 14939 in chain, failed to locate parent block 000000000000040167c69f7a835d124214316b72d9a9fc2ec2413a238b6ab6da

I have to exit with ctrl-c.

[Buffer Overflow]

Ok, thank you very much.

How do I change over to the new style blockchain files? I'm using 0.7.1.

Code:

git clone git://github.com/bitcoin/bitcoin.git bitcoin-head
cd bitcoin-head
qmake-qt4
make -j4
./bitcoin-qt &

Be aware this is going to "upgrade" your datafiles
and that this "upgrade" is likely not reversible.

You might want to wait until this is officially supported
by the released client.

Oh, I see, it's in Beta state. Think I leave it then.

[Pieter Wuille]

Oh, I see, it's in Beta state. Think I leave it then.

Well, all bitcoin releases to date have been beta.

This is about the code that hasn't even been released, but will eventually become 0.8.

[Buffer Overflow]

Oh, I see, it's in Beta state. Think I leave it then.

Well, all bitcoin releases to date have been beta.

This is about the code that hasn't even been released, but will eventually become 0.8.

That's a good point. I wonder when Bitcoin will come out of beta? 1.0 I guess.

[Jouke]

Oh dear more problems. Just cloned latest commit and tested with ./parser simpleStats and this appears:

warning: at depth 20221 in chain, failed to locate parent block 000000000000040167c69f7a835d124214316b72d9a9fc2ec2413a238b6ab6da
warning: at depth 12432 in chain, failed to locate parent block 000000000000040167c69f7a835d124214316b72d9a9fc2ec2413a238b6ab6da
warning: at depth 4315 in chain, failed to locate parent block 000000000000040167c69f7a835d124214316b72d9a9fc2ec2413a238b6ab6da
warning: at depth 14255 in chain, failed to locate parent block 000000000000040167c69f7a835d124214316b72d9a9fc2ec2413a238b6ab6da
warning: at depth 2975 in chain, failed to locate parent block 000000000000040167c69f7a835d124214316b72d9a9fc2ec2413a238b6ab6da
warning: at depth 13760 in chain, failed to locate parent block 000000000000040167c69f7a835d124214316b72d9a9fc2ec2413a238b6ab6da
warning: at depth 15626 in chain, failed to locate parent block 000000000000040167c69f7a835d124214316b72d9a9fc2ec2413a238b6ab6da
warning: at depth 15844 in chain, failed to locate parent block 000000000000040167c69f7a835d124214316b72d9a9fc2ec2413a238b6ab6da
warning: at depth 629 in chain, failed to locate parent block 000000000000040167c69f7a835d124214316b72d9a9fc2ec2413a238b6ab6da
warning: at depth 3965 in chain, failed to locate parent block 000000000000040167c69f7a835d124214316b72d9a9fc2ec2413a238b6ab6da
warning: at depth 3249 in chain, failed to locate parent block 000000000000040167c69f7a835d124214316b72d9a9fc2ec2413a238b6ab6da
warning: at depth 13269 in chain, failed to locate parent block 000000000000040167c69f7a835d124214316b72d9a9fc2ec2413a238b6ab6da
warning: at depth 8480 in chain, failed to locate parent block 000000000000040167c69f7a835d124214316b72d9a9fc2ec2413a238b6ab6da
warning: at depth 16582 in chain, failed to locate parent block 000000000000040167c69f7a835d124214316b72d9a9fc2ec2413a238b6ab6da
warning: at depth 18383 in chain, failed to locate parent block 000000000000040167c69f7a835d124214316b72d9a9fc2ec2413a238b6ab6da
warning: at depth 6801 in chain, failed to locate parent block 000000000000040167c69f7a835d124214316b72d9a9fc2ec2413a238b6ab6da
warning: at depth 14939 in chain, failed to locate parent block 000000000000040167c69f7a835d124214316b72d9a9fc2ec2413a238b6ab6da

I have to exit with ctrl-c.

I have the same problem with 7.2

[Jouke]

I did a git reset 90a89c0373, but that didn't help.
nm. I am running an extra daemon now.

However:
info: Address cluster for address 16EC7Nx6THDZpGMCavLubbtt2UPXimyUx7:
warning: specified key was never used to spend coins

But it is used in this transaction:
https://blockchain.info/tx/49688f5183b3898d19de3904a09d75d1af52a14edd5f951f371f6823eb22b1f6

[Jouke]

You need to make sure that your local blockchain is up to date.

Hmm, strange, bitcoind getinfo told me it was at up2date.

[SilverLeaf]

Same "Failed to locate parent block..." problem.

Opened a GitHub issue here: https://github.com/znort987/blockparser/issues/1 .

[SilverLeaf]

Your blockchain files are likely corrupted.

Even if they aren't, I do not plan to support old style bitcoind blockchain in the future.

If you want to use blockparser, I would strongly advise moving to a recent version of the bitcoind
client with the levelDB backend (the one that has a directory called "chainstate" in ~/.bitcoin)

Thank you, I am regenerating the blockchain using bootstrap.dat and trying again.

blockparser doesn't support levelDB by now, right?

[SilverLeaf]

Thank you, now it's much more clear.

EDIT: I can confirm that it works with the git version of bitcoind.

[naima53]

Is compatible with version 0.8 bitcoin-qt ?

[Dabs]

Is there a pre-compiled windows version? binary? (which you can of course sign or produce a SHA so us newbies can be sure we have a clean binary.)

[Buffer Overflow]

Blockparser does not run on Windows and other legacy technologies from the 20th Century

LOL 
I couldn't agree more.

[ShadowOfHarbringer]

Is there a pre-compiled windows version? binary? (which you can of course sign or produce a SHA so us newbies can be sure we have a clean binary.)

Blockparser does not run on Windows and other legacy technologies from the 20th Century

Hahahahaha.
Splendid statement, milord.

[codro]

It would be really interesting to see a visualization (graph/chart/printout ) of all the bitcoins being traded in the past couple of years, how many of them (atomically) haven't exchanged hands at all in the past 2 years? Since all coins should be able to be traced back to the moment they were mined, it should be fairly trivial to see how many times and the dates when they were transacted. No?

I think this would be valuable for finding out how much is being hoarded, and how much is in circulation.

I haven't fully looked into this tool yet to see if it can do this, but any pointers would be appreciated.

[Sukrim]

Well, in theory it should be possible to let this run on Windows as well... in practice however I've only managed to compile boost and am still fighting with sparsehash as well as openssl and it's dependencies (openssl wants perl for example).

Sparsehash also seems to really not like to be compiled with MingW... Let's see if I give up and just install a VM on my big machine, because my small Linux Atom nettop probably will choke to death on the hash tables.