New wallet is currently in the works that will implement some changes to prevent such exploit that caused much havoc yesterday.Bittrex wallet is currently in maintenance mode. It will be back online in a day or so after the new wallet has been tested by devs.

In the meantime, make sure your wallet is at or just ahead of the MN info page's shown block and that the block hash matches.If not, you need to resync with a backed up chain or from scratch with following lines in the darknet.conf. (no other addnodes)

After yesterday affaire I have been trying to recover one of the MN in Paul's servers and I'm not capable of getting any connection. I have used a valid blockchain, one of the shared here, and I have added the addnode and bantime lines you comment here. Node started, stopped and started again an all the rest of usual tricks done. I'm stucked with no connections in block 272484. Any new ideas??Salute

I'm not ENT dev neither affiliated with EternityGroup in any way. Simply, the coin gives good returns.

After yesterday affaire I have been trying to recover one of the MN in Paul's servers and I'm not capable of getting any connection. I have used a valid blockchain, one of the shared here, and I have added the addnode and bantime lines you comment here. Node started, stopped and started again an all the rest of usual tricks done. I'm stucked with no connections in block 272484. Any new ideas??Salute

For those running multiple masternodes on a single Vultr server, have you noticed if they lag in block number quite often?e.g. Out of 5 instances, few often lag behind and show EXPIRED on my controller but catches up later on. Resource issue?

For those running multiple masternodes on a single Vultr server, have you noticed if they lag in block number quite often?e.g. Out of 5 instances, few often lag behind and show EXPIRED on my controller but catches up later on. Resource issue?

I am still seeing a bunch of wallets/nodes running on the bad chain. please check your block height and hash against either Presstabs BE, or the Stats page. The difficulty is also been lower than usual, so i assume many are not staking. feel free to stake away, and Obfuscate..

There will be a mandatory update coming shortly.. Keep an Eye out for our announcement.

New wallet is currently in the works that will implement some changes to prevent such exploit that caused much havoc yesterday.Bittrex wallet is currently in maintenance mode. It will be back online in a day or so after the new wallet has been tested by devs.

In the meantime, make sure your wallet is at or just ahead of the MN info page's shown block and that the block hash matches.If not, you need to resync with a backed up chain or from scratch with following lines in the darknet.conf. (no other addnodes)

New wallet is currently in the works that will implement some changes to prevent such exploit that caused much havoc yesterday.Bittrex wallet is currently in maintenance mode. It will be back online in a day or so after the new wallet has been tested by devs.

In the meantime, make sure your wallet is at or just ahead of the MN info page's shown block and that the block hash matches.If not, you need to resync with a backed up chain or from scratch with following lines in the darknet.conf. (no other addnodes)

I am still seeing a bunch of wallets/nodes running on the bad chain. please check your block height and hash against either Presstabs BE, or the Stats page. The difficulty is also been lower than usual, so i assume many are not staking. feel free to stake away, and Obfuscate..

There will be a mandatory update coming shortly.. Keep an Eye out for our announcement.

Hey guys. The update is more or less ready to roll out. I would be interested in the debug.logs from you guys who are still forking just to make sure that it is caused by the issue that is fixed in this new release. I would rather hold off another day or say and make sure that the problems are solved than have to have another release soon after because something got missed. Thanks.

When was the last time you confirmed that you were on the correct chain?Also, how are you confirming that you have really forked?

If you haven't resynced since last week with bantime of 50, your nodes would have forked last week when we had a network issue..I have many wallets & masternodes and none of them has had any issues since the resync few days ago using bantime=50 in conf..

Just to be clear, being few blocks behind is OK and isn't due to a fork. (it can take some time to catch up but it will eventually)