Bitcoin Forum
May 09, 2024, 01:36:15 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: A fetal error occurred. Bitcoin no longer continue safely and will quit  (Read 1009 times)
qasimilyas99 (OP)
Newbie
*
Offline Offline

Activity: 55
Merit: 0


View Profile
June 29, 2017, 08:12:55 PM
 #1

I have upgraded Bitcoin Core version 0.10.0 to version 0.14.2 & replaced my wallet.dat but problem is when i try to open Bitcoin Core version 0.14.2 it shows error that >  A fetal error occurred. Bitcoin no longer continue safely and will quit.
Please help me, Thank You.
https://image.prntscr.com/image/YAHAZ3edS-mn6iVSrcflKw.png
1715261775
Hero Member
*
Offline Offline

Posts: 1715261775

View Profile Personal Message (Offline)

Ignore
1715261775
Reply with quote  #2

1715261775
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1715261775
Hero Member
*
Offline Offline

Posts: 1715261775

View Profile Personal Message (Offline)

Ignore
1715261775
Reply with quote  #2

1715261775
Report to moderator
jackg
Copper Member
Legendary
*
Offline Offline

Activity: 2856
Merit: 3071


https://bit.ly/387FXHi lightning theory


View Profile
June 29, 2017, 09:17:21 PM
 #2

I have upgraded Bitcoin Core version 0.10.0 to version 0.14.2 & replaced my wallet.dat but problem is when i try to open Bitcoin Core version 0.14.2 it shows error that >  A fetal error occurred. Bitcoin no longer continue safely and will quit.
Please help me, Thank You.


Can you post the debug.log file? It'll be in the same folder as the bitcoin wallet and will provide more tehcnical information so the problaem can be diagnosed better.
qasimilyas99 (OP)
Newbie
*
Offline Offline

Activity: 55
Merit: 0


View Profile
June 29, 2017, 10:06:13 PM
 #3

Which part of  debug.log i need to show here, Thank You.
achow101
Moderator
Legendary
*
Offline Offline

Activity: 3388
Merit: 6631


Just writing some code


View Profile WWW
June 30, 2017, 04:46:48 AM
 #4

Which part of  debug.log i need to show here, Thank You.
All of it.

qasimilyas99 (OP)
Newbie
*
Offline Offline

Activity: 55
Merit: 0


View Profile
June 30, 2017, 04:07:53 PM
 #5

debug.log

Code:


2017-06-30 15:58:57



2017-06-30 15:58:57 Bitcoin version v0.14.2
2017-06-30 15:58:57 InitParameterInteraction: parameter interaction: -whitelistforcerelay=1 -> setting -whitelistrelay=1
2017-06-30 15:58:57 Assuming ancestors of block 00000000000000000013176bf8d7dfeab4e1db31dc93bc311b436e82ab226b90 have valid signatures.
2017-06-30 15:58:57 GUI: "registerShutdownBlockReason: Successfully registered: Bitcoin Core didn't yet exit safely..."
2017-06-30 15:58:57 Default data directory C:\Users\Qasim\AppData\Roaming\Bitcoin
2017-06-30 15:58:57 Using data directory C:\Users\Qasim\AppData\Roaming\Bitcoin
2017-06-30 15:58:57 Using config file C:\Users\Qasim\AppData\Roaming\Bitcoin\bitcoin.conf
2017-06-30 15:58:57 Using at most 125 automatic connections (2048 file descriptors available)
2017-06-30 15:58:57 Using 32 MiB out of 32 requested for signature cache, able to store 1048576 elements
2017-06-30 15:58:57 Using 2 threads for script verification
2017-06-30 15:58:57 Using BerkeleyDB version Berkeley DB 4.8.30: (April  9, 2010)
2017-06-30 15:58:57 Using wallet wallet.dat
2017-06-30 15:58:57 scheduler thread start
2017-06-30 15:58:57 init message: Verifying wallet...
2017-06-30 15:58:57 CDBEnv::Open: LogDir=C:\Users\Qasim\AppData\Roaming\Bitcoin\database ErrorFile=C:\Users\Qasim\AppData\Roaming\Bitcoin\db.log
2017-06-30 15:58:57 Bound to [::]:8333
2017-06-30 15:58:57 Bound to 0.0.0.0:8333
2017-06-30 15:58:57 Cache configuration:
2017-06-30 15:58:57 * Using 2.0MiB for block index database
2017-06-30 15:58:57 * Using 8.0MiB for chain state database
2017-06-30 15:58:57 * Using 440.0MiB for in-memory UTXO set (plus up to 286.1MiB of unused mempool space)
2017-06-30 15:58:57 init message: Loading block index...
2017-06-30 15:58:57 Opening LevelDB in C:\Users\Qasim\AppData\Roaming\Bitcoin\blocks\index
2017-06-30 15:58:58 Opened LevelDB successfully
2017-06-30 15:58:58 Using obfuscation key for C:\Users\Qasim\AppData\Roaming\Bitcoin\blocks\index: 0000000000000000
2017-06-30 15:58:58 Opening LevelDB in C:\Users\Qasim\AppData\Roaming\Bitcoin\chainstate
2017-06-30 15:58:58 Opened LevelDB successfully
2017-06-30 15:58:58 Wrote new obfuscate key for C:\Users\Qasim\AppData\Roaming\Bitcoin\chainstate: 907f67956e728e5d
2017-06-30 15:58:58 Using obfuscation key for C:\Users\Qasim\AppData\Roaming\Bitcoin\chainstate: 907f67956e728e5d
2017-06-30 15:58:58 LoadBlockIndexDB: last block file = 0
2017-06-30 15:58:58 LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=0, size=0, heights=0...0, time=1970-01-01...1970-01-01)
2017-06-30 15:58:58 Checking all blk files are present...
2017-06-30 15:58:58 LoadBlockIndexDB: transaction index disabled
2017-06-30 15:58:58 Initializing databases...
2017-06-30 15:58:58 Pre-allocating up to position 0x1000000 in blk00000.dat
2017-06-30 15:58:58 init message: Verifying blocks...
2017-06-30 15:58:58  block index             438ms
2017-06-30 15:58:58 init message: Loading wallet...
2017-06-30 15:58:58 nFileVersion = 140200
2017-06-30 15:58:58 Keys: 0 plaintext, 0 encrypted, 0 w/ metadata, 0 total
2017-06-30 15:58:58 Performing wallet upgrade to 60000
2017-06-30 15:58:58 keypool added key 1, size=1
2017-06-30 15:58:59 keypool added key 2, size=2
2017-06-30 15:58:59 keypool added key 3, size=3
2017-06-30 15:58:59 keypool added key 4, size=4
2017-06-30 15:58:59 keypool added key 5, size=5
2017-06-30 15:58:59 keypool added key 6, size=6
2017-06-30 15:58:59 keypool added key 7, size=7
2017-06-30 15:58:59 keypool added key 8, size=8
2017-06-30 15:58:59 keypool added key 9, size=9
2017-06-30 15:58:59 keypool added key 10, size=10
2017-06-30 15:59:00 keypool added key 11, size=11
2017-06-30 15:59:00 keypool added key 12, size=12
2017-06-30 15:59:00 keypool added key 13, size=13
2017-06-30 15:59:00 keypool added key 14, size=14
2017-06-30 15:59:00 keypool added key 15, size=15
2017-06-30 15:59:00 keypool added key 16, size=16
2017-06-30 15:59:00 keypool added key 17, size=17
2017-06-30 15:59:01 keypool added key 18, size=18
2017-06-30 15:59:01 keypool added key 19, size=19
2017-06-30 15:59:01 keypool added key 20, size=20
2017-06-30 15:59:01 keypool added key 21, size=21
2017-06-30 15:59:01 keypool added key 22, size=22
2017-06-30 15:59:01 keypool added key 23, size=23
2017-06-30 15:59:01 keypool added key 24, size=24
2017-06-30 15:59:01 keypool added key 25, size=25
2017-06-30 15:59:01 keypool added key 26, size=26
2017-06-30 15:59:02 keypool added key 27, size=27
2017-06-30 15:59:02 keypool added key 28, size=28
2017-06-30 15:59:02 keypool added key 29, size=29
2017-06-30 15:59:02 keypool added key 30, size=30
2017-06-30 15:59:02 keypool added key 31, size=31
2017-06-30 15:59:02 keypool added key 32, size=32
2017-06-30 15:59:02 keypool added key 33, size=33
2017-06-30 15:59:03 keypool added key 34, size=34
2017-06-30 15:59:03 keypool added key 35, size=35
2017-06-30 15:59:03 keypool added key 36, size=36
2017-06-30 15:59:03 keypool added key 37, size=37
2017-06-30 15:59:03 keypool added key 38, size=38
2017-06-30 15:59:03 keypool added key 39, size=39
2017-06-30 15:59:03 keypool added key 40, size=40
2017-06-30 15:59:04 keypool added key 41, size=41
2017-06-30 15:59:04 keypool added key 42, size=42
2017-06-30 15:59:04 keypool added key 43, size=43
2017-06-30 15:59:04 keypool added key 44, size=44
2017-06-30 15:59:04 keypool added key 45, size=45
2017-06-30 15:59:04 keypool added key 46, size=46
2017-06-30 15:59:04 keypool added key 47, size=47
2017-06-30 15:59:04 keypool added key 48, size=48
2017-06-30 15:59:04 keypool added key 49, size=49
2017-06-30 15:59:05 keypool added key 50, size=50
2017-06-30 15:59:05 keypool added key 51, size=51
2017-06-30 15:59:05 keypool added key 52, size=52
2017-06-30 15:59:05 keypool added key 53, size=53
2017-06-30 15:59:05 keypool added key 54, size=54
2017-06-30 15:59:05 keypool added key 55, size=55
2017-06-30 15:59:06 keypool added key 56, size=56
2017-06-30 15:59:06 keypool added key 57, size=57
2017-06-30 15:59:06 keypool added key 58, size=58
2017-06-30 15:59:06 keypool added key 59, size=59
2017-06-30 15:59:06 keypool added key 60, size=60
2017-06-30 15:59:06 keypool added key 61, size=61
2017-06-30 15:59:07 keypool added key 62, size=62
2017-06-30 15:59:07 keypool added key 63, size=63
2017-06-30 15:59:07 keypool added key 64, size=64
2017-06-30 15:59:07 keypool added key 65, size=65
2017-06-30 15:59:08 keypool added key 66, size=66
2017-06-30 15:59:08 keypool added key 67, size=67
2017-06-30 15:59:08 keypool added key 68, size=68
2017-06-30 15:59:08 keypool added key 69, size=69
2017-06-30 15:59:09 keypool added key 70, size=70
2017-06-30 15:59:09 keypool added key 71, size=71
2017-06-30 15:59:09 keypool added key 72, size=72
2017-06-30 15:59:09 keypool added key 73, size=73
2017-06-30 15:59:10 keypool added key 74, size=74
2017-06-30 15:59:10 keypool added key 75, size=75
2017-06-30 15:59:11 keypool added key 76, size=76
2017-06-30 15:59:11 keypool added key 77, size=77
2017-06-30 15:59:11 keypool added key 78, size=78
2017-06-30 15:59:11 keypool added key 79, size=79
2017-06-30 15:59:11 keypool added key 80, size=80
2017-06-30 15:59:12 keypool added key 81, size=81
2017-06-30 15:59:12 keypool added key 82, size=82
2017-06-30 15:59:12 keypool added key 83, size=83
2017-06-30 15:59:12 keypool added key 84, size=84
2017-06-30 15:59:13 keypool added key 85, size=85
2017-06-30 15:59:13 keypool added key 86, size=86
2017-06-30 15:59:13 keypool added key 87, size=87
2017-06-30 15:59:13 keypool added key 88, size=88
2017-06-30 15:59:14 keypool added key 89, size=89
2017-06-30 15:59:14 keypool added key 90, size=90
2017-06-30 15:59:14 keypool added key 91, size=91
2017-06-30 15:59:15 keypool added key 92, size=92
2017-06-30 15:59:15 keypool added key 93, size=93
2017-06-30 15:59:15 keypool added key 94, size=94
2017-06-30 15:59:16 keypool added key 95, size=95
2017-06-30 15:59:16 keypool added key 96, size=96
2017-06-30 15:59:16 keypool added key 97, size=97
2017-06-30 15:59:16 keypool added key 98, size=98
2017-06-30 15:59:16 keypool added key 99, size=99
2017-06-30 15:59:17 keypool added key 100, size=100
2017-06-30 15:59:17 keypool added key 101, size=101
2017-06-30 15:59:17 keypool reserve 1
2017-06-30 15:59:17 keypool keep 1
2017-06-30 15:59:17  wallet                19470ms
2017-06-30 15:59:17 setKeyPool.size() = 100
2017-06-30 15:59:17 mapWallet.size() = 0
2017-06-30 15:59:17 mapAddressBook.size() = 1
2017-06-30 15:59:17 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(0tx)
2017-06-30 15:59:17 mapBlockIndex.size() = 1
2017-06-30 15:59:17 Failed to open mempool file from disk. Continuing anyway.
2017-06-30 15:59:17 nBestHeight = 0
2017-06-30 15:59:17 torcontrol thread start
2017-06-30 15:59:17 init message: Loading addresses...
2017-06-30 15:59:17 ERROR: Read: Failed to open file C:\Users\Qasim\AppData\Roaming\Bitcoin\peers.dat
2017-06-30 15:59:17 Invalid or missing peers.dat; recreating
2017-06-30 15:59:17 init message: Loading banlist...
2017-06-30 15:59:17 ERROR: Read: Failed to open file C:\Users\Qasim\AppData\Roaming\Bitcoin\banlist.dat
2017-06-30 15:59:17 Invalid or missing banlist.dat; recreating
2017-06-30 15:59:18 init message: Starting network threads...
2017-06-30 15:59:18 net thread start
2017-06-30 15:59:18 dnsseed thread start
2017-06-30 15:59:18 addcon thread start
2017-06-30 15:59:18 Loading addresses from DNS seeds (could take a while)
2017-06-30 15:59:18 opencon thread start
2017-06-30 15:59:18 msghand thread start
2017-06-30 15:59:18 init message: Done loading
2017-06-30 15:59:18 GUI: Platform customization: "windows"
2017-06-30 15:59:18 GUI: PaymentServer::LoadRootCAs: Loaded  53  root certificates
2017-06-30 15:59:19 receive version message: /Satoshi:0.14.2/UASF-Segwit:0.3(BIP148)/: version 70015, blocks=473536, us=39.46.178.9:54839, peer=0
2017-06-30 15:59:19 receive version message: /Satoshi:0.14.1/: version 70015, blocks=473536, us=39.46.178.9:54840, peer=1
2017-06-30 15:59:20 120 addresses found from DNS seeds
2017-06-30 15:59:20 dnsseed thread exit
2017-06-30 15:59:20 receive version message: /Satoshi:0.14.1/: version 70015, blocks=473536, us=39.46.178.9:54842, peer=2
2017-06-30 15:59:36 tor: Thread interrupt
2017-06-30 15:59:36 addcon thread exit
2017-06-30 15:59:36 torcontrol thread exit
2017-06-30 15:59:36 scheduler thread interrupt
2017-06-30 15:59:36 Shutdown: In progress...
2017-06-30 15:59:36 net thread exit
2017-06-30 15:59:36 msghand thread exit
2017-06-30 15:59:38 opencon thread exit
2017-06-30 15:59:38 Dumped mempool: 0s to copy, 0.084629s to dump
2017-06-30 15:59:38 Shutdown: done
2017-06-30 16:00:23



















2017-06-30 16:00:23 Bitcoin version v0.14.2
2017-06-30 16:00:23 InitParameterInteraction: parameter interaction: -whitelistforcerelay=1 -> setting -whitelistrelay=1
2017-06-30 16:00:23 Assuming ancestors of block 00000000000000000013176bf8d7dfeab4e1db31dc93bc311b436e82ab226b90 have valid signatures.
2017-06-30 16:00:23 GUI: "registerShutdownBlockReason: Successfully registered: Bitcoin Core didn't yet exit safely..."
2017-06-30 16:00:23 Default data directory C:\Users\Qasim\AppData\Roaming\Bitcoin
2017-06-30 16:00:23 Using data directory C:\Users\Qasim\AppData\Roaming\Bitcoin
2017-06-30 16:00:23 Using config file C:\Users\Qasim\AppData\Roaming\Bitcoin\bitcoin.conf
2017-06-30 16:00:23 Using at most 125 automatic connections (2048 file descriptors available)
2017-06-30 16:00:23 Using 32 MiB out of 32 requested for signature cache, able to store 1048576 elements
2017-06-30 16:00:23 Using 2 threads for script verification
2017-06-30 16:00:23 Using BerkeleyDB version Berkeley DB 4.8.30: (April  9, 2010)
2017-06-30 16:00:23 scheduler thread start
2017-06-30 16:00:23 Using wallet wallet.dat
2017-06-30 16:00:23 init message: Verifying wallet...
2017-06-30 16:00:23 CDBEnv::Open: LogDir=C:\Users\Qasim\AppData\Roaming\Bitcoin\database ErrorFile=C:\Users\Qasim\AppData\Roaming\Bitcoin\db.log
2017-06-30 16:00:24 Bound to [::]:8333
2017-06-30 16:00:24 Bound to 0.0.0.0:8333
2017-06-30 16:00:24 Cache configuration:
2017-06-30 16:00:24 * Using 2.0MiB for block index database
2017-06-30 16:00:24 * Using 8.0MiB for chain state database
2017-06-30 16:00:24 * Using 440.0MiB for in-memory UTXO set (plus up to 286.1MiB of unused mempool space)
2017-06-30 16:00:24 init message: Loading block index...
2017-06-30 16:00:24 Opening LevelDB in C:\Users\Qasim\AppData\Roaming\Bitcoin\blocks\index
2017-06-30 16:00:24 Opened LevelDB successfully
2017-06-30 16:00:24 Using obfuscation key for C:\Users\Qasim\AppData\Roaming\Bitcoin\blocks\index: 0000000000000000
2017-06-30 16:00:24 Opening LevelDB in C:\Users\Qasim\AppData\Roaming\Bitcoin\chainstate
2017-06-30 16:00:24 Opened LevelDB successfully
2017-06-30 16:00:24 Using obfuscation key for C:\Users\Qasim\AppData\Roaming\Bitcoin\chainstate: 907f67956e728e5d
2017-06-30 16:00:24 LoadBlockIndexDB: last block file = 0
2017-06-30 16:00:24 LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=1, size=293, heights=0...0, time=2009-01-03...2009-01-03)
2017-06-30 16:00:24 Checking all blk files are present...
2017-06-30 16:00:24 LoadBlockIndexDB: transaction index disabled
2017-06-30 16:00:24 LoadBlockIndexDB: hashBestChain=000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f height=0 date=2009-01-03 18:15:05 progress=0.000000
2017-06-30 16:00:24 init message: Rewinding blocks...
2017-06-30 16:00:24 init message: Verifying blocks...
2017-06-30 16:00:24  block index             368ms
2017-06-30 16:00:24 init message: Loading wallet...
2017-06-30 16:00:25 nFileVersion = 100000
2017-06-30 16:00:25 Keys: 0 plaintext, 22950 encrypted, 0 w/ metadata, 22950 total
2017-06-30 16:00:25 Performing wallet upgrade to 60000
2017-06-30 16:00:25

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

2017-06-30 16:00:31 CDBEnv::EnvShutdown: Error 22 shutting down database environment: Invalid argument


achow101
Moderator
Legendary
*
Offline Offline

Activity: 3388
Merit: 6631


Just writing some code


View Profile WWW
June 30, 2017, 04:41:50 PM
 #6

It looks like your wallet.dat file is corrupted. Try replacing your wallet.dat file with a backup.

qasimilyas99 (OP)
Newbie
*
Offline Offline

Activity: 55
Merit: 0


View Profile
June 30, 2017, 05:05:28 PM
 #7

I tried this method but still showing problem. I've mentioned below which Bitcoin Core working or not working with my wallet.dat,

Bitcoin Core version 0.14.2 Not working with my wallet.dat
Bitcoin Core version 0.14.1 Not working with my wallet.dat
Bitcoin Core version 0.14.0 Not working with my wallet.dat
Bitcoin Core version 0.13.2 Not working with my wallet.dat
Bitcoin Core version 0.13.1 Not working with my wallet.dat
Bitcoin Core version 0.13.0 Not working with my wallet.dat
Bitcoin Core version 0.12.1 Working with my wallet.dat
Bitcoin Core version 0.12.0 Working with my wallet.dat
Bitcoin Core version 0.11.2 Working with my wallet.dat
Bitcoin Core version 0.11.1 Working with my wallet.dat
Bitcoin Core version 0.10.3 Working with my wallet.dat
Bitcoin Core version 0.11.0 Working with my wallet.dat
Bitcoin Core version 0.10.2 Working with my wallet.dat
Bitcoin Core version 0.10.1 Working with my wallet.dat
Bitcoin Core version 0.10.0 Working with my wallet.dat
achow101
Moderator
Legendary
*
Offline Offline

Activity: 3388
Merit: 6631


Just writing some code


View Profile WWW
June 30, 2017, 05:53:27 PM
 #8

I tried this method but still showing problem. I've mentioned below which Bitcoin Core working or not working with my wallet.dat,

Bitcoin Core version 0.14.2 Not working with my wallet.dat
Bitcoin Core version 0.14.1 Not working with my wallet.dat
Bitcoin Core version 0.14.0 Not working with my wallet.dat
Bitcoin Core version 0.13.2 Not working with my wallet.dat
Bitcoin Core version 0.13.1 Not working with my wallet.dat
Bitcoin Core version 0.13.0 Not working with my wallet.dat
Bitcoin Core version 0.12.1 Working with my wallet.dat
Bitcoin Core version 0.12.0 Working with my wallet.dat
Bitcoin Core version 0.11.2 Working with my wallet.dat
Bitcoin Core version 0.11.1 Working with my wallet.dat
Bitcoin Core version 0.10.3 Working with my wallet.dat
Bitcoin Core version 0.11.0 Working with my wallet.dat
Bitcoin Core version 0.10.2 Working with my wallet.dat
Bitcoin Core version 0.10.1 Working with my wallet.dat
Bitcoin Core version 0.10.0 Working with my wallet.dat
Interesting. Thank you for trying that, I know what the problem is now and how you can fix it (although it is a bug that needs to be looked at).

Go to the Bitcoin Core datadir (same place where you find the debug.log file). Then either edit or create a bitcoin.conf file. Add to that file the following line:
Code:
usehd=0
Then start Bitcoin Core and it should work.

qasimilyas99 (OP)
Newbie
*
Offline Offline

Activity: 55
Merit: 0


View Profile
June 30, 2017, 06:29:10 PM
 #9

I have created bitcoin.conf file then added the following line: usehd=0 , it's problem solved & Bitcoin Core version 0.14.2 working correctly, but my bitcoins not showing, Very very thanks for your cooperation.

achow101
Moderator
Legendary
*
Offline Offline

Activity: 3388
Merit: 6631


Just writing some code


View Profile WWW
July 01, 2017, 07:39:17 AM
 #10

but my bitcoins not showing
Are you fully synced yet? If not, let it sync. If you are synced, try rescanning. Add rescan=1 to your bitcoin.conf file and start Bitcoin Core. Once Core has started, remove that line so that you don't rescan every time you start Core.

Also, would you be willing to send me your wallet.dat file, after you move all of your Bitcoin out of it of course. I want to investigate what is causing the error so that I can determine whether it is a bug in Core and if it can be fixed.

qasimilyas99 (OP)
Newbie
*
Offline Offline

Activity: 55
Merit: 0


View Profile
July 01, 2017, 03:06:13 PM
 #11

It's not fully synced yet, My wallet.dat is password protected & I don't know password, I'm finding best tool for recovering my password, Thank You for your cooperation.


jackg
Copper Member
Legendary
*
Offline Offline

Activity: 2856
Merit: 3071


https://bit.ly/387FXHi lightning theory


View Profile
July 02, 2017, 06:40:37 PM
 #12

It's not fully synced yet, My wallet.dat is password protected & I don't know password, I'm finding best tool for recovering my password, Thank You for your cooperation.




If you don't know the password then the core cannot work out what your private keys are and your addresses. There's no point syncing your core version until you unencrypt your wallet.dat. as it'll have to rescan at the least. Unless your addresses show.
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!