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.
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 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.
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