Topic: [ANN][ENT] Eternity - X11 - No Premine - page 27. (Read 83895 times)

How much eternity do you get in 24h with like 1200 MH/s ? Is it worth?

Friends are concerned about this project, I asked him to help me invest in this project, I do not know how the rate of return later

Yep. I also wrote note on Eternity Coin Slack workspace as there are some people trying to setup nodes last 2 days.
I hope they will read that and download upgraded wallet.

within 1-2 days there will be a normalization

Great, looks like we get a stable chain. But still too much old nodes, hope they will switch soon.

I have same:

{
  "version": 120105,
  "protocolversion": 70206,
  "walletversion": 61000,
  "balance": 0.00000000,
  "spysend_balance": 0.00000000,
  "blocks": 213009,
  "timeoffset": 0,
  "connections": 26,
  "proxy": "",
  "difficulty": 404.7126935880735,
  "testnet": false,
  "keypoololdest": 1506766687,
  "keypoolsize": 1004,
  "paytxfee": 0.00000000,
  "relayfee": 0.00010000,
  "errors": ""
}


and running upgraded version of node.

Not sure if this is the right hight:
{
  "version": 120105,
  "protocolversion": 70206,
  "walletversion": 61000,
  "balance": 0.00000000,
  "spysend_balance": 0.00000000,
  "blocks": 213009,
  "timeoffset": 0,
  "connections": 26,
  "proxy": "",
  "difficulty": 404.7126935880735,
  "testnet": false,
  "keypoololdest": 1508187095,
  "keypoolsize": 1001,
  "paytxfee": 0.00000000,
  "relayfee": 0.00010000,
  "errors": ""
}

26 connections, all with the new wallet. I think your chain is forked one.

I'm sorry I did not understand the question.

hight - 212777.
Nodes are incompatible, so there is a chain rejection with old wallets  

Is the mac wallet bounty still available?

What is the block hight on your pool? I think the problem is that still too many nodes are on a wrong wallet version and the chain is forking.
How about the eternity nodes. I can't see one working, all of them get rejected. Why?

The explorer block will be rebooted in the near future, the mining pool is working, new blocks are appearing steadily.

Blockchain
http://ent.eternity-group.org/blockchain.zip
http://ent.eternity-group.org/blockchain.tar.gz

I did that few time on node today with no luck. Will try one more time and see how it will go.
Synchronizing from zero now.

Hi Guys,

the block explorer seems to be stuck, too.
However I was able to install the wallets on two computers and one vps and all of them got synced to the same block (currently 212982).
This is what worked out for me:
- download the last wallet (Eternity Core:0.12.1.5)
- delete everything in your data folder except the wallet.dat and conf files (eternity.conf and eternitynode.conf)
- !!! DO NOT delete wallet.dat !!! You will lose all your coins if you do so!
- Put the list with nodes having the last client ((Eternity Core:0.12.1.5)) into your eternity.conf file. You can get the list from the block explorer or just copy and paste it from bellow.
- Start the wallet and let it sync. If it gets stuck for more than 15 min. just restart it.

Good luck!

List with actual nodes:
addnode=104.197.250.207
addnode=144.76.33.134
addnode=178.5.133.211
addnode=188.170.80.122
addnode=188.170.83.4
addnode=188.64.170.222
addnode=199.241.185.174
addnode=217.93.232.51
addnode=37.120.161.145
addnode=37.120.169.19
addnode=37.120.174.228
addnode=37.120.177.142
addnode=37.221.192.220
addnode=37.221.194.222
addnode=37.221.194.43
addnode=45.32.185.29
addnode=45.63.101.182
addnode=45.76.131.52
addnode=45.77.52.16
addnode=46.188.22.143
addnode=46.38.251.78
addnode=46.38.254.197
addnode=46.38.255.176
addnode=5.9.55.201
addnode=58.165.91.237
addnode=66.70.222.129
addnode=73.41.65.201
addnode=75.130.162.248
addnode=78.47.238.36
addnode=80.211.136.43
addnode=80.211.192.50
addnode=81.2.239.50
addnode=91.122.42.45
addnode=93.197.125.1
addnode=93.199.90.222
addnode=95.31.211.13

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.

`we stuck huh ?

What's wrong? Block explorer shows that latest block was like 12 hours ago

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.

Anobody update eternitynode to new version on vps?

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