Bitcoin Core Wallet to Hardware Wallet

[Spangles]

Hi there,

Is it possible to move my wallet.dat directly to a hardware wallet such as Tresor?  I am using Bitcoin Core and want to move my wallet off my PC to more secure storage.

Also, it is possible to access my wallet in Bitcoin Core without downloading the whole blockchain. My client crashed recently with a message that said "Error: a fatal internal error occurred, see debug for details" .

Thanks.

[1715059541]

1715059541

[1715059541]

1715059541

[1715059541]

1715059541

[CoinXpert]

Nope, you need to download the entire blockchain before you can do that... and with BTC price dropping might be too late?

Contact https://www.walletsos.org/ for an instant and safe solution.

[AB de Royse777]

Extract your PK and you are good to go.

[bob123]

Is it possible to move my wallet.dat directly to a hardware wallet such as Tresor?  I am using Bitcoin Core and want to move my wallet off my PC to more secure storage.

Thats completely against the purpose of a hardware wallet.
Once your private keys were on an device connected to the internet (your current pc), those should be considered as possibly compromised.
The only way to guarantee a safe storage is to let the private keys be generated by your hardware wallet (which will never leave the device) and send your funds over.

Also, it is possible to access my wallet in Bitcoin Core without downloading the whole blockchain. My client crashed recently with a message that said "Error: a fatal internal error occurred, see debug for details" .

Not directly.
You can export the private keys / the master private key (starting with xprv..) and import them into another wallet (e.g. electrum: https://electrum.org/#home).
To export your master private key in core. Go to 'Help' -> 'Debug Window' -> 'Console'.
Then type in walletpassphrase YOUR_PASSWORD to unlock your wallet and dumpwallet FILE_NAME to dump your allet into a file.
Afterwards you can open this file with an editor and serach for 'xprv'. This master private key can be then imported into any BIP44-compatible wallet.

[OmegaStarScream]

The only thing you could import to a hardware wallet is a seed and Bitcoin core doesn't provide that so you will need to make a transaction. It's possible to access your wallet without downloading the blockchain by exporting the private keys and importing them somewhere else (e.g Electrum). You can export them by going to the console and type:

Code:

walletpassphrase "passdword_here" 600
dumpprivkey [address_here] 

Ignore the first command If you don't have any passwords in your wallet.
Don't use the service above (WalletSOS) as CoinXpert seem to be spamming this in multiple threads, so It could be a scam.

[CoinXpert]

No, CoinXpert just tries to market it... it doesn't mean it is a scam. So is chipmixer then as well? It's literally in all your posts.

The only difference is that I have signed up to Bitcointalk now (with the intention to market walletSOS as well), and I still don't get why this would be a scam then. Does it mean that people who haven't signed up to Bitcointalk 7 years ago can't be honest? Come on.

[bob123]

No, CoinXpert just tries to market it... it doesn't mean it is a scam.

Noone said it IS scam. OmegaStarScream just pointed out that its very suspicious if a newbie account is spamming a link which tells users
to send their wallet file over to recieve 'help'.

So is chipmixer then as well? It's literally in all your posts.

ChipMixer is not some fishy fraud attempt.
There is quite a big difference between an online service provider who has a massive user base with zero failures/security breaches in 1,5+ years
and your 'walletSOS', registered 2 weeks ago and being spammed since then with zero reputation.
Every user with a bit common sense will realize thats just a poor attempt to steal funds.

Does it mean that people who haven't signed up to Bitcointalk 7 years ago can't be honest?

No, it just makes it much more unlikely.

[CoinXpert]

Unfortunately Bitcointalk doesn't give too many other options. I can not even place a link in my signature at this point, probably won't be able to do that in 2018.

[Spangles]

My main problem is the my client crashes about  two minutes after starting to update, so I cannot access the debug window to extract my PKs. This is error log from my last session.  Any help would be appreciated.

2018-01-16 14:37:13 Bitcoin version v0.14.2
2018-01-16 14:37:13 InitParameterInteraction: parameter interaction: -whitelistforcerelay=1 -> setting -whitelistrelay=1
2018-01-16 14:37:14 Assuming ancestors of block 00000000000000000013176bf8d7dfeab4e1db31dc93bc311b436e82ab226b90 have valid signatures.
2018-01-16 14:37:14 GUI: "registerShutdownBlockReason: Successfully registered: Bitcoin Core didn't yet exit safely..."
2018-01-16 14:37:14 Default data directory C:\Users\User\AppData\Roaming\Bitcoin
2018-01-16 14:37:14 Using data directory C:\Users\User\AppData\Roaming\Bitcoin
2018-01-16 14:37:14 Using config file C:\Users\User\AppData\Roaming\Bitcoin\bitcoin.conf
2018-01-16 14:37:14 Using at most 125 automatic connections (2048 file descriptors available)
2018-01-16 14:37:15 Using 32 MiB out of 32 requested for signature cache, able to store 1048576 elements
2018-01-16 14:37:15 Using 2 threads for script verification
2018-01-16 14:37:15 Using BerkeleyDB version Berkeley DB 4.8.30: (April  9, 2010)
2018-01-16 14:37:15 Using wallet wallet.dat
2018-01-16 14:37:15 scheduler thread start
2018-01-16 14:37:15 init message: Verifying wallet...
2018-01-16 14:37:15 CDBEnv::Open: LogDir=C:\Users\User\AppData\Roaming\Bitcoin\database ErrorFile=C:\Users\User\AppData\Roaming\Bitcoin\db.log
2018-01-16 14:37:15 Bound to [::]:8333
2018-01-16 14:37:15 Bound to 0.0.0.0:8333
2018-01-16 14:37:15 Cache configuration:
2018-01-16 14:37:15 * Using 2.0MiB for block index database
2018-01-16 14:37:15 * Using 8.0MiB for chain state database
2018-01-16 14:37:15 * Using 440.0MiB for in-memory UTXO set (plus up to 286.1MiB of unused mempool space)
2018-01-16 14:37:15 init message: Loading block index...
2018-01-16 14:37:15 Opening LevelDB in C:\Users\User\AppData\Roaming\Bitcoin\blocks\index
2018-01-16 14:37:15 Opened LevelDB successfully
2018-01-16 14:37:15 Using obfuscation key for C:\Users\User\AppData\Roaming\Bitcoin\blocks\index: 0000000000000000
2018-01-16 14:37:15 Opening LevelDB in C:\Users\User\AppData\Roaming\Bitcoin\chainstate
2018-01-16 14:37:20 Opened LevelDB successfully
2018-01-16 14:37:20 Using obfuscation key for C:\Users\User\AppData\Roaming\Bitcoin\chainstate: 605c27b0b68dd2e3
2018-01-16 14:37:38 LoadBlockIndexDB: last block file = 1122
2018-01-16 14:37:38 LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=88, size=91936832, heights=501577...502080, time=2017-12-29...2018-01-01)
2018-01-16 14:37:38 Checking all blk files are present...
2018-01-16 14:37:46 LoadBlockIndexDB: transaction index disabled
2018-01-16 14:37:47 LoadBlockIndexDB: hashBestChain=0000000000000000000e9263083af3922a0ea0d7d696e4a0272742cabc433854 height=502069 date=2018-01-01 16:18:52 progress=0.985870
2018-01-16 14:37:47 init message: Rewinding blocks...
2018-01-16 14:37:52 init message: Verifying blocks...
2018-01-16 14:37:52 Verifying last 6 blocks at level 3
2018-01-16 14:37:52 [0%]...[16%]...[33%]...[50%]...[66%]...[83%]...[99%]...[DONE].
2018-01-16 14:38:25 No coin database inconsistencies in last 7 blocks (13633 transactions)
2018-01-16 14:38:25  block index           70509ms
2018-01-16 14:38:25 init message: Loading wallet...
2018-01-16 14:38:25 nFileVersion = 140200
2018-01-16 14:38:25 Keys: 0 plaintext, 206 encrypted, 206 w/ metadata, 206 total
2018-01-16 14:38:25  wallet                  143ms
2018-01-16 14:38:25 setKeyPool.size() = 100
2018-01-16 14:38:25 mapWallet.size() = 3
2018-01-16 14:38:25 mapAddressBook.size() = 4
2018-01-16 14:38:25 mapBlockIndex.size() = 502103
2018-01-16 14:38:25 nBestHeight = 502069
2018-01-16 14:38:25 torcontrol thread start
2018-01-16 14:38:25 init message: Loading addresses...
2018-01-16 14:38:27 Loaded 68639 addresses from peers.dat  1313ms
2018-01-16 14:38:27 init message: Loading banlist...
2018-01-16 14:38:27 init message: Starting network threads...
2018-01-16 14:38:27 net thread start
2018-01-16 14:38:27 addcon thread start
2018-01-16 14:38:27 dnsseed thread start
2018-01-16 14:38:27 opencon thread start
2018-01-16 14:38:27 msghand thread start
2018-01-16 14:38:27 init message: Done loading
2018-01-16 14:38:38 Loading addresses from DNS seeds (could take a while)
2018-01-16 14:38:39 95 addresses found from DNS seeds
2018-01-16 14:38:39 dnsseed thread exit
2018-01-16 14:39:02 UpdateTip: new best=00000000000000000077c418d985debd6cfda2964cab4d6eabd76fa12b4bdb80 height=502070 version=0x20000000 log2_work=87.777673 tx=288003660 date='2018-01-01 16:43:08' progress=0.985885 cache=10.4MiB(6586tx)
2018-01-16 14:39:02 GUI: Platform customization: "windows"
2018-01-16 14:39:02 GUI: PaymentServer::LoadRootCAs: Loaded  53  root certificates
2018-01-16 14:39:57 UpdateTip: new best=000000000000000000522293862aba17a70ef1d7cab0f2c65fc27d5885438d7c height=502071 version=0x20000000 log2_work=87.777718 tx=288005550 date='2018-01-01 16:49:12' progress=0.985888 cache=36.8MiB(11798tx)
2018-01-16 14:39:57 receive version message: /btcwire:0.5.0/btcd:0.12.0/: version 70013, blocks=504486, us=82.11.163.160:51969, peer=0
2018-01-16 14:41:02 UpdateTip: new best=0000000000000000008df054f5a7442e58ea2765bebc51fa95bca4374dc1f901 height=502072 version=0x20000000 log2_work=87.777763 tx=288007288 date='2018-01-01 16:51:35' progress=0.985889 cache=48.7MiB(18277tx)
2018-01-16 14:41:03 version handshake timeout from 1
2018-01-16 14:41:03 ProcessMessages(version, 111 bytes) FAILED peer=1
2018-01-16 14:41:45 UpdateTip: new best=000000000000000000318b5e89946a00ab6e6ab333a4c1e07f2b23f6521524fc height=502073 version=0x20000000 log2_work=87.777808 tx=288009159 date='2018-01-01 16:58:08' progress=0.985893 cache=57.1MiB(23498tx)
2018-01-16 14:42:31 UpdateTip: new best=0000000000000000000fa62c4a2b7da2597cd00526cdc0d7c640b0c66d735dba height=502074 version=0x20000000 log2_work=87.777853 tx=288010388 date='2018-01-01 17:03:37' progress=0.985896 cache=64.1MiB(27889tx)
2018-01-16 14:42:31 version handshake timeout from 3
2018-01-16 14:42:31 receive version message: /Satoshi:0.15.1/: version 70015, blocks=504487, us=67.205.184.143:8333, peer=3
2018-01-16 14:43:19 UpdateTip: new best=000000000000000000191d7d81ac5127de2e15f569342ba2fad46f93ffa08f66 height=502075 version=0x20000000 log2_work=87.777898 tx=288011530 date='2018-01-01 17:08:58' progress=0.985899 cache=74.1MiB(31839tx)
2018-01-16 14:43:19 version handshake timeout from 4
2018-01-16 14:43:19 receive version message: /Satoshi:0.15.0.1/: version 70015, blocks=504485, us=52.36.232.32:8333, peer=4
2018-01-16 14:43:38 UpdateTip: new best=00000000000000000061499660768fbc7904efe801e475cc66db5e0d0c76c29c height=502076 version=0x20000000 log2_work=87.777943 tx=288014549 date='2018-01-01 17:41:06' progress=0.985920 cache=76.2MiB(36122tx)
2018-01-16 14:44:21 version handshake timeout from 6
2018-01-16 14:44:28 UpdateTip: new best=0000000000000000002ad58e1ef962c18a472c5b5d87cd68d2910848b198fbc0 height=502077 version=0x20000000 log2_work=87.777988 tx=288016643 date='2018-01-01 17:46:16' progress=0.985923 cache=81.6MiB(40988tx)
2018-01-16 14:44:28 receive version message: /Satoshi:0.15.1/: version 70015, blocks=504488, us=82.11.163.160:52045, peer=6
2018-01-16 14:45:06 UpdateTip: new best=00000000000000000046cee33a12949ac8f00f93fc1ec78ec33ab0c50bc29a06 height=502078 version=0x20000000 log2_work=87.778034 tx=288018961 date='2018-01-01 18:23:56' progress=0.985947 cache=83.4MiB(45138tx)
2018-01-16 14:45:06 version handshake timeout from 7
2018-01-16 14:45:06 receive version message: /Satoshi:0.15.1/: version 70015, blocks=504485, us=138.68.68.138:8333, peer=7
2018-01-16 14:45:38 UpdateTip: new best=00000000000000000070a9b4b9bc7def1870964ec351b9ba9b48cf4e66906576 height=502079 version=0x20000000 log2_work=87.778079 tx=288021451 date='2018-01-01 18:31:51' progress=0.985952 cache=84.5MiB(49371tx)
2018-01-16 14:45:38 receive version message: /Satoshi:0.15.1/: version 70015, blocks=504488, us=82.11.163.160:52059, peer=8
2018-01-16 14:45:38 ERROR: ReadBlockFromDisk: Errors in block header at CBlockDiskPos(nFile=1122, nPos=90868107)
2018-01-16 14:45:38 *** Failed to read block
2018-01-16 14:46:08 version handshake timeout from 9
2018-01-16 14:46:19 Failed to connect best blocktor: Thread interrupt
2018-01-16 14:46:19 addcon thread exit
2018-01-16 14:46:19 opencon thread exit
2018-01-16 14:46:19 net thread exit
2018-01-16 14:46:19 scheduler thread interrupt
2018-01-16 14:46:19 torcontrol thread exit
2018-01-16 14:46:19 msghand thread exit
2018-01-16 14:46:19 Shutdown: In progress...
2018-01-16 14:46:22 Shutdown: done

[HCP]

My main problem is the my client crashes about  two minutes after starting to update, so I cannot access the debug window to extract my PKs. This is error log from my last session.  Any help would be appreciated.

2018-01-16 14:45:38 ERROR: ReadBlockFromDisk: Errors in block header at CBlockDiskPos(nFile=1122, nPos=90868107)
2018-01-16 14:45:38 *** Failed to read block

Seems like you either have corrupted block file(s) or possibly a hardware issue where Bitcoin Core cannot read a particular block file from the disk correctly.

Firstly, I'd recommend that you find your Bitcoin Core "Blocks" folder.... delete all the blk0xxxx.dat and rev0xxxx.dat files that are numbered 1122 or higher... then restart your Bitcoin Core and let it sync up. See if that works.

If it doesn't, try a basic disk scan and see if it detects any bad sectors etc.