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

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?

New Coin Name: no.  This project is for New England Coin. I do not see any better name for this project. 
New Design:  Yes.  I am not good designer.  I expect NENG community to grow  larger to take over the decision making on this kind of thing. As dev, I have to start to use
some graphic. This is decentralized coin and project, I fully foresee graphic design is most likely to be outside DEV team's domain  and to have major change in the future.

what do you think about new coin name and  design for NewEnglandcoin- ?

We are now 2691 blocks past the forked point.  The longer the block length over the forked position, then the more solid confirmation of the new dynamic anti-instant mining algo.

NENG blockchain is under attack from miner with IP from EU or UK.  Someone with old wallet version probably applied huge instant mining over last night, probably in private chain, then put the chain in public now.  Here is my wallet peerinfo:

{
"addr" : "206.189.113.92:6377",
"services" : "00000003",
"lastsend" : 1550544393,
"lastrecv" : 1550544393,
"bytessent" : 1920,
"bytesrecv" : 6156,
"blocksrequested" : 2,
"conntime" : 1550544357,
"version" : 70002,
"subver" : "/Satoshi:0.8.7.5/",
"inbound" : false,
"startingheight" : 276181,
"banscore" : 0,
"syncnode" : true
},
{
"addr" : "51.77.116.183:6377",
"services" : "00000003",
"lastsend" : 1550544359,
"lastrecv" : 1550544359,
"bytessent" : 229,
"bytesrecv" : 4465,
"blocksrequested" : 0,
"conntime" : 1550544358,
"version" : 70002,
"subver" : "/Satoshi:0.8.7.5/",
"inbound" : false,
"startingheight" : 280817,
"banscore" : 0
}


Note the total block length is only 276181,  the lower IP has 280817, so much longer block length.  This attack is not going to work because those extra blocks probably have many block times
within Spike difficulty (3 seconds) range and they are mostly likely obtained from per-forked old algo. Those extra  4,636 blocks,  or extra 92 million NENG will be deemed invalid in new v1.2.0 core wallet full node.  

Just a warning for big ASIC miners:   do not throw in big hash rate thinking that you are going to make killing on rewards because base difficulty is low.

current is boom time for small ASIC/GPU solo miners and CPU miners.   Because the base difficulty is very low,  big ASIC miners are not doing well, only getting some rewards.   In fact, I would say small ASIC miners and GPU miners obtain more rewards than big ASIC miners now.
This  is because of reset last night, the base diff is slowingly going up, but not very fast.  

When the base diff goes up in the future above 1, big  ASIC miners will do well then. Not for now.