Support Notice

CRON: Blockchain fork made nodes require new restart

CRON: Blockchain fork made nodes require new restart
Users with a Crown masternode with the new start required status shall restart the node and check if it become ENABLED. Blockchain forks with an orphan chain are natural to Bitcoin forks, the 120 minutes to new start limit was deprecated by Dash to an adaptive model that take in account the number of blocks online to tag a node as expired. Hence a permanent solution can be applied via new daemon version with DIP003.

Bitblocks chain fix

Bitblocks chain fix
Node owner must sync to the correct blockchain and restart the masternode

Zcoin with many orphan blocks - Some nodes need restart

Zcoin with many orphan blocks - Some nodes need restart
Some nodes got stuck in the blockchain split. Users need to restart the Znode as required. All the nodes are sync in the main chain already.

PIVX 4.0 Mandatory update

PIVX 4.0 Mandatory update
PIVX Wallet update to 4.0 with required user action: restart the masternode after server update (Saturday, December 21st at 1:00 PM GMT)

ZCoin Emergency Mandatory update + user action

ZCoin Emergency Mandatory update + user action
Zcoin wallet requires update and user action in the console to allow sync after block 220754. ZNode is required after the update for many node owners.

Nodes required a bootstrap and in the sequence New Start in less than 80 minutes

Nodes required a bootstrap and in the sequence New Start in less than 80 minutes
4 PIVX services within 64.44.137.[104--111], required New Start after a corrective bootstrap completed in less than 80 minutes. Affected user must restart. We will investigate this unexpected behaviour.

Smartcash blockchain freeze at block height 1239298

Smartcash blockchain freeze at block height 1239298
443 Smartnodes got stuck in the block 1239298. Some nodes may require new start as the node restart took about 50 minutes to be completed.

Smartcash nodes restart issues

Smartcash nodes restart issues
The Smartcash wallet replaced the node config files by empty ones in about 2% of the Smartnodes that we host. The lack of Smartnode informations lead to the New_Restart_Required with the need of admin (configuration) and owner intervention (restart).

PivX protocol change completed (v 3.4)

PivX protocol change completed (v 3.4)
PivX update in our servers to v. 3.4 completed . Users must update to the v. 3.4 and restart the node to resume rewards.

Multiple join-split failures, global rescan enforced

Multiple join-split failures, global rescan enforced
To prevent/mitigate losses a restart with rescan will be enforced to all Horizen Nodes. Compensations will NOT be credited since it is unpredictable and it is impossible to prevent, hence excluded from our SLA

Smartcash - Orphan chain detected - Restart required

Smartcash - Orphan chain detected - Restart required
21 Smartnodes got stuck in the an orphan blockchain, they are restricted to two IP spaces: [64.44.137.{2--34}] and [64.44.142.{52--71}], affected nodes require new start. This event is NOT covered by SLA.

Another Polis Mandatory Update

Another Polis Mandatory Update
Servers updated to the version 1.4.15 that that shall solve sync problems. Users MUST install new wallet, do bootstrap and restart the masternode.