Topic: Best client for importing multiple private keys? - page 2. (Read 8398 times)
ahh.. no no. I need to import them into Bitcoin Core wallet.dat. Because it's going to run on a server as a full node.
I would personally recommend Electrum , really easy to do what you asking for . but know that imported keys are not recoverable from seed
Sorry for the necro-bump, but is there a way to bulk import a few thousand keys into an encrypted wallet.dat (Bitcoin Core wallet, version 0.9.3)?
What I'm trying to do:
1. brand new wallet.dat (I call it empty.dat)
2. encrypt it with crazy long password
3. import keys using bitcoin-cli / bitcoind
However, I need to import a few thousand keys.
What I'm trying to do:
1. brand new wallet.dat (I call it empty.dat)
2. encrypt it with crazy long password
3. import keys using bitcoin-cli / bitcoind
However, I need to import a few thousand keys.
I solved this problem just the other day with Multibit. You can work with everything in .csv format and edit the file in Excel.
Sorry for the necro-bump, but is there a way to bulk import a few thousand keys into an encrypted wallet.dat (Bitcoin Core wallet, version 0.9.3)?
What I'm trying to do:
1. brand new wallet.dat (I call it empty.dat)
2. encrypt it with crazy long password
3. import keys using bitcoin-cli / bitcoind
However, I need to import a few thousand keys.
What I'm trying to do:
1. brand new wallet.dat (I call it empty.dat)
2. encrypt it with crazy long password
3. import keys using bitcoin-cli / bitcoind
However, I need to import a few thousand keys.
try Mycelium. we specifically support this usecase. With the cold storage spend wizard one keysweep takes about 10 seconds.
see this video demonstration: https://www.youtube.com/watch?v=1pDSzOiFgIk
if you want to import keys in bulk, you can have up to 10 keys imported in the "active" section at once and send 1 transaction from those keys.
see this video demonstration: https://www.youtube.com/watch?v=1pDSzOiFgIk
if you want to import keys in bulk, you can have up to 10 keys imported in the "active" section at once and send 1 transaction from those keys.
In that case, don't bother importing or deleting. Just use the raw transaction API to create, sign and send the transaction.
Agreed.
Don't import private keys. That is far too slow. Just use them to sign raw transactions.
Can anyone point to any howtos for something like this?
In that case, don't bother importing or deleting. Just use the raw transaction API to create, sign and send the transaction.
Agreed.
Don't import private keys. That is far too slow. Just use them to sign raw transactions.
In that case, don't bother importing or deleting. Just use the raw transaction API to create, sign and send the transaction.
Dare I ask why you are deleting the key?
Are you really that sure that no one will re-use one?
Are you really that sure that no one will re-use one?
The private keys will still be available in cold storage.
Dare I ask why you are deleting the key?
Are you really that sure that no one will re-use one?
Are you really that sure that no one will re-use one?
I'm going to go with armory on this one.
Electrum is much easy. Import private key, send funds, freeze that key, import new one, and repeat the process. Or simply import all keys at once.
But that's not automated.
But that's not automated.
I am looking to automate a process of importing a private key to a client, send a certain amount from the client then delete the private key before moving on to the next private key.
Currently I am figuring I can set up a fresh wallet.dat, import a private key and send the BTC, then overwrite the wallet.dat with a copy of the fresh wallet.dat.
There should be a better way.
Currently I am figuring I can set up a fresh wallet.dat, import a private key and send the BTC, then overwrite the wallet.dat with a copy of the fresh wallet.dat.
There should be a better way.
bitcoind with proper scripting will do it.
I am looking to automate a process of importing a private key to a client, send a certain amount from the client then delete the private key before moving on to the next private key.
Currently I am figuring I can set up a fresh wallet.dat, import a private key and send the BTC, then overwrite the wallet.dat with a copy of the fresh wallet.dat.
There should be a better way.
Currently I am figuring I can set up a fresh wallet.dat, import a private key and send the BTC, then overwrite the wallet.dat with a copy of the fresh wallet.dat.
There should be a better way.
Jump to: