wallet.dat backwards incompatibility in 0.15.1 version

[MysteryMiner]

I decided to sweep the pocket change from my old wallet.dat files. One wallet.dat file that I created with 0.23.1 version of Bitcoin and last used with 0.4.x or 0.5.x version worked perfectly when pasted in 0.15.1 64-bit version data directory. But I have problem with wallet.dat created with 0.6.x or 0.7.x version in late 2013 or first half of 2014 and last used in first half of year 2015. Version 0.10.1 32-bit opens and runs it fine. Version 0.14.2 64-bit opens and runs fine, but throws out error when shutting down Bitcoin Core. Version 0.15.1 throws out error when starting up and is unusable.

Code:

EXCEPTION: St13runtime_error       
GenerateNewKey: AddKey failed       
C:\Program Files\Bitcoin\bitcoin-qt.exe in Runaway exception       

2018-02-10 11:10:28 CDBEnv::EnvShutdown: Error -30974 shutting down database environment: DB_RUNRECOVERY: Fatal error, run database recovery

So far I think my workaround for this situation will be using 0.14.2 to sync and send the coins.

[1714139885]

1714139885

[1714139885]

1714139885

[1714139885]

1714139885

[1714139885]

1714139885

[1714139885]

1714139885

[ranochigo]

Can you try starting Bitcoin Core with -upgradewallet for the wallet in question?
ie. run CMD and paste the following inside.

Code:

 C:\Program Files\Bitcoin\bitcoin-qt.exe -upgradewallet

Can you also post the full debug.log either publicly or privately to me?

[MysteryMiner]

Here is debug.log contents. Installed Bitcoin Core 0.15.1 and started it up. Set the options and edited bitcoin.conf to add pruning. Then closed, replaced wallet.dat with problematic one and started Bitcoin-qt.exe with -upgradewallet option. Gave me the same error.

Code:

2018-02-10 11:59:52 



















2018-02-10 11:59:52 Bitcoin version v0.15.1
2018-02-10 11:59:52 InitParameterInteraction: parameter interaction: -whitelistforcerelay=1 -> setting -whitelistrelay=1
2018-02-10 11:59:52 Assuming ancestors of block 0000000000000000003b9ce759c2a087d52abc4266f8f4ebd6d768b89defa50a have valid signatures.
2018-02-10 11:59:52 Setting nMinimumChainWork=000000000000000000000000000000000000000000723d3581fe1bd55373540a
2018-02-10 11:59:52 Using the 'standard' SHA256 implementation
2018-02-10 11:59:52 Using RdRand as an additional entropy source
2018-02-10 11:59:53 GUI: "registerShutdownBlockReason: Successfully registered: Bitcoin Core didn't yet exit safely..."
2018-02-10 11:59:53 Default data directory C:\Users\Admin\AppData\Roaming\Bitcoin
2018-02-10 11:59:53 Using data directory C:\Users\Admin\AppData\Roaming\Bitcoin
2018-02-10 11:59:53 Using config file C:\Users\Admin\AppData\Roaming\Bitcoin\bitcoin.conf
2018-02-10 11:59:53 Using at most 125 automatic connections (2048 file descriptors available)
2018-02-10 11:59:53 Using 16 MiB out of 32/2 requested for signature cache, able to store 524288 elements
2018-02-10 11:59:53 Using 16 MiB out of 32/2 requested for script execution cache, able to store 524288 elements
2018-02-10 11:59:53 Using 0 threads for script verification
2018-02-10 11:59:53 init message: Verifying wallet(s)...
2018-02-10 11:59:53 Using BerkeleyDB version Berkeley DB 4.8.30: (April  9, 2010)
2018-02-10 11:59:53 Using wallet wallet.dat
2018-02-10 11:59:53 CDBEnv::Open: LogDir=C:\Users\Admin\AppData\Roaming\Bitcoin\database ErrorFile=C:\Users\Admin\AppData\Roaming\Bitcoin\db.log
2018-02-10 11:59:53 Cache configuration:
2018-02-10 11:59:53 * Using 2.0MiB for block index database
2018-02-10 11:59:53 * Using 8.0MiB for chain state database
2018-02-10 11:59:53 * Using 440.0MiB for in-memory UTXO set (plus up to 286.1MiB of unused mempool space)
2018-02-10 11:59:53 init message: Ielādē bloku indeksu...
2018-02-10 11:59:53 Opening LevelDB in C:\Users\Admin\AppData\Roaming\Bitcoin\blocks\index
2018-02-10 11:59:53 scheduler thread start
2018-02-10 11:59:53 Opened LevelDB successfully
2018-02-10 11:59:53 Using obfuscation key for C:\Users\Admin\AppData\Roaming\Bitcoin\blocks\index: 0000000000000000
2018-02-10 11:59:53 LoadBlockIndexDB: last block file = 0
2018-02-10 11:59:53 LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=0, size=0, heights=0...0, time=1970-01-01...1970-01-01)
2018-02-10 11:59:53 Checking all blk files are present...
2018-02-10 11:59:53 LoadBlockIndexDB: transaction index disabled
2018-02-10 11:59:53 Initializing databases...
2018-02-10 11:59:53 Pre-allocating up to position 0x1000000 in blk00000.dat
2018-02-10 11:59:53 Opening LevelDB in C:\Users\Admin\AppData\Roaming\Bitcoin\chainstate
2018-02-10 11:59:53 Opened LevelDB successfully
2018-02-10 11:59:53 Wrote new obfuscate key for C:\Users\Admin\AppData\Roaming\Bitcoin\chainstate: 8ccea2ae22e7c058
2018-02-10 11:59:53 Using obfuscation key for C:\Users\Admin\AppData\Roaming\Bitcoin\chainstate: 8ccea2ae22e7c058
2018-02-10 11:59:53 init message: Rewinding blocks...
2018-02-10 11:59:53  block index               3ms
2018-02-10 11:59:53 init message: Ielādē maciņu...
2018-02-10 11:59:53 nFileVersion = 150100
2018-02-10 11:59:53 Keys: 0 plaintext, 0 encrypted, 0 w/ metadata, 0 total
2018-02-10 11:59:53 Performing wallet upgrade to 60000
2018-02-10 11:59:54 keypool added 2000 keys (1000 internal), size=2000 (1000 internal)
2018-02-10 11:59:54 keypool reserve 1
2018-02-10 11:59:54 keypool keep 1
2018-02-10 11:59:54  wallet                 1139ms
2018-02-10 11:59:54 keypool added 1 keys (0 internal), size=2000 (1000 internal)
2018-02-10 11:59:54 setKeyPool.size() = 2000
2018-02-10 11:59:54 mapWallet.size() = 0
2018-02-10 11:59:54 mapAddressBook.size() = 1
2018-02-10 11:59:54 UpdateTip: new best=000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f height=0 version=0x00000001 log2_work=32.000022 tx=1 date='2009-01-03 18:15:05' progress=0.000000 cache=0.0MiB(0txo)
2018-02-10 11:59:54 mapBlockIndex.size() = 1
2018-02-10 11:59:54 nBestHeight = 0
2018-02-10 11:59:54 Failed to open mempool file from disk. Continuing anyway.
2018-02-10 11:59:54 torcontrol thread start
2018-02-10 11:59:54 Bound to [::]:8333
2018-02-10 11:59:54 Bound to 0.0.0.0:8333
2018-02-10 11:59:54 init message: Loading P2P addresses...
2018-02-10 11:59:54 ERROR: DeserializeFileDB: Failed to open file C:\Users\Admin\AppData\Roaming\Bitcoin\peers.dat
2018-02-10 11:59:54 Invalid or missing peers.dat; recreating
2018-02-10 11:59:54 init message: Loading banlist...
2018-02-10 11:59:54 ERROR: DeserializeFileDB: Failed to open file C:\Users\Admin\AppData\Roaming\Bitcoin\banlist.dat
2018-02-10 11:59:54 Invalid or missing banlist.dat; recreating
2018-02-10 11:59:54 init message: Starting network threads...
2018-02-10 11:59:54 net thread start
2018-02-10 11:59:54 dnsseed thread start
2018-02-10 11:59:54 Loading addresses from DNS seeds (could take a while)
2018-02-10 11:59:54 addcon thread start
2018-02-10 11:59:54 opencon thread start
2018-02-10 11:59:54 msghand thread start
2018-02-10 11:59:54 init message: Ielāde pabeigta
2018-02-10 11:59:54 GUI: Platform customization: "windows"
2018-02-10 11:59:54 GUI: PaymentServer::LoadRootCAs: Loaded  8  root certificates
2018-02-10 11:59:56 receive version message: /Satoshi:0.14.2/: version 70015, blocks=508507, us=212.3.196.61:49166, peer=0
2018-02-10 11:59:57 receive version message: /Satoshi:0.15.1/: version 70015, blocks=508507, us=212.3.196.61:49168, peer=1
2018-02-10 11:59:58 receive version message: /Satoshi:0.16.0/: version 70015, blocks=508507, us=212.3.196.61:49169, peer=2
2018-02-10 11:59:59 138 addresses found from DNS seeds
2018-02-10 11:59:59 dnsseed thread exit
2018-02-10 12:00:02 GUI:   OpenType support missing for script 12
2018-02-10 12:00:02 GUI:   OpenType support missing for script 12
2018-02-10 12:00:02 GUI:   OpenType support missing for script 12
2018-02-10 12:00:02 GUI:   OpenType support missing for script 12
2018-02-10 12:00:02 GUI:   OpenType support missing for script 12
2018-02-10 12:00:02 GUI:   OpenType support missing for script 12
2018-02-10 12:00:02 GUI:   OpenType support missing for script 12
2018-02-10 12:00:02 GUI:   OpenType support missing for script 12
2018-02-10 12:00:02 GUI:   OpenType support missing for script 12
2018-02-10 12:00:02 GUI:   OpenType support missing for script 11
2018-02-10 12:00:02 GUI:   OpenType support missing for script 11
2018-02-10 12:00:02 GUI:   OpenType support missing for script 11
2018-02-10 12:00:02 GUI:   OpenType support missing for script 11
2018-02-10 12:00:02 GUI:   OpenType support missing for script 11
2018-02-10 12:00:02 GUI:   OpenType support missing for script 11
2018-02-10 12:00:02 GUI:   OpenType support missing for script 11
2018-02-10 12:00:02 GUI:   OpenType support missing for script 20
2018-02-10 12:00:02 GUI:   OpenType support missing for script 20
2018-02-10 12:00:02 GUI:   OpenType support missing for script 20
2018-02-10 12:00:02 GUI:   OpenType support missing for script 20
2018-02-10 12:00:02 GUI:   OpenType support missing for script 20
2018-02-10 12:00:02 GUI:   OpenType support missing for script 20
2018-02-10 12:00:02 GUI:   OpenType support missing for script 20
2018-02-10 12:00:02 GUI:   OpenType support missing for script 16
2018-02-10 12:00:02 GUI:   OpenType support missing for script 16
2018-02-10 12:00:02 GUI:   OpenType support missing for script 16
2018-02-10 12:00:02 GUI:   OpenType support missing for script 16
2018-02-10 12:00:02 GUI:   OpenType support missing for script 16
2018-02-10 12:00:02 GUI:   OpenType support missing for script 16
2018-02-10 12:00:02 GUI:   OpenType support missing for script 16
2018-02-10 12:00:02 GUI:   OpenType support missing for script 17
2018-02-10 12:00:02 GUI:   OpenType support missing for script 17
2018-02-10 12:00:02 GUI:   OpenType support missing for script 17
2018-02-10 12:00:02 GUI:   OpenType support missing for script 17
2018-02-10 12:00:02 GUI:   OpenType support missing for script 17
2018-02-10 12:00:02 GUI:   OpenType support missing for script 17
2018-02-10 12:00:02 GUI:   OpenType support missing for script 17
2018-02-10 12:00:28 ProcessMessages(version, 113 bytes) FAILED peer=3
2018-02-10 12:00:43 upnp thread start
2018-02-10 12:00:45 No valid UPnP IGDs found
2018-02-10 12:00:45 upnp thread exit
2018-02-10 12:00:46 tor: Thread interrupt
2018-02-10 12:00:46 net thread exit
2018-02-10 12:00:46 torcontrol thread exit
2018-02-10 12:00:46 scheduler thread interrupt
2018-02-10 12:00:46 Shutdown: In progress...
2018-02-10 12:00:46 addcon thread exit
2018-02-10 12:00:46 msghand thread exit
2018-02-10 12:00:47 opencon thread exit
2018-02-10 12:00:47 Dumped mempool: 0s to copy, 0s to dump
2018-02-10 12:00:48 Shutdown: done
2018-02-10 12:02:20 



















2018-02-10 12:02:20 Bitcoin version v0.15.1
2018-02-10 12:02:20 InitParameterInteraction: parameter interaction: -whitelistforcerelay=1 -> setting -whitelistrelay=1
2018-02-10 12:02:20 Assuming ancestors of block 0000000000000000003b9ce759c2a087d52abc4266f8f4ebd6d768b89defa50a have valid signatures.
2018-02-10 12:02:20 Setting nMinimumChainWork=000000000000000000000000000000000000000000723d3581fe1bd55373540a
2018-02-10 12:02:20 Prune configured to target 4096MiB on disk for block and undo files.
2018-02-10 12:02:20 Using the 'standard' SHA256 implementation
2018-02-10 12:02:20 Using RdRand as an additional entropy source
2018-02-10 12:02:21 GUI: "registerShutdownBlockReason: Successfully registered: Bitcoin Core didn't yet exit safely..."
2018-02-10 12:02:21 Default data directory C:\Users\Admin\AppData\Roaming\Bitcoin
2018-02-10 12:02:21 Using data directory C:\Users\Admin\AppData\Roaming\Bitcoin
2018-02-10 12:02:21 Using config file C:\Users\Admin\AppData\Roaming\Bitcoin\bitcoin.conf
2018-02-10 12:02:21 Using at most 125 automatic connections (2048 file descriptors available)
2018-02-10 12:02:21 Using 16 MiB out of 32/2 requested for signature cache, able to store 524288 elements
2018-02-10 12:02:21 Using 16 MiB out of 32/2 requested for script execution cache, able to store 524288 elements
2018-02-10 12:02:21 Using 0 threads for script verification
2018-02-10 12:02:21 init message: Verifying wallet(s)...
2018-02-10 12:02:21 Using BerkeleyDB version Berkeley DB 4.8.30: (April  9, 2010)
2018-02-10 12:02:21 Using wallet wallet.dat
2018-02-10 12:02:21 CDBEnv::Open: LogDir=C:\Users\Admin\AppData\Roaming\Bitcoin\database ErrorFile=C:\Users\Admin\AppData\Roaming\Bitcoin\db.log
2018-02-10 12:02:21 Cache configuration:
2018-02-10 12:02:21 * Using 2.0MiB for block index database
2018-02-10 12:02:21 * Using 8.0MiB for chain state database
2018-02-10 12:02:21 * Using 440.0MiB for in-memory UTXO set (plus up to 286.1MiB of unused mempool space)
2018-02-10 12:02:21 init message: Loading block index...
2018-02-10 12:02:21 Opening LevelDB in C:\Users\Admin\AppData\Roaming\Bitcoin\blocks\index
2018-02-10 12:02:21 scheduler thread start
2018-02-10 12:02:22 Opened LevelDB successfully
2018-02-10 12:02:22 Using obfuscation key for C:\Users\Admin\AppData\Roaming\Bitcoin\blocks\index: 0000000000000000
2018-02-10 12:02:24 LoadBlockIndexDB: last block file = 0
2018-02-10 12:02:24 LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=1, size=293, heights=0...0, time=2009-01-03...2009-01-03)
2018-02-10 12:02:24 Checking all blk files are present...
2018-02-10 12:02:24 LoadBlockIndexDB: transaction index disabled
2018-02-10 12:02:24 Opening LevelDB in C:\Users\Admin\AppData\Roaming\Bitcoin\chainstate
2018-02-10 12:02:24 Opened LevelDB successfully
2018-02-10 12:02:24 Using obfuscation key for C:\Users\Admin\AppData\Roaming\Bitcoin\chainstate: 8ccea2ae22e7c058
2018-02-10 12:02:24 Loaded best chain: hashBestChain=000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f height=0 date=2009-01-03 18:15:05 progress=0.000000
2018-02-10 12:02:24 init message: Rewinding blocks...
2018-02-10 12:02:24 init message: Verifying blocks...
2018-02-10 12:02:24  block index            2855ms
2018-02-10 12:02:24 init message: Loading wallet...
2018-02-10 12:02:24 nFileVersion = 90300
2018-02-10 12:02:24 Keys: 104 plaintext, 0 encrypted, 0 w/ metadata, 104 total
2018-02-10 12:02:24 Performing wallet upgrade to 60000
2018-02-10 12:02:24  wallet                   31ms
2018-02-10 12:02:24 

************************
EXCEPTION: St13runtime_error       
GenerateNewKey: AddKey failed       
C:\Program Files\Bitcoin\bitcoin-qt.exe in Runaway exception       

2018-02-10 12:02:30 CDBEnv::EnvShutdown: Error -30974 shutting down database environment: DB_RUNRECOVERY: Fatal error, run database recovery

[MysteryMiner]

Additional info about this wallet.dat file. It was running with command line option to disable last blocks check upon startup or with reduced count of last blocks check. It was due to default option taking from 45minutes to 1 hour to start Bitcoin Core on old computer. I do not remember what the command line option was back then and the bitcoin.conf from that setup is gone long ago.

edit: db.log contents. Seems like it thinks wallet.dat is corrupted. But the Bitcoin-Qt version used back then did not consider it to be corrupted and also I took great care to backup this wallet.dat when the node is properly shut down.

Code:

file wallet.dat has LSN 1/4211, past end of log at 1/333
Commonly caused by moving a database from one database environment
to another without clearing the database LSNs, or by removing all of
the log files from a database environment
DB_ENV->log_flush: LSN of 1/4211 past current end-of-log of 1/333
Database environment corrupt; the wrong log files may have been removed or incompatible database files imported from another environment
PANIC: DB_RUNRECOVERY: Fatal error, run database recovery
wallet.dat: unable to flush page: 10
txn_checkpoint: failed to flush the buffer cache: DB_RUNRECOVERY: Fatal error, run database recovery
PANIC: fatal region error detected; run recovery
PANIC: fatal region error detected; run recovery
File handles still open at environment close
Open file handle: C:\Users\Admin\AppData\Roaming\Bitcoin\wallet.dat
Open file handle: C:\Users\Admin\AppData\Roaming\Bitcoin\database\log.0000000001
PANIC: fatal region error detected; run recovery

[AB de Royse777]

Correct my if i'm wrong but isn't it easier to use a python script to just extract the PK's? There are some scripts build especially for that.... or am i missing something here?

[MysteryMiner]

Correct my if i'm wrong but isn't it easier to use a python script to just extract the PK's? There are some scripts build especially for that.... or am i missing something here?

This is unexpected behavior in the client and it must be fixed. It is clearly some sort of bug, since even older wallet.dat runs without slightest problems. I can use recovery tools on this wallet.dat, but it will be just like repairing teeth trough anus. I will get my coins anyway with older version, I just want to help sorting out what is wrong.

[AB de Royse777]

Correct my if i'm wrong but isn't it easier to use a python script to just extract the PK's? There are some scripts build especially for that.... or am i missing something here?

This is unexpected behavior in the client and it must be fixed. It is clearly some sort of bug, since even older wallet.dat runs without slightest problems. I can use recovery tools on this wallet.dat, but it will be just like repairing teeth trough anus. I will get my coins anyway with older version, I just want to help sorting out what is wrong.

Point taken... Amazing analogy by the way 

[DrSha]

Following steps might help you dump the pk from the wallet:

1    Start Bitcoin Core
2    Stop Bitcoin Core
3    Datadir should be created, open the datadir folder (https://en.bitcoin.it/wiki/Data_directory)
4    Replace the existing wallet.dat (backup it if you already had Bitcoin Core installed) with your old wallet
5    Start Bitcoin Core
6    If you want to export your keys, open the debug console and type dumpwallet <filename>

edit : just noticed the new post above.. this may not be the solution you require.

[MysteryMiner]

Following steps might help you dump the pk from the wallet:

1    Start Bitcoin Core
2    Stop Bitcoin Core
3    Datadir should be created, open the datadir folder (https://en.bitcoin.it/wiki/Data_directory)
4    Replace the existing wallet.dat (backup it if you already had Bitcoin Core installed) with your old wallet
5    Start Bitcoin Core
6    If you want to export your keys, open the debug console and type dumpwallet <filename>

Sorry, but You did not read the thread properly. After Step 5. the Bitcoin Core crashes and it is over. Also I do not need tips on recovery, I am syncing the wallet in question with 0.14.2 version as I write this. This is thread about possible problems either with Bitcoin Core or particular wallet.dat file. If the wallet.dat does not contain history of some of my illegal activities, I will post it publicly for examination after moving coins away from it.

[DrSha]

From the log posted above there you could remove the chains folder and re-download or the other issue may be that it was built with another version of berkeley db.

This may be why reason :  CDBEnv::EnvShutdown: Error -30974 shutting down database environment:

Try remove the chains folder and re-download.

You can also try the built with --with-incompatible-bdb option

[MysteryMiner]

Update. 0.14.2 version also have problems. It appears that wallet.dat have problems, but 0.15.1 does throw error straight away. Added last entries from debug.log

Code:

2018-02-10 16:56:58 UpdateTip: new best=00000000000001590c53c7be3e40f01c0ef9cb1900a300bdad19e1078d1d66f4 height=206842 version=0x00000001 log2_work=68.983027 tx=8659530 date='2012-11-07 08:19:28' progress=0.029266 cache=194.8MiB(570029tx)
2018-02-10 16:56:58 Pre-allocating up to position 0x400000 in rev00028.dat
2018-02-10 16:57:00 Prune: UnlinkPrunedFiles deleted blk/rev (00000)
2018-02-10 16:57:03 *** System error while flushing: CDB: Error -30974, can't open database wallet.dat
2018-02-10 16:57:31 ERROR: ProcessNewBlock: ActivateBestChain failed
2018-02-10 16:57:31 tor: Thread interrupt
2018-02-10 16:57:31 addcon thread exit
2018-02-10 16:57:31 torcontrol thread exit
2018-02-10 16:57:31 msghand thread exit
2018-02-10 16:57:31 scheduler thread interrupt
2018-02-10 16:57:31 Shutdown: In progress...
2018-02-10 16:57:31 net thread exit
2018-02-10 16:57:33 opencon thread exit
2018-02-10 16:57:33 Dumped mempool: 0s to copy, 0s to dump
2018-02-10 16:57:33 *** System error while flushing: CDB: Error -30974, can't open database wallet.dat
2018-02-10 16:57:35 CDBEnv::EnvShutdown: Error -30974 shutting down database environment: DB_RUNRECOVERY: Fatal error, run database recovery
2018-02-10 16:57:35 Shutdown: done

[bob123]

Is there a specific reason to use core to access those private keys?
If not, you can use pywallet [1].

According to your statement:

Python is modern day version of 90ties Visual Basic.

you might not want to use python (because of whatever reason).


But as i already awnsered in the other thread this statement is rubbish. This is probably the fastest way of accessing all of your private keys.
Pywallet should work with all versions of wallet.dat. You might try that out. Afterwards you could simply import those private key into a newly generated wallet in core.


[1] https://github.com/jackjack-jj/pywallet

[achow101]

Your wallet is corrupted, kind of. I have seen this behavior before in other wallets and, if the problem is what I think it is, it has been fixed in Bitcoin Core 0.16.0.

Try using Bitcoin Core 0.16.0rc3 available from here: https://bitcoincore.org/bin/bitcoin-core-0.16.0/test.rc3/


If this does not work, make a backup of your wallet and try starting Bitcoin Core with the -salvagewallet option.

[MysteryMiner]

Is there a specific reason to use core to access those private keys?

Not really. I just want to know what is wrong. I am curious.

If not, you can use pywallet

I have used pywallet in past and will use it eventually on this wallet in question.

Your wallet is corrupted, kind of. I have seen this behavior before in other wallets and, if the problem is what I think it is, it has been fixed in Bitcoin Core 0.16.0.

Try using Bitcoin Core 0.16.0rc3 available from here: https://bitcoincore.org/bin/bitcoin-core-0.16.0/test.rc3/


If this does not work, make a backup of your wallet and try starting Bitcoin Core with the -salvagewallet option.

I was not here for long time. I hope bitcoincore.org is not just another scam site similar to Bitcoin Crash bitcoincash.com or another scamfork. As for now, the binaries appear to be signed with Bitcoin Foundation key. Will try Bitcoin Core 0.16.0 Research Chemical 3

[achow101]

I was not here for long time. I hope bitcoincore.org is not just another scam site

Bitcoincore.org is Bitcoin Core's official site. W're moving away from using bitcoin.org for Bitcoin Core. You can check that SHA256SUMS.asc is signed with Wladimir's release key which can be found here, here, and here (it's the same key in 3 difference places). Also bitcoincore.org is stated as the new Bitcoin Core website on bitcoin.org's Bitcoin Core page.

Will try Bitcoin Core 0.16.0 Research Chemical 3

RC stands for Release Candidate 

[MysteryMiner]

Bitcoincore.org is Bitcoin Core's official site. W're moving away from using bitcoin.org for Bitcoin Core. You can check that SHA256SUMS.asc is signed with Wladimir's release key which can be found here, here, and here (it's the same key in 3 difference places). Also bitcoincore.org is stated as the new Bitcoin Core website on bitcoin.org's Bitcoin Core page.

I checked the site and it is legit. But I think it is stupid to separate into many different domains. Eventually you lose access to one of them and it is used as attack vector to spread fun. Even large corporations fall to this. Using subdomains I think was how it all was intended. Also I do not like that Bitcoin Core in named in honor of Intel processors. It should be named after AMD or even better called simply Bitcoin or when needed to specify called Satoshi's Bitcoin or reference Bitcoin client.

RC stands for Release Candidate

I know but when taking into account Bitcoin's main usage as deep web drug trade enabler, Research Chemical is more fitting description. Also, just like IRL Reserach Chemical, using RC version can lead to unexpected consequences.

edit: 0.16.0 RC3 also crashes upon startup.

[bob123]

I know but when taking into account Bitcoin's main usage as deep web drug trade enabler...

That was a joke, am i right?
Bitcoin is by far not the best crypto currency (still better than any other 'standard' blockchain currency) for illegal activites.
Bitcoin addresses used on silk road 6 years ago can still be traced. There has been a study released where researcher found a
coherence between those addresses used on silk road and transactions tied to their real identity.

The only way to stay fully anonymous while purchasing any illegal stuff is to either
1) Use a coin tumbler (https://chipmixer.com/) or
2) use monero

But with 70%+ hashrate of monero being held by botnets.. that might be the more risky option.

[MysteryMiner]

After messing around I come to this conclusion. The wallet.dat somehow got corrupted and newer Bicoin Core versions have problem when trying to use it. The solution was to run bitcoin-qt.exe with -salvagewallet option. It created new High Definition wallet with private keys imported from old wallet.dat Except the labels are not imported.

The thread should be renamed to more appropriate name. Also I will not share the corrupt wallet since it does contain something I would not like to share.