We managed to sync all Smartnodes to 1.3.3 (358 IPs). Users may need to perform actions to restart Smartnodes. Smartcash support will be limited until Sept 22nd to compensate the previous workload.
Our server CHI02 (the very same one that act as a hub for shared date) freezed by 2020-09-01 10:42:59 CDT. many clients of legacy masternodes (ie. non deterministic masternodes) will need to restart its nodes. The cause of freeze is a bad piece of RAM.
Smartnodes are freezing in the block 1761798, reindex, restart, or snapshot reload did not fix. All Smartnodes will be down until we get a fix from the Smartcash team.
The super server CHI12, become unresponsive at 14:35:46 CDT, it was running fine since started servicing by Feb 07 13:54:51. Simple consensus masternodes will require a new start. Deterministic masternodes will not be affected.
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.
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.
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.
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).
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.
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.
- Page 1 of 3
- Next page