Any idea what happened and how to fix that?
In fact it is interesting situation and will be good to see what and how happened... and most likely how it was resolved.

Yep. Updated node yesterday. And now it stuck with synchronization on "blocks": 212437.

Last block successfuly synchronized:
2017-10-18 09:30:03 ProcessNewBlock : ACCEPTED
2017-10-18 09:30:03 UpdateTip: new best=00000000005f3aa414d482842df1bc4788bfa7b0cc158ee2bd92e4c28cf26c7d  height=212437  log2_work=58.603905  tx=286688  date=2017-10-17 23:16:35 progress=0.979987  cache=9.0MiB(21818tx)

Now I have only that in logs:
2017-10-18 09:58:31 CEternitynodeSync::ProcessTick -- nTick 4675 nRequestedEternitynodeAssets 1 -- requesting sporks from peer 10
2017-10-18 09:58:31 ProcessMessages(spork, 86 bytes): Exception 'CDataStream::read(): end of data' caught, normally caused by a message being shorter than its stated length
2017-10-18 09:58:31 ProcessMessages(spork, 86 bytes) FAILED peer=10
2017-10-18 09:58:31 ProcessMessages(spork, 86 bytes): Exception 'CDataStream::read(): end of data' caught, normally caused by a message being shorter than its stated length
2017-10-18 09:58:31 ProcessMessages(spork, 86 bytes) FAILED peer=10
2017-10-18 09:58:31 ProcessMessages(spork, 86 bytes): Exception 'CDataStream::read(): end of data' caught, normally caused by a message being shorter than its stated length
2017-10-18 09:58:31 ProcessMessages(spork, 86 bytes) FAILED peer=10
2017-10-18 09:58:31 ProcessMessages(spork, 86 bytes): Exception 'CDataStream::read(): end of data' caught, normally caused by a message being shorter than its stated length
2017-10-18 09:58:31 ProcessMessages(spork, 86 bytes) FAILED peer=10
2017-10-18 09:58:37 CEternitynodeSync::ProcessTick -- nTick 4681 nRequestedEternitynodeAssets 1 nRequestedEternitynodeAttempt 0 nSyncProgress 0.000000
2017-10-18 09:58:43 CEternitynodeSync::ProcessTick -- nTick 4687 nRequestedEternitynodeAssets 1 nRequestedEternitynodeAttempt 0 nSyncProgress 0.000000


And not able to start Node as it says:
"errorMessage": "Sync in progress. Must wait until sync is complete to start Eternitynode"


So, some issues with synchronization.

Same on my side. Tried to re-sync, reindex, etc.... no luck

Seems that there are some issues.
My Masternode stuck and is generating continuously messages:

2017-10-18 08:21:17 CEternitynodeSync::ProcessTick -- nTick 247 nRequestedEternitynodeAssets 1 nRequestedEternitynodeAttempt 0 nSyncProgress 0.000000
2017-10-18 08:21:23 CEternitynodeSync::ProcessTick -- nTick 253 nRequestedEternitynodeAssets 1 nRequestedEternitynodeAttempt 0 nSyncProgress 0.000000
2017-10-18 08:21:26 connection from 95.31.211.13:62253 dropped (banned)
2017-10-18 08:21:29 CEternitynodeSync::ProcessTick -- nTick 259 nRequestedEternitynodeAssets 1 nRequestedEternitynodeAttempt 0 nSyncProgress 0.000000
2017-10-18 08:21:35 CEternitynodeSync::ProcessTick -- nTick 265 nRequestedEternitynodeAssets 1 nRequestedEternitynodeAttempt 0 nSyncProgress 0.000000
2017-10-18 08:21:41 CEternitynodeSync::ProcessTick -- nTick 271 nRequestedEternitynodeAssets 1 nRequestedEternitynodeAttempt 0 nSyncProgress 0.000000

Any status? Is there any fix planned?

You have 2 options:
 - YAJU Wallet
 - https://coinsmarkets.com

Joined AirDrop!
Looking forward to see it in wallet and start staking

From what I see there is a need to rebuild team for Eternity.
Seems that there is community interested in keep that project going as still lot of masternodes out there (I have MN for ENT too).

Roadmap definition would be good for beginning to re-define shape of Eternity.
Project requires dev team to be re-established as well.

Any chance to use existing home page, etc.? Current home page is ok I think, just need some current information. Important will be to have devs to keep working on wallet (still missing for macOS). Also, we can think how to add ENT as currency to existing multi-currency wallets (like exodus?). But that requires devs :/

Agreed. I'd like to see Eternity progressing. However, how to approach that? There is no roadmap for Eternity project.
Any ideas how can we push it forward?

Also have no payment for about 2 weeks now. Did restart of the node and nothing happened. In debug.log all seems to be fine and no errors.