Support Notice

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.

Polis update to 1.4.18

Polis update to 1.4.18
In order to fix the New Start Required issue we update our to the latest version. Users must do a wallet update and restart the node. Now our serve...

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.

 

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.

Server Update - RAID 0

Server Update - RAID 0
We are updating the service for RAID 0. Some interruption in the tolerance windows is expected.

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

Crown Emergency update - Mandatory

Crown Emergency update - Mandatory
To fix the network and allow mining via PoS, the Crown team release a new mandatory daemon version (0.13.2.0). All users MUST download and install in order to be able to start the nodes.

Crown Daemon scheduled update to v.0.13

Crown Daemon scheduled update to v.0.13
Our servers will perform the mandatory update to the new Crown daemon v 0.13 at April 5th, 2019, 00:01 UTC. This update affect all types of nodes as it is a protocol update. Users must update and cast a new start on nodes after the server update.

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