Support Notice

PivX Update to 3.3.0 and EZ Sync Keeper

PivX Update to 3.3.0 and EZ Sync Keeper

PivX daemons where update to v3.3.0, clients MUST update and restart the node on the client wallet. EZ Sync Keeper is working perfectly with PivX and already saved some rewards from blockchain fork.

 

Update PolisCore v1.4.16a

Update PolisCore v1.4.16a
100% successful updated of Polis daemons to v.1.4.16a, no action is required from users. EZ Sync Keeper is enabled and already saved some rewards

Lack of IPv6 connectivity - Courtesy credit

Lack of IPv6 connectivity - Courtesy credit
Courtesy credit will be paid to 6 Secure Horizen nodes affected nodes by 4 hours of connectivity loss.

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

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.