Bitcoin Forum
May 11, 2024, 02:32:13 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Fastest way to Import Private Keys?  (Read 641 times)
crazylikeafox (OP)
Sr. Member
****
Offline Offline

Activity: 798
Merit: 251



View Profile
November 19, 2012, 03:54:48 PM
 #1

As suggested in the BitCoin Merchant HowTo, I'm playing around with pre-generating several thousand bitcoin addresses.  The problem seems to be importing them.  Even PyWallet only lets you import them into your wallet.dat one at a time.  Is there a decent solution for this?
1715394733
Hero Member
*
Offline Offline

Posts: 1715394733

View Profile Personal Message (Offline)

Ignore
1715394733
Reply with quote  #2

1715394733
Report to moderator
The grue lurks in the darkest places of the earth. Its favorite diet is adventurers, but its insatiable appetite is tempered by its fear of light. No grue has ever been seen by the light of day, and few have survived its fearsome jaws to tell the tale.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1715394733
Hero Member
*
Offline Offline

Posts: 1715394733

View Profile Personal Message (Offline)

Ignore
1715394733
Reply with quote  #2

1715394733
Report to moderator
DeathAndTaxes
Donator
Legendary
*
Offline Offline

Activity: 1218
Merit: 1079


Gerald Davis


View Profile
November 19, 2012, 04:04:07 PM
 #2

Why import them?  Simply set the keypool to a large number (say 2000) and bitcoind will produce them internally. 
You can then bulk export the addresses or just grab a new one in realtime using bitcoind "getnewaddress".

I know it doesn't answer your direct question but it likely is a lot more efficient doing it this way.
crazylikeafox (OP)
Sr. Member
****
Offline Offline

Activity: 798
Merit: 251



View Profile
November 19, 2012, 04:50:59 PM
 #3

Why import them?  Simply set the keypool to a large number (say 2000) and bitcoind will produce them internally. 
You can then bulk export the addresses or just grab a new one in realtime using bitcoind "getnewaddress".

I know it doesn't answer your direct question but it likely is a lot more efficient doing it this way.

OK, that sounds reasonable.  So my understanding is that the keypool is essentially a group of addresses that have been generated by your client but aren't displayed to you in the "receive coins" interface (until you request a new address).  If I export these addresses, and people send coins to some of them, will they be included in my balance on the client even though they aren't displayed in the "receive coins" interface?
DeathAndTaxes
Donator
Legendary
*
Offline Offline

Activity: 1218
Merit: 1079


Gerald Davis


View Profile
November 19, 2012, 05:16:54 PM
 #4

I have have never used it that way so you should probably test it.  Just use pywallet or a tool like that to grab a key from the keypool which hasn't been "used".  Send funds to it and see if the wallet detects it.  I would be surprised if keypool addresses aren't checked for balance/transactions though.  It would cause all kinds of "weirdness" when an old backup is used if it didn't.
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!