Topic: [NENG]Nengcoin - Litecoin on Steroids - Scrypt for All Miners - page 40. (Read 46901 times)

The wallet "out of sync" warning should be gone for now.  The public chain block length is already longer than that of bad nodes.  Here it is from my wallet getpeerinfo command,
This is one of the bad node with 284124 blocks:
{
"addr" : "51.77.116.183:6377",
"services" : "00000003",
"lastsend" : 1550891119,
"lastrecv" : 1550891119,
"bytessent" : 13018,
"bytesrecv" : 146422,
"blocksrequested" : 8,
"conntime" : 1550888808,
"version" : 70002,
"subver" : "/Satoshi:0.8.7.5/",
"inbound" : false,
"startingheight" : 284124,
"banscore" : 0
},

The current block explorer length is 285338.

Dev Policy on Checkpoints on NewEnglandcoin

NewEnglandcoin v1.2.1 update is checkpoints security upgrade to secure the blockchain on hard fork.  Checkpoints technique is controversial method in blockchain world.
In fact, bitcoin itself has not performed checkpoints for a long long time.  The issue with checkpoints is that decentralization of  a coin means that nobody has central control on blockchain.
Certainly NENG dev does not intend to control NewEnglandcoin blockchain and merely view ourself as tech support.  However, frequent checkpoints on a coin means the coin is centrally controlled by dev team.

In order to fulfill decentralization goal of NewEnglandcoin, we as dev do not plan to frequently apply checkpoints technique.  We only intend to apply that on hard fork in the future.
Even for hard fork, we do not intend to impose our forking view by ourselves.  Any future hard fork will have several weeks to a month of pre-annoucement on hard fork in bitcointalk or discord for the intention.  We will also issue release of new software version one week in advance in order for members to prepare fork. The new release will have 1 week compatible blockchain with older version and will have fork a week later.   Therefore, 1 week to 1 month time will be available for NENG members to express any opposing opinions on fork, and there will be minimum of 1 week period to allow DEV to cancel or modify hard fork plans in the future.   We believe such procedure in place on NewEnglandcoin  from now on will surely confirm that
any future checkpoints on hard fork is not indication of any centralization.  NewEnglandcoin will continue to be a decentralized cryptocurrency and controlled by nobody just like bitcoin, litecoin or dogecoin.
  
The next hard fork or potentially a checkpoint on NewEnglandcoin will be Q3 of 2019, to be determined by our research on the results of v1.2.x release.

Congrats. Just checked my 2 core Linux running cheetah for 17 hours, mined 9 blocks.  I thought CPU were not doing well, you scooped almost all!

really my asic L3+ produces very few blocks! but mining cpu I got for 8 hours 400 + blocks

For the first time tested out GPU solo-mining.  Just find out that GPU solo-mining now can make killing on NENG block rewards, getting blocks pretty much very 10 seconds.
Actually GPU solo mining is much better than even small ASIC USB stick mining.  Small ASIC probably only get one block per two minutes.

The breakdown of three groups really should be GPU/CPU/ASIC.  Now is the time for GPU solo miners.  Added "GPU mining" in the title of this thread.

Update on v1.2.1 new version mining situations now:

I do not have thorough research on distribution of mining rewards, just few observation and a guess, which most likely to be close to truth:

Break down of big ASIC miners vs  small ASIC/GPU  vs CPU miners

 Right now the winner is small ASIC or GPU solo miners.  My guess is that today
50% of blocks were mined by small ASIC solo miners or GPU solo miners.   This group of miners are big winner today.  This is unexpected in that the new algo is much more
big ASIC resistant than I originally thought.  

big ASIC or big POOL miners probably gets 30% of blocks mined now.

CPU miners may get 20% of total blocks mined for now.  


Previously  Dynamic Diff v1.1.x was never friendly to small ASIC or GPU miners. It was either big ASIC or CPU miners.  Now things changed dramatically on the mining situation of
NENG blockchain.  This change of trend was expected in whitepaper design. But the degree of change so far exceeded original plan.

Updated current "getpeerinfo" from my wallet, in case some one needs to do "addnode" for IPs to sync the wallet with good nodes:


Good nodes out of total 16 peers, bad nodes manually removed by myself



"addr" : "206.189.113.92:6377",
"addr" : "97.73.84.138:37036",
"addr" : "217.9.123.38:57879",
"addr" : "84.59.246.89:54293",
"addr" : "196.52.2.116:64279",
"addr" : "217.9.123.38:65528",
"addr" : "76.70.51.130:50781",
"addr" : "76.70.51.130:58690",
"addr" : "81.191.6.111:45699",
"addr" : "104.129.6.156:38008",
"addr" : "212.56.109.179:55000",
"addr" : "76.70.51.130:38750",


To addnode in order to sync wallet better, do this in GUI wallet  click HELP -> Debug Window -> Console , 

one example type in below commands manually for one IP, do it for several node IPs until wallet is good at syncing:

Try to search the block chain explorer for the transactions:

http://nengexplorer.mooo.com:3001/


 Hard Fork was announced for software release 1 week before the event actually happened, 1 month and half after whitepaper v1.0 was announced on this.  Anything mined in old wallet version after hard fork is no longer valid, waste of energy.  There could be 10 to 20 blocks compatible after fork with old wallet, but not likely to be more blocks than that.

You can re-sync the chain with new version of wallet software on the same backed up wallet file.  Make sure to back up wallet file first.   Those mined coins after fork will be gone if  you were mining the dead chain.  Old wallet file is always good to use up to the fork.  

Before I updated the wallet, I sent some coins to the shoreline, the wallet appeared as a validated transaction, but the coins were not credited to me on the shoreline. Then I updated the wallet and can not synchronize more, and if I leave mining with the cheetah, he never stops mining, he keeps mining all the time and I do not even know if I'm finding anything. For txid I did not find anything in the block explorer, but the coins left my wallet and I do not know where they are.

My wallet shows that "out of sync" zero hour behind. But mining is normal. Ignore the out of sync as this is mainly that bad node still has 300 blocks longer, not giving up.  The wallet and network are fine.

Fixed issue. The seednode that ShorelineCrypto operates was shut down by cloud provider due to billing payment issue. The issue was resolved and seednode is up.

Loss of seednode plus the.bad node not giving up was cause of network problems. Now all should be good. Mining is normal on my side.  The bad node is still there but it won't  affect mining or anything else

I updated the wallet and then the wallet does not sync anymore. I can not mine because the wallet does not sync.

The bad nodes are attacking the network. Still not giving up. Make sure to update to v1.2.1 wallet and CPU mining with cheetah.

Hi, here the wallet is not syncing, can you send the nodes or the conf file?

Thanks

Sometimes GUI wallet may show out of sync because only the bad nodes are connected. To resolve this, just type addnode in GUI window debug command as below:
type in few words using one good node as example:

 addnode 212.92.112.191:57775 add

Just pick above good nodes, or from explorer network, add some good nodes, the wallet will be fine, "out of sync" will go away.

snapshot of current NENG blockchain status, 22 peers in my wallet, the three (shown below top three) nodes are bad nodes with  281822 blocks:
"addr" : "51.77.116.183:53714",
"addr" : "222.105.128.90:54057",
"addr" : "217.99.103.36:49312",
Avoid addnode for above 3 IPs.

Majority nodes are good nodes.  So far so good.  The corrupted nodes are stale, not moving at 281822.  The good nodes are moving along. One more day the public
node will have longer bockchain length than the corrupted node.

getpeerinfo


22:00:53

[
-------skipped -----------
{
"addr" : "51.77.116.183:53714",
"services" : "00000003",
"lastsend" : 1550717964,
"lastrecv" : 1550716896,
"bytessent" : 7937,
"bytesrecv" : 7742,
"blocksrequested" : 6,
"conntime" : 1550716024,
"version" : 70002,
"subver" : "/Satoshi:0.8.7.5/",
"inbound" : true,
"startingheight" : 281822,
"banscore" : 0
},
{
"addr" : "222.105.128.90:54057",
"services" : "00000003",
"lastsend" : 1550717964,
"lastrecv" : 1550716896,
"bytessent" : 6894,
"bytesrecv" : 1433,
"blocksrequested" : 3,
"conntime" : 1550716216,
"version" : 70002,
"subver" : "/Satoshi:0.8.7.5/",
"inbound" : true,
"startingheight" : 281822,
"banscore" : 0
},
{
"addr" : "217.99.103.36:49312",
"services" : "00000003",
"lastsend" : 1550717964,
"lastrecv" : 1550716996,
"bytessent" : 7320,
"bytesrecv" : 5694,
"blocksrequested" : 5,
"conntime" : 1550716256,
"version" : 70002,
"subver" : "/Satoshi:0.8.7.5/",
"inbound" : true,
"startingheight" : 281822,
"banscore" : 0
},
{
"addr" : "76.70.51.130:37418",
"services" : "00000003",
"lastsend" : 1550717964,
"lastrecv" : 1550717029,
"bytessent" : 5584,
"bytesrecv" : 229,
"blocksrequested" : 0,
"conntime" : 1550717029,
"version" : 70002,
"subver" : "/Satoshi:0.8.7.5/",
"inbound" : true,
"startingheight" : 280303,
"banscore" : 0
},
{
"addr" : "212.56.109.179:47844",
"services" : "00000003",
"lastsend" : 1550717964,
"lastrecv" : 1550717039,
"bytessent" : 5584,
"bytesrecv" : 229,
"blocksrequested" : 0,
"conntime" : 1550717039,
"version" : 70002,
"subver" : "/Satoshi:0.8.7.5/",
"inbound" : true,
"startingheight" : 280303,
"banscore" : 0
},
{
"addr" : "104.129.6.156:34714",
"services" : "00000003",
"lastsend" : 1550717964,
"lastrecv" : 1550717056,
"bytessent" : 5499,
"bytesrecv" : 229,
"blocksrequested" : 0,
"conntime" : 1550717056,
"version" : 70002,
"subver" : "/Satoshi:0.8.7.5/",
"inbound" : true,
"startingheight" : 280303,
"banscore" : 0
},
{
"addr" : "139.180.209.194:41826",
"services" : "00000003",
"lastsend" : 1550717964,
"lastrecv" : 1550717060,
"bytessent" : 5554,
"bytesrecv" : 229,
"blocksrequested" : 0,
"conntime" : 1550717059,
"version" : 70002,
"subver" : "/Satoshi:0.8.7.5/",
"inbound" : true,
"startingheight" : 280303,
"banscore" : 0
},
{
"addr" : "81.191.6.111:53849",
"services" : "00000003",
"lastsend" : 1550717964,
"lastrecv" : 1550717093,
"bytessent" : 5584,
"bytesrecv" : 229,
"blocksrequested" : 0,
"conntime" : 1550717092,
"version" : 70002,
"subver" : "/Satoshi:0.8.7.5/",
"inbound" : true,
"startingheight" : 280303,
"banscore" : 0
},
{
"addr" : "76.70.51.130:52016",
"services" : "00000003",
"lastsend" : 1550717964,
"lastrecv" : 1550717119,
"bytessent" : 5584,
"bytesrecv" : 229,
"blocksrequested" : 0,
"conntime" : 1550717119,
"version" : 70002,
"subver" : "/Satoshi:0.8.7.5/",
"inbound" : true,
"startingheight" : 280303,
"banscore" : 0
},

{
"addr" : "95.47.170.115:53501",
"services" : "00000003",
"lastsend" : 1550717964,
"lastrecv" : 1550717964,
"bytessent" : 8788,
"bytesrecv" : 5822,
"blocksrequested" : 6,
"conntime" : 1550717224,
"version" : 70002,
"subver" : "/Satoshi:0.8.7.5/",
"inbound" : true,
"startingheight" : 280304,
"banscore" : 0
},
{
"addr" : "212.92.112.191:57775",
"services" : "00000003",
"lastsend" : 1550717964,
"lastrecv" : 1550717964,
"bytessent" : 7767,
"bytesrecv" : 4740,
"blocksrequested" : 6,
"conntime" : 1550717232,
"version" : 70002,
"subver" : "/Satoshi:0.8.7.5/",
"inbound" : true,
"startingheight" : 280304,
"banscore" : 0
},
{
"addr" : "217.9.123.38:61853",
"services" : "00000003",
"lastsend" : 1550717964,
"lastrecv" : 1550717964,
"bytessent" : 9352,
"bytesrecv" : 2134,
"blocksrequested" : 5,
"conntime" : 1550717236,
"version" : 70002,
"subver" : "/Satoshi:0.8.7.5/",
"inbound" : true,
"startingheight" : 280304,
"banscore" : 0
},
{
"addr" : "97.73.84.138:37013",
"services" : "00000003",
"lastsend" : 1550717965,
"lastrecv" : 1550717965,
"bytessent" : 7275,
"bytesrecv" : 991,
"blocksrequested" : 8,
"conntime" : 1550717268,
"version" : 70002,
"subver" : "/Satoshi:0.8.7.5/",
"inbound" : true,
"startingheight" : 280305,
"banscore" : 0
}
]

The right chain is http://nengexplorer.mooo.com:3001/

The v1.2.1 is to ensure hard fork with checkpoints.

Some miner in EU or UK mined huge mount of corrupted chain in private.   Yesterday, the public chain made 1000 blocks longer,  the dead chain moved 500 blocks longer yesterday.
Today it appears that the public chain is moving along normally, the dead chain is giving up.

The dead chain miner could be unintentionally, but I would not be too naive about it.  ShorelineCrypto also had huge amount of deposit of NENG last couple of days, possibly from "corrupt" chain to do %51 attack.  Those coins were not confirmed, will go away as "dead" chain or invalid deposit after several days.  We actually got email from a long corrupted email addressed user questioning why his deposit of NENG did not go through.  Obviously some attempt to cheat the system, but failed.

now you have 2 chain
where is right chain

NewEnglandland v1.2.1 released at : https://github.com/ShorelineCrypto/NewEnglandCoin/releases

This is security update to have checkpoints on block 278008 to secure the hard fork.  This is recommended for upgrade for all users.

With base difficulty at this low at 0.00031592 , I would recommend all CPU miners directly mine from wallet without Cheetah software.  Just use GUI wallet, -> Click "Help" in menu,
click "Debug window",  click "Console",  type in below command:
setgenerate true


To stop mining, type in below:
setgenerate false