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

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

Yes.

Does this tarde only on shorelinecrypto?

To me, this project seems to deriving huge profits for traders as well as investors. Also, if you can share some major advantages of this project, it will be really great. We also have a token named as ‘OXY2’ token which is currently running through phase 2. Cryptoxygen is the ideal solution to what current crypto-users look out for on the crypto market.

Advertising, or more proper word, marketing.  Yes, you raised very good point on lack of attention on NENG.

At initial dev stage, we have been focusing mainly on "tech" side, or specifically "security", or "decentralization" side of this coin. To make NENG a solid footing.
In my opinion, an altcoin has no future if the 51% attack risk or security of a coin issue is not addressed.  Bitcoin, or even Litecoin/Dogecoin are so much better,  much more secure than most other small altcoins due to their huge energy cost mining barrier. That is why my focus has been on that up to date.

I think after v1.2.0 upgrade,  burden on pure "tech" side is lessened.  The focus would be shifted toward more toward marketing of this coin.  I would hope community members or investors can pick up more actual marketing with word of mouth tasks.  For dev point of view, I am starting to think of marketing related dev on NENG, for example, a reward system on NENG because people love reward.  Masternode coins is kind of reward, Electroneum cell phone mining is essentially a reward.  Coinbase paid $100 million for earn.com, essentially earn.com is watching some videos and get some crypto reward.

We will develop a kind of reward system around NENG on dev work.  It is too early and I am still researching and exploring this field.  I can not say too much on that. But after 2019 Q2,  dev work will most likely shift toward "marketing" heavy work such as reward based work to attract more users and get bigger attentions.  Just pay attention to this bitcointalk ann and discord for our future announcement on NENG new directions.

I see that you are developing, but very slowly.
You should pay more attention to advertising!
Where can people find out that your coin is better and faster?