Support Notice

DNS failure, lost reward - SLA approved with full compensation

DNS failure, lost reward - SLA approved with full compensation
Our SLA will compensate all users, paying the regular ZEN reward amount to the collateral wallet for the reward of April 11th, 2020. EasyDNS failed to recover our DNSSec key and the required amount of time for Horizen to re-check the DNS record with a new key led to the losses of a reward.

Multiple wallets getting corrupted at once

Multiple wallets getting corrupted at once
Many Horizen Wallets had unexpected behavior across multiple servers. Some nodes got in a fail loop leading to the reward loss. No compensation will be paid in this event.

Horizen 2.0.2 - Mandatory update

Horizen 2.0.2 - Mandatory update
All Horizen nodes were successfully updated in the very same moment. User MUST check the tracker to be sure that the re connection was also success!

June Compensations for Super and Secure nodes

June Compensations for Super and Secure nodes
During June, 2019 we had an exceptional number of compensations for Horizen: 109 for Secure nodes and 15 for Super Nodes. All affected nodes will be over compensated in 25% over the maximum value of Horizen in June ($11.67).

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

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.

Server upgrade and dadfailed on child bug lead to some reward loss

Server upgrade and dadfailed on child bug lead to some reward loss

EZ Masternodes is moving all its nodes from Dual E5-2650v2 128GB SSD servers to Dual E5-2650v2 256GB 3D SSD with Raid 0. During the process we had an IPv6 connectivity issue, after moving the nodes, in the new server, an Ubuntu confirmed bug did not allowed us to attach some IPv6 (dadfailed on child interface error). As result  daemons that rely on IPv6 in the range 2602:ffc8:1:2::3:100/64 to 2602:ffc8:1:2::3:154/64 may endure reward loss, but we decide to compensate users.

Horizen Mandatory Update

Horizen Mandatory Update

Horizen daemon will be update today to the version ZEN 2.0.17, node disconnection is expected, simultaneously we will perform a fresh bootstrap in all nodes to provide better network healthy and consensus. Some users may need to update they wallets to be able to move funds again.

 

Daemon Memory leak - Preemptive maintenance

Daemon Memory leak - Preemptive maintenance

Our staff noticed some Horizen daemons requesting almost 5G of RAM of resident memory and almost 30GB of virtual memory. We had to impose a regular daemon restarting routine. Many users may notice 6-12 minutes of disconnection in their nodes until this is improved by the team

Upgrade Maintenance at SuperServer

A maintenance operation caused a 10-20 minutes downtime for Horizen Nodes in the interval sv1571.ez-mn.net to sv1585.ez-mn.net. SLA compensation offered

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.