Quote from: crowi on October 17, 2017, 07:34:27 AM

Quote from: EternityGroup on October 17, 2017, 12:25:59 AM

Quote from: crowi on October 16, 2017, 07:15:01 PM

My Unomp is sticking at:

"[2017-10-16 21:11:46.459] [DEBUG] [default] - Pool eternity Thread 1 Downloaded 100.00% of blockchain from 8 peers"

and doesn't start the ENT threads. Sad

Everything else is fine, new core and the js snipplet from above added.

Any ideas?

It is enough to add the above code, for the normal operation of the pool. As an example, http://pool.eternity-group.org works great.

All mined Blocks get orphaned, mining on the new core eternity-0.12.1.5 and with the code implemented.

see: http://37.120.182.204:8081/stats

That is what Im talking about, all normal mined blocks start confirming and get rejected afterwards.
Looking on the log file those blocks were replaced by other and mostly several blocks at once (I saw up to 10 blocks replaced on this way).
We have here an fishy miner or something is wrong with code.

Futtermore, dev what men all the status on the eternity nodes: pre-enabled, has to be restarted and so on. Im trying to start a node since 2 days without success. And my nose configuration is ok. At least says mastermind successfully started and after a while goes to needs to be restated status. What does this mean?
Thanks.

Edit: looking on the block explorer only one address is mining all the blocks. Quite strange if there are several pools and self mining going on!