Quote from: RizSphere on February 18, 2019, 04:11:18 PM

Quote from: honglu69 on February 18, 2019, 05:30:50 AM

CPU mining were back just minutes ago. This was likely to be difficulty reset period. It used to be super fast movement, 1 second per block for ASIC miners for 1440 blocks.
Because v1.2.0 upgrade removed instant mining, the reset took much longer to the point of slow movement on very low diff.

But now the base diff is up so that CPU mining is back into play.

I started mining this coin about 14 hours ago, using a Rock64 (had to use a modified 'atomic_pointer.h to compile for the ARM processor) and have mined 21 blocks so far.

I just want to be sure I'm on the correct chain... block number and nethash matches the explorer listed in original post:

   "blocks" : 275437,
   "currentblocksize" : 1000,
   "currentblocktx" : 0,
   "difficulty" : 0.00024414,
   "errors" : "",
   "generate" : true,
   "genproclimit" : 4,
   "hashespersec" : 4093,
   "networkhashps" : 12837,
   "pooledtx" : 0,
   "testnet" : false

Networkhaskps seems rather low... and looks to be continually dropping.

Also, does a "miningprivkey= " entry in the .conf file work the same as other bitcoin derived alts (to mine to one address)?

Edit: should have included version - is this correct?
   "version" : 80705,
   "protocolversion" : 70002,
   "walletversion" : 60000,

Looks normal so far. Try to search one block hash against the explorer, make sure the block is there:
http://nengexplorer.mooo.com:3001/

The block diff has multiple levels. One is base level, currently at 0.000772. Another is CPU mining level, which is 0.00024414. Last night for a while the base level was same as
CPU diff level. There is Spike level 244,000 difficulty, which is rare. So far no block was mined on spike diff level yet, in theory it could, but not expected to happen.

The version is still "version" : 80705. For two reasons we did not change this. One is that this is fork off version from Litecoin (or same from bitcoin) that our dynamic diff algo is based on.
The second is that we do not want wallet version to be disclosed to hackers in traffic. Our network is safer if potential attackers do not know peers software versions. We also expected to update our wallet versions frequently in 2019 and beyond. Each wallet update transition period has potential to be attacked by 51% attackers.