What has it got in its walletses?

[Hal]

I modified the bc_key program originally by dirtyfilthy, to dump out info on everything in the wallet.dat file.

https://github.com/halfinney/bc_key

It prints out keys (as addresses), transaction hashes, key pool addresses, address book names, etc.

Run it as:

./bc_key EVERYTHING ~/.bitcoin/wallet.dat

or wherever your wallet.dat might be. I like to pipe the output through sort.

I've noticed two oddities in the couple of wallets I've looked at:

There are no wkey entries, only keys. wkeys would hold extra stuff with Merkle branches and all that. Is this not yet (or no longer) supported, present in the code for the hypothetical "lightweight client"?

I have a very old wallet, created by the first version of bitcoin. Recently I upgraded to a modern version. However, the wallet has no pool entries. I thought the upgrade would create 100 keypool entries?

[1715008576]

1715008576

[1715008576]

1715008576

[1715008576]

1715008576

[1715008576]

1715008576

[1715008576]

1715008576

[1715008576]

1715008576

[dirtyfilthy]

Good job. Do you happen to know how the blockchain is stored?

[Gavin Andresen]

I have a very old wallet, created by the first version of bitcoin. Recently I upgraded to a modern version. However, the wallet has no pool entries. I thought the upgrade would create 100 keypool entries?

It will create 100 keypool entries the first time you request a new address or if you turn on coin generation (the mining threads each ask the keypool for an address to create the coinbase transactions).

I don't know what the story is with "wkey".

[theymos]

I have a very old wallet, created by the first version of bitcoin.

Impressive that upgrading even worked!

[Hal]

I was scared to upgrade since I had a fair amount of vintage bitcoins in there. But everything seemed ok. I'll play with it some more and see if I can get a key pool.

I was wrong about the wkey, it would mostly add creation and expiration dates, maybe a future feature.

[Mike Hearn]

The block chain file is simply a concatenation of the blocks themselves. The index file then allows you to map transaction IDs into blk00000.dat file offsets.