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.

PAC with high number of nodes in an alternative chain

PAC with high number of nodes in an alternative chain
High amount of nodes with an alternative blockchain -- more than 30% according to our estimations. PoSe score will increase, wallets may not sync properly. No user action is required we can fix the masternodes from here. No user action is required.

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.

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.

Our IaaS is excelent, but nothing is perfect: 3h downtime across all servers

Our IaaS is excelent, but nothing is perfect: 3h downtime across all servers
Nexeon had IPv6 connectivity issue across all of our servers, that took a bit more than 2h to be solved. Full compensation for Horizen Nodes is in place.

Lack of IPv6 connectivity - Courtesy credit

Lack of IPv6 connectivity - Courtesy credit
Courtesy credit will be paid to 6 Secure Horizen nodes affected nodes by 4 hours of connectivity loss.

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.

Protection fault, 35 nodes off: full compensation + bonus to affected users

Protection fault, 35 nodes off: full compensation + bonus to affected users
35 nodes in the range sv1508--sv1540 and sv1811--sv1820 went off and lost the reward. We will provide automatic compensation above the expected earnings: Super $4.00; Secure $0.80. New preventives measures will be set in place soon.

Fixing BC Cold Stake with EZ Masternodes

Fixing BC Cold Stake with EZ Masternodes
To resume BC cold stake at EZ-MN the user will have to replace the remote node stake address. We committed to provide FREE cold staking service continuity. The failure was addressed and we committed to execute some task to prevent the event recurrence.

Bitcoin Confidential wallet.dat fault, staking stopped

Bitcoin Confidential wallet.dat fault, staking stopped

Our staking node is non-operational. Retrieved info from the running daemon on our server node and indicated that it is running with a blank wallet.dat (no stacking addresses in there). Unfortunately the backup file was the same information (we do not have an older version). We shall return with more information in the next 24h.