How can I tell a new wallet has generated its 100 addresses?

bitlotto

hero member

Activity: 672

Merit: 500

BitLotto - best odds + best payouts + cheat-proof

Quote from: ColdHardMetal on June 23, 2011, 02:57:45 AM

I can't find the thread but there was a guy awhile ago that lost some coins when he was trying to move them to a new wallet. The problem had something to do with the new wallet he made not having generated all of the addresses it was supposed to, or something along those lines.

I'm setting up a wallet on machine I intend to keep unconnected to the web and want to make sure I don't repeat the same mistake. So how can I make sure I'm doing it properly?

Thanks.

That was an old bug. The newest version now creates all the addresses listed during first run. Before 1 was made but the next 99 wouldn't be generated till a transaction was done. If you are worried send a tiny bit to those addresses you are saving to. Once you have a completely up to date block chain with those transactions confirmed save the block chain on a usb stick. You can see the transactions on your offline computer just by copying the block chain over and see if it worked. You don't have to connect to check it!!

goozman96

hero member

Activity: 728

Merit: 500

My recommendation would be to click on the Address Book button in the BitCoin client and count how many receiving addresses you have.

I could be wrong though.

Maged

legendary

Activity: 1204

Merit: 1015

Quote from: ColdHardMetal on June 23, 2011, 02:57:45 AM

... want to make sure I don't repeat the same mistake.

It's simple: Make a backup AFTER you finish the transactions you want, not BEFORE. Assume that a backup is worthless as soon as you use it again, if you plan on deleting your unencrypted wallet. The key pool should only be depended on in emergencies, so only depend on it for the regular backups you make of your spending wallet, NEVER for your savings wallet.

BrianH

sr. member

Activity: 280

Merit: 253

Quote from: casascius on June 23, 2011, 02:59:03 AM

Here is an unofficial observation from me: the wallet file is about 32 kbytes before this happens, and around 90 when it has.

~164k for me. 42MB for a 100,000 address wallet. Cool

kseistrup

hero member

Activity: 566

Merit: 500

Unselfish actions pay back better

Quote from: casascius on June 23, 2011, 02:59:03 AM

It seems to happen when you generate two or three addresses.

Running a getinfo() RPC command seems to be enough…

Cheers,

casascius

vip

Activity: 1386

Merit: 1140

The Casascius 1oz 10BTC Silver Round (w/ Gold B)

Here is an unofficial observation from me: the wallet file is about 32 kbytes before this happens, and around 90 when it has. It seems to happen when you generate two or three addresses. However, I offer no warranty for this observation. Use at your own risk.

ColdHardMetal

hero member

Activity: 700

Merit: 500

I can't find the thread but there was a guy awhile ago that lost some coins when he was trying to move them to a new wallet. The problem had something to do with the new wallet he made not having generated all of the addresses it was supposed to, or something along those lines.

I'm setting up a wallet on machine I intend to keep unconnected to the web and want to make sure I don't repeat the same mistake. So how can I make sure I'm doing it properly?

Thanks.

Topic: How can I tell a new wallet has generated its 100 addresses? (Read 1138 times)