Support Notice

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.

 

Service limited - Nodes information are unavailable for the user

Service limited - Nodes information are unavailable for the user
EZ Masternodes node database is temporary non-responsible, during that none of the running nodes will be affected but we will not be able to deliver new orders or even show details about running orders. We already got in touch with our provider and hope for fast solution.

Enforced Polis Protocol upgrade - 70215

Enforced Polis Protocol upgrade - 70215
Polis team release the new daemon version v.1.4.13, forcing the protocol bump to 70215. As a consequence wallet update and masternode restart is required.

Polis Mandatory Update v1.4.12

Polis Mandatory Update v1.4.12
We just started another Mandatory Update of Polis for v1.4.12. User may expect Sentinel ping Expired, Expired, but NOT New Start Required in the next 4 hours. Please report if your node got the NSR status.

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.

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

Crown is CPU and RAM hungry now! Costs will get higher! --- Not anymore!

Crown is CPU and RAM hungry now! Costs will get higher! --- Not anymore!
UPDATE: prices are back to normal since there is a preview of fix   The last version increased the RAM usage, now a Crown SystemNode almost require...

Server update for Polis Core v1.4.11 - Mandatory

Server update for Polis Core v1.4.11 - Mandatory
We shall be performing the server update for all of our Polis nodes according to the team requirements today (April/17/2019)! This is a Mandatory u...

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.