Support Notice

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.

Crown daemon update v. 0.13.4

Crown daemon update v. 0.13.4
Non-mandatory update with good improvements. No restart is necessary or expected.

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.

Another Polis Mandatory Update

Another Polis Mandatory Update
Servers updated to the version 1.4.15 that that shall solve sync problems. Users MUST install new wallet, do bootstrap and restart the masternode.

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.

 

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.