Support Notice

Temporary loss of IPv6 connectivity

Temporary loss of IPv6 connectivity
Our IaaS provider, incorrectly disable our IPv6 ranges, and that provoked loss of reward for all customers. We will compensate all the losses.

EZ AI + PAC: perfect symbiosis

EZ AI + PAC: perfect symbiosis
After adjusts the EZ AI blended perfectly to the new version that solved many issues that were giving a hard time to our AI. We expect to see undesirable events in a rate lower than 0.02%. Orders on hold are good to be delivered soon.

DNS failure, lost reward - SLA approved with full compensation

DNS failure, lost reward - SLA approved with full compensation
Our SLA will compensate all users, paying the regular ZEN reward amount to the collateral wallet for the reward of April 11th, 2020. EasyDNS failed to recover our DNSSec key and the required amount of time for Horizen to re-check the DNS record with a new key led to the losses of a reward.

Multiple wallets getting corrupted at once

Multiple wallets getting corrupted at once
Many Horizen Wallets had unexpected behavior across multiple servers. Some nodes got in a fail loop leading to the reward loss. No compensation will be paid in this event.

Bitcoin Confidential Service Relaunch

Bitcoin Confidential Service Relaunch
The daemon wallet had 37MB and got corrupted. To resume cold staking, all users need to buy a new cold staking address and register a new cold stake node ($3/year).

Smartcash nodes with high freeze rate

Smartcash nodes with high freeze rate
There is high rate of Smartnodes freezing. Users must restart if required.

Polis update to 1.6.1 completed but not satisfactory

Polis update to 1.6.1 completed but not satisfactory
Deterministic masternodes is fully active, but the improper control of node connectivity allow the node to connect to old version and freeze the node. Users shall wait for the new version.

CRON: Blockchain fork made nodes require new restart

CRON: Blockchain fork made nodes require new restart
Users with a Crown masternode with the new start required status shall restart the node and check if it become ENABLED. Blockchain forks with an orphan chain are natural to Bitcoin forks, the 120 minutes to new start limit was deprecated by Dash to an adaptive model that take in account the number of blocks online to tag a node as expired. Hence a permanent solution can be applied via new daemon version with DIP003.

PAC with high number of nodes in an alternative chain

PAC with high number of nodes in an alternative chain
High amount of nodes with an alternative blockchain -- more than 30% according to our estimations. PoSe score will increase, wallets may not sync properly. No user action is required we can fix the masternodes from here. No user action is required.

Bitblocks chain fix

Bitblocks chain fix
Node owner must sync to the correct blockchain and restart the masternode

Zcoin with many orphan blocks - Some nodes need restart

Zcoin with many orphan blocks - Some nodes need restart
Some nodes got stuck in the blockchain split. Users need to restart the Znode as required. All the nodes are sync in the main chain already.

Nodes required a bootstrap and in the sequence New Start in less than 80 minutes

Nodes required a bootstrap and in the sequence New Start in less than 80 minutes
4 PIVX services within 64.44.137.[104--111], required New Start after a corrective bootstrap completed in less than 80 minutes. Affected user must restart. We will investigate this unexpected behaviour.