Quote from: polis_social on January 03, 2018, 12:23:51 AM

Quote from: Flenger on January 03, 2018, 12:21:09 AM

Quote from: polis_social on January 03, 2018, 12:00:55 AM

Everyone please ensure you are on the right chain. http://block.polispay.org and https://coinsmarkets.com/walletstatus.php?ticker=POLIS show the correct blockheight.

If you are having trouble syncing to the right block, use the following for your .conf file:

Code:

maxconnections=256
connect=35.227.49.86:24126
connect=192.243.103.182:24126
connect=185.153.231.146:24126
connect=91.223.147.100:24126
connect=96.43.143.93:24126
connect=104.236.147.210:24126
connect=159.89.137.114:24126
connect=159.89.139.41:24126
connect=174.138.70.155:24126
connect=174.138.70.16:24126

Then clear old %appdata% except wallet and configs and reindex (on linux its the .poliscore folder).

The "connect" command forces the client to use only the listed nodes, whereas the "addnode" command does not force the client to use the listed nodes. So "connect" will force the right chain, but it will reduce your connections as the client will not connect to anything else. Once you are on the right chain, you can switch from "connect=" to "addnode=".

Credit to our amazing Discord community for these instructions and for banding together to nip a potential fork problem right in the bud.

Those of you with missing transactions: re-sync your wallet once you are on the right chain.

Those of you with missing pool payments: see @grendel25's post above.

Other masternodes will not receive coins? Other masters will not receive coins? Those that are not on the list.

All masternodes that are on the right chain and set up properly will receive rewards. The .conf setting above just ensures that the client syncs to the right blockchain.

In the correct network node 46.36.216.183:24126 ?

Flenger

Posts

Merits