Quote from: execoin on August 29, 2014, 06:12:46 AM

Quote from: Qxw on August 29, 2014, 05:49:03 AM

Quote from: execoin on August 29, 2014, 05:27:29 AM

Exelite lightweight Execoin wallet has been updated (to version 0.3.11.9)

But WHY qt-wallet loose sync frequently.

Just import one priv key to wallet and soon it show just ok. After fifteen minutes I look agen and think I send coins to other address. What hell... wallet is out of sync.
348292 and now waiting estimated block number 363763. (Edit: just now 5.50AM GMT)

With different times, different numbers it loose sync. Sometimes restrat help shortly, sometimes it soon return this kind of state when it get more connections.
Now there is one connection and situation is "out of sync" and this totally wrong block count what it is waiting. Where from it get this wrong data?

Agen day what I can not move my coins due to this hassle with sync.

Two days ago I send over 10k EXE and it fails. Wallet tell balance zero after send and block chan Explorer tell coins sit still in addres and have not moved. After hours waiting and in this time walllet was also later sunc, I stop waiting. (transfer status in wallet was just ?).

I delete wallet dat (name it agen) and start new. Agen it get sync, then Private key in and it show agen balance. I send agen it to this other address. wallet then zero balance, this ok, and show transfer status ?. Agen wait long time, restart wallet two times. Some times it sync. But coins did not go to other address where I send these.
Agen wallet dat rename and start new. Import priv, agen it show balance ok. This time wallet stau sync and I send coins and this time it success.

What are these sync drop outs with wrong block numbers from some node?

If this can not solve it destroy this coin. What there so difficult to keep nodes in sync so that there is not agen and agen this wrong fork on the air. Who is running this wrong fork and why?

Because there are still nodes on wrong fork. Correct block now is 348314.
In order to get rid of wrong nodes you could add the following to execoin.conf https://bitcointalk.org/index.php?topic=491058.msg8566412#msg8566412

You can't fix a fork with addnodes. You need to checkpoint the correct chain at a point after the fork.

why is the chain still forking?