Quote from: VirtualCloudMining on May 04, 2015, 11:02:15 PM

Quote from: TeamNeutron on May 04, 2015, 09:59:01 PM

Hey folks,

The forking issues has been fixed. Please download the new wallet from the OP. In addition, don't forget to do a full resync from scratch. That means delete everything except for wallet.dat, and then start your wallet. I have removed the revamped wallets as they are of an older protocol. Remember, do not click any download links replied to this thread, as most likely they are phishing links.

Regards,
Team Neutron

Quote from: cryptowest on May 04, 2015, 03:23:42 AM

Quote from: VirtualCloudMining on May 04, 2015, 02:50:49 AM

The coin Neutron have had trouble with synching. This is claimed to be becaused of code taken from this coin Positron. Here is tips to correct the code.

I originally added a parameter to the function to pass the block height, but later found it wasn't needed during my testing.

TRON hasn't had any syncing problems, we had a short fork during the POW phase but I resolved it with ocminer from Suprnova within a few minutes.

The more likely problem for your sync is the outgoing maxconnections variable in net.cpp. The defaults are really low and seednodes and pools should always increase them. Neutron's default outgoing connection # is only 16:

https://github.com/teamneutron/Neutron/blob/master/src/net.cpp#L28

The reason a lot of these high POS coins are having problems connecting or syncing is because so many wallets are staking now and demanding more node connections. That variable needs to be increased to like 1024 for your main seed nodes, then recompile.

I'm glad to see someone took over the failing neutron project and made something of it.

Good luck.

Why wasn't it necessary to increase the number of outgoing connections?

Not every wallet needs that much outgoing connections, just the seednodes...