Support Notice

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.

 

The SAME Horizen Node goes rougue and claim 80GB of data in 1h

The SAME Horizen Node goes rougue and claim 80GB of data in 1h
20 Horizen nodes in the IP range 64.44.137.[124--143] went down, yesterday due to the same Horizen Node requesting too much resources. It is all been fixed, and we will offer a full compensation for users that endured loss of rewards in there.

Horizen - daemon go rougue

Horizen - daemon go rougue

A Horizen node generated a 42GB database folder and that made the plataform to shutdown all the processes using the same code for safety. Once we evaluated the source of the issue all the operations were resumed. This event will NOT be covered by our SLA since it was cause by the project code unexpected behaviour.
debug.log file will be preserved and can be requested by the users for further analysis.

Miss configuration of 15 Horizen Daemons

Miss configuration of 15 Horizen Daemons

One of our servers had a fault maintenance in the IO restriction. This lead to an initial lost of sync and later our attempt to solve the problem made it worse.

Some nodes in the range sv1541 to sv1555 will not be able to sync before 1 hour, and some not before 2 hours. So, it may lead to a rewad loss for some users.

Complete refund for endured losses will be performed upon user request.

daemon memory leak

A daemon bad behaviour "pushed" 30GB of daemons from RAM to SWAP that lead 22 Smartnodes (among 200+) to get the New Start Required Status. This was not caused by our team and nothing in that is affordable by our cost prediction could be performed to prevent this. This event will NOT lead to any compensation. Affected users shall restart the daemons