Can't synchronize


your problem is not with the mempool…you need to reindex and rescan the blockchain by starting litecoin-qt from command prompt with the -reindex -rescan flags…

in windows in command prompt/terminal its
litecoin-qt.exe -reindex -rescan

in linux in terminal its
./litecoin-qt -reindex -rescan

on mac in termainal its
open -a litecoin-qt -reindex -rescan


I did reindex from terminal. What’s the difference between -reindex and -reindex -rescan.
-reindex and -rescan can be used same ?


re index will reindex the block headers on your drive so they can be synced and rescan rescan’s the blockchain looking for values belonging to the address contained in the wallet…you cant rescan correctly if the indexing on your drive is messed up for some reason…usually happens accidentally sometimes if the node was closed while in the middle of receiving syncing information from the chain

notice when you open the app it loads the block index then syncs the headers then syncs the chain after all the block and wallet information is in its correct place

Rebuild chain state and block index from the blk*.dat files on disk

Rescan the block chain for missing wallet transactions on startup

here is a list of all the command options and what they do(this is from version 13.1.2 so there are some new options in 14.2 now as well)

Litecoin Core version v0.13.2.1 (64-bit)
litecoin-qt [command-line options]

Print this help message and exit
Print version and exit
Execute command when a relevant alert is received or we see a really long fork (%s in cmd is replaced by message)
Execute command when the best block changes (%s in cmd is replaced by block hash)
How many blocks to check at startup (default: 24, 0 = all)
How thorough the block verification of -checkblocks is (0-4, default: 3)
Specify configuration file (default: litecoin.conf)
Specify data directory
Set database cache size in megabytes (4 to 16384, default: 300)
Imports blocks from external blk000??.dat file on startup
Keep at most unconnectable transactions in memory (default: 100)
Keep the transaction memory pool below megabytes (default: 5)
Do not keep transactions in the mempool longer than hours (default: 72)
Set the number of script verification threads (-3 to 16, 0 = auto, <0 = leave that many cores free, default: 0)
Reduce storage requirements by pruning (deleting) old blocks. This mode is incompatible with -txindex and -rescan. Warning: Reverting this setting requires re-downloading the entire blockchain. (default: 0 = disable pruning blocks, >550 = target size in MiB to use for block files)
Rebuild chain state from the currently indexed blocks
Rebuild chain state and block index from the blk*.dat files on disk
Maintain a full transaction index, used by the getrawtransaction rpc call (default: 0)

Connection options:

Add a node to connect to and attempt to keep the connection open
Threshold for disconnecting misbehaving peers (default: 100)
Number of seconds to keep misbehaving peers from reconnecting (default: 86400)
Bind to given address and always listen on it. Use [host]:port notation for IPv6
Connect only to the specified node(s)
Discover own IP addresses (default: 1 when listening and no -externalip or -proxy)
Allow DNS lookups for -addnode, -seednode and -connect (default: 1)
Query for peer addresses via DNS lookup, if low on addresses (default: 1 unless -connect)
Specify your own public address
Always query for peer addresses via DNS lookup (default: 0)
Accept connections from outside (default: 1 if no -proxy or -connect)
Automatically create Tor hidden service (default: 1)
Maintain at most connections to peers (default: 125)
Maximum per-connection receive buffer, *1000 bytes (default: 5000)
Maximum per-connection send buffer, *1000 bytes (default: 1000)
Maximum allowed median peer time offset adjustment. Local perspective of time may be influenced by peers forward or backward by this amount. (default: 2100 seconds)
Use separate SOCKS5 proxy to reach peers via Tor hidden services (default: -proxy)
Only connect to nodes in network (ipv4, ipv6 or onion)
Relay non-P2SH multisig (default: 1)
Support filtering of blocks and transaction with bloom filters (default: 1)
Listen for connections on (default: 9333 or testnet: 19333)
Connect through SOCKS5 proxy
Randomize credentials for every proxy connection. This enables Tor stream isolation (default: 1)
Sets the serialization of raw transaction or block hex returned in non-verbose mode, non-segwit(0) or segwit(1) (default: 1)
Connect to a node to retrieve peer addresses, and disconnect
Specify connection timeout in milliseconds (minimum: 1, default: 5000)
Tor control port to use if onion listening enabled (default:
Tor control port password (default: empty)
Use UPnP to map the listening port (default: 0)
Bind to given address and whitelist peers connecting to it. Use [host]:port notation for IPv6
Whitelist peers connecting from the given IP address (e.g. or CIDR notated network (e.g. Can be specified multiple times. Whitelisted peers cannot be DoS banned and their transactions are always relayed, even if they are already in the mempool, useful e.g. for a gateway
Accept relayed transactions received from whitelisted peers even when not relaying transactions (default: 1)
Force relay of transactions from whitelisted peers even if they violate local relay policy (default: 1)
Tries to keep outbound traffic under the given target (in MiB per 24h), 0 = no limit (default: 0)

Wallet options:

Do not load the wallet and disable wallet RPC calls
Set key pool size to (default: 100)
A fee rate (in LTC/kB) that will be used when fee estimation has insufficient data (default: 0.002)
Fees (in LTC/kB) smaller than this are considered zero fee for transaction creation (default: 0.001)
Fee (in LTC/kB) to add to transactions you send (default: 0.00)
Rescan the block chain for missing wallet transactions on startup
Attempt to recover private keys from a corrupt wallet on startup
Spend unconfirmed change when sending transactions (default: 1)
If paytxfee is not set, include enough fee so transactions begin confirmation on average within n blocks (default: 2)
Use hierarchical deterministic key generation (HD) after BIP32. Only has effect during wallet creation/first start (default: 1)
Upgrade wallet to latest format on startup
Specify wallet file (within data directory) (default: wallet.dat)
Make the wallet broadcast transactions (default: 1)
Execute command when a wallet transaction changes (%s in cmd is replaced by TxID)
Delete all wallet transactions and only recover those parts of the blockchain through -rescan on startup (1 = keep tx meta data e.g. account owner and payment request information, 2 = drop tx meta data)

Debugging/Testing options:

Append comment to the user agent string
Output debugging information (default: 0, supplying is optional). If is not supplied or if = 1, output all debugging information. can be: addrman, alert, bench, cmpctblock, coindb, db, http, libevent, lock, mempool, mempoolrej, net, proxy, prune, rand, reindex, rpc, selectcoins, tor, zmq, qt.
Show all debugging options (usage: --help -help-debug)
Include IP addresses in debug output (default: 0)
Prepend debug output with timestamp (default: 1)
Fees (in LTC/kB) smaller than this are considered zero fee for relaying, mining and transaction creation (default: 0.001)
Maximum total fees (in LTC) to use in a single wallet transaction or raw transaction; setting this too low may abort large transactions (default: 0.10)
Send trace/debug info to console instead of debug.log file
Shrink debug.log file on client startup (default: 1 when no -debug)

Chain selection options:

Use the test chain

Node relay options:

Equivalent bytes per sigop in transactions for relay and mining (default: 20)
Relay and mine data carrier transactions (default: 1)
Maximum size of data in data carrier transactions we relay and mine (default: 83)
Enable transaction replacement in the memory pool (default: 0)

Block creation options:

Set maximum BIP141 block weight (default: 3000000)
Set maximum block size in bytes (default: 750000)
Set maximum size of high-priority/low-fee transactions in bytes (default: 0)

RPC server options:

Accept command line and JSON-RPC commands
Accept public REST requests (default: 0)
Bind to given address to listen for JSON-RPC connections. Use [host]:port notation for IPv6. This option can be specified multiple times (default: bind to all interfaces)
Location of the auth cookie (default: data dir)
Username for JSON-RPC connections
Password for JSON-RPC connections
Username and hashed password for JSON-RPC connections. The field comes in the format: :$. A canonical python script is included in share/rpcuser. This option can be specified multiple times
Listen for JSON-RPC connections on (default: 9332 or testnet: 19332)
Allow JSON-RPC connections from specified source. Valid for are a single IP (e.g., a network/netmask (e.g. or a network/CIDR (e.g. This option can be specified multiple times
Set the number of threads to service RPC calls (default: 4)

UI Options:

Choose data directory on startup (default: 0)
Set language, for example “de_DE” (default: system locale)
Start minimized
Set SSL root certificates for payment request (default: -system-)
Show splash screen on startup (default: 1)
Reset all settings changed in the GUI


I’m doing litecoin-qt -reindex -rescan now. I’ll let you know the result. Thank you.!


The progress bar stopped about 60 % but synchronizing (100.0%) appeared at the bottom of screen. Is this successful?
The result of debug log was same…




if synchronization is at 100% then you are synchronized…
are you using the latest verison of litecoin? version 14.2? because it seems like you have a corrupted backup

your very first post shows you storing “nonstandard transactions”…

are you sure you only have one copy of wallet.dat in your appdata folder?

try starting with -mempoolreplacment flag?

only other thing I can think to do is delete your backup and start litecoin…make it sync from scratch as an empty wallet…and then replace the wallet.dat file with oyur backup renaming it wallet.dat and deleting the first .dat file…now that you have a full copy of the blockchain you can use -rescan flag


My litecoin version is v14.2. I updated latest version.

try starting with -mempoolreplacment flag?
Not yet. I’ll try.

only other thing I can think to do is delete your >backup and start litecoin…make it sync from scratch >as an empty wallet…and then replace the wallet.dat >file with oyur backup renaming it wallet.dat and >deleting the first .dat file…now that you have a full >copy of the blockchain you can use -rescan flag

I haven’t understand how to do what you said. Firstly, I’ll try rescan flag just in case.


just make sure you keep a good copy of that backup separately…I have had to completely uninstall and reinstall and then let it sync and then replace the wallet.dat file on my laptop…that was the only way I could get it to work…it was a registry problem when I installed it…reinstall was the only way I was able to fix the problem i had…good luck


Hi I saved backup and install again and sync from scratch. It completely done(sync) after that I saved wallet.dat from backup. Finally, the LTC value appears normally!!:+1::blush:


Thank you for your lots of tips and support!!