Im a noob here, what do I do?
open command line and start litecoin core like this firstâŚ
for windows:
litecoin-qt.exe -reindex -rescan
for linux/apple:
./litecoin-qt -reindex -rescan
in your appdata folder you need to see what the issue is at the bottom of the âdebug.logâ file
since your new this all may sound like jibberish to youâŚ
is it the newest version? 14.2? what OS are you runningâŚin windows you may need to right click and select âcompatibility optionsââŚ
do you have a backup?
if you have a backupâŚyou can just reinstall litecoin core after you do a memory diagnostic and you know the wallet is compatible with your OS you can reinstall core wallet and let it sync as a blank walletâŚthen replace the âwallet.datâ file in the appdata folder with your backup and start core from command line with the â-rescanâ flagâŚ
send me a message and I can walk you through a step by stepâŚ
2 Likes
Thanks for responding. I was able to do some research and went to the Appdata folder to force a rescan. It downloaded fine after that, and now I can move forward.This experience had me realize that as a noob I need to switch to an less advanced wallet, like Electrum. Thanks again.
Electrum isnât less advanced. It just doesnât need to sync the whole blockchain. Requires less space.
But it replies on a remote electrum server, possibly less interesting if youâre very concerned about your privacy.
Other than that itâs a very good wallet
1 Like
That is good to know. I read somewhere that it was easier. What better, more secure wallet do you recommend?
core wallet is the only âdecentralizedâ wallet out there that runs its own serverâŚall the others are applications that connect to centralized serversâŚhowever you can run a full litecoin node and use a wallet app to connect to the full node as wellâŚ
Hello, I saw this thread and am having the same issue. I am new to this. Any help is greatly appreciated. I experienced this problem after Bit Defender blocked the load up of lite coin core. I reinstalled the program after adding it to the exception list but am still having the same issue.
Even after adding the -reindex -rescan line to the shortcut it hangs on syncing headers. Below is a screen shot of how far it gets. I have included a copy of the debug log after a fresh install of the wallet with out me pasting my old wallet.dat into the directory.
I am running version 18.1 64 bit on Windows 10 Pro 64 Bit.
2021-04-01T14:22:08Z Litecoin Core version v0.18.1 (release build)
2021-04-01T14:22:09Z Assuming ancestors of block b34a457c601ef8ce3294116e3296078797be7ded1b0d12515395db9ab5e93ab8 have valid signatures.
2021-04-01T14:22:09Z Setting nMinimumChainWork=0000000000000000000000000000000000000000000002ee655bf00bf13b4cca
2021-04-01T14:22:09Z Using the âshani(1way,2way)â SHA256 implementation
2021-04-01T14:22:09Z Using RdSeed as additional entropy source
2021-04-01T14:22:09Z Using RdRand as an additional entropy source
2021-04-01T14:22:09Z Default data directory C:\Users\micah\AppData\Roaming\Litecoin
2021-04-01T14:22:09Z Using data directory F:\Litecoin Block Chain
2021-04-01T14:22:09Z Config file: F:\Litecoin Block Chain\litecoin.conf (not found, skipping)
2021-04-01T14:22:09Z Using at most 125 automatic connections (2048 file descriptors available)
2021-04-01T14:22:09Z Using 16 MiB out of 32/2 requested for signature cache, able to store 524288 elements
2021-04-01T14:22:09Z Using 16 MiB out of 32/2 requested for script execution cache, able to store 524288 elements
2021-04-01T14:22:09Z Using 16 threads for script verification
2021-04-01T14:22:09Z GUI: âregisterShutdownBlockReason: Successfully registered: Litecoin Core didnât yet exit safelyâŚâ
2021-04-01T14:22:09Z scheduler thread start
2021-04-01T14:22:09Z Using wallet directory F:\Litecoin Block Chain
2021-04-01T14:22:09Z init message: Verifying wallet(s)âŚ
2021-04-01T14:22:09Z Using BerkeleyDB version Berkeley DB 4.8.30: (April 9, 2010)
2021-04-01T14:22:09Z Using wallet F:\Litecoin Block Chain
2021-04-01T14:22:09Z BerkeleyEnvironment::Open: LogDir=F:\Litecoin Block Chain\database ErrorFile=F:\Litecoin Block Chain\db.log
2021-04-01T14:22:09Z init message: Loading banlistâŚ
2021-04-01T14:22:09Z Cache configuration:
2021-04-01T14:22:09Z * Using 2.0 MiB for block index database
2021-04-01T14:22:09Z * Using 8.0 MiB for chain state database
2021-04-01T14:22:09Z * Using 440.0 MiB for in-memory UTXO set (plus up to 286.1 MiB of unused mempool space)
2021-04-01T14:22:09Z init message: Loading block indexâŚ
2021-04-01T14:22:09Z Opening LevelDB in F:\Litecoin Block Chain\blocks\index
2021-04-01T14:22:09Z Opened LevelDB successfully
2021-04-01T14:22:09Z Using obfuscation key for F:\Litecoin Block Chain\blocks\index: 0000000000000000
2021-04-01T14:22:09Z LoadBlockIndexDB: last block file = 0
2021-04-01T14:22:09Z LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=1, size=288, heights=0âŚ0, time=2011-10-07âŚ2011-10-07)
2021-04-01T14:22:09Z Checking all blk files are presentâŚ
2021-04-01T14:22:09Z Opening LevelDB in F:\Litecoin Block Chain\chainstate
2021-04-01T14:22:09Z Opened LevelDB successfully
2021-04-01T14:22:09Z Using obfuscation key for F:\Litecoin Block Chain\chainstate: 85bf7f80a48dceea
2021-04-01T14:22:09Z Loaded best chain: hashBestChain=12a765e31ffd4059bada1e25190f6e98c99d9714d334efa41a195a7e7e04bfe2 height=0 date=2011-10-07T07:31:05Z progress=0.000000
2021-04-01T14:22:09Z init message: Rewinding blocksâŚ
2021-04-01T14:22:09Z init message: Verifying blocksâŚ
2021-04-01T14:22:09Z block index 89ms
2021-04-01T14:22:09Z init message: Loading walletâŚ
2021-04-01T14:22:09Z BerkeleyEnvironment::Open: LogDir=F:\Litecoin Block Chain\database ErrorFile=F:\Litecoin Block Chain\db.log
2021-04-01T14:22:09Z [default wallet] nFileVersion = 180100
2021-04-01T14:22:09Z [default wallet] Keys: 2001 plaintext, 0 encrypted, 2001 w/ metadata, 2001 total. Unknown wallet records: 0
2021-04-01T14:22:09Z [default wallet] Wallet completed loading in 40ms
2021-04-01T14:22:09Z [default wallet] setKeyPool.size() = 2000
2021-04-01T14:22:09Z [default wallet] mapWallet.size() = 0
2021-04-01T14:22:09Z [default wallet] mapAddressBook.size() = 0
2021-04-01T14:22:09Z mapBlockIndex.size() = 1
2021-04-01T14:22:09Z nBestHeight = 0
2021-04-01T14:22:09Z Imported mempool transactions from disk: 0 succeeded, 0 failed, 0 expired, 0 already there
2021-04-01T14:22:09Z torcontrol thread start
2021-04-01T14:22:09Z Bound to [::]:9333
2021-04-01T14:22:09Z Bound to 0.0.0.0:9333
2021-04-01T14:22:09Z init message: Loading P2P addressesâŚ
2021-04-01T14:22:09Z Loaded 23 addresses from peers.dat 1ms
2021-04-01T14:22:09Z init message: Starting network threadsâŚ
2021-04-01T14:22:09Z net thread start
2021-04-01T14:22:09Z dnsseed thread start
2021-04-01T14:22:09Z addcon thread start
2021-04-01T14:22:09Z opencon thread start
2021-04-01T14:22:09Z init message: Done loading
2021-04-01T14:22:09Z msghand thread start
2021-04-01T14:22:09Z GUI: Platform customization: âwindowsâ
2021-04-01T14:22:09Z GUI: PaymentServer::LoadRootCAs: Loaded 47 root certificates
2021-04-01T14:22:20Z Loading addresses from DNS seeds (could take a while)
2021-04-01T14:22:20Z 23 addresses found from DNS seeds
2021-04-01T14:22:20Z dnsseed thread exit
2 Likes
Finally figured it out. It appears that even adding it to the exception that Bit Defender had blocked it on the fire wall side. This has been fixed and now all the ledgers are current.
3 Likes
Thanks for sharing. Itâs too common that people find the answer for their own problems, then forget to come back to share it with the others who will have the same problem and get here by a search.
2 Likes