GAWMiner Hashlet Discussion Thread

I saw this when I logged into my Zencloud today:

Quote

A message from the CTO:

There are still remaining issues that are being worked on and resolved as quick as possible. We will also be reconciling old accounts that have not been paid out correctly due to merging/splitting/boosting/double hash.

Here are some of the remaining issues and statuses:

Double Hash not paying out correctly -Fixed -Need to reconcile all accounts for payout issues
Double Hash lasting longer than 12 hrs -Fixed
Caching issue on client browser (balance/HP/Miners) -Fixed by allowing the admin to clear the cache for a user
Ability to apply boost upgrade while mining a second pool (double hash) -Fixed
Withdraw fee not properly deducted -In progress
Customer perception issue when upgrading SHA hardware to Hashlets. Hardware to Hashlet upgrades reset the billing start date to 0 free days (by design) -Hashlets cannot have free days like hardware devices
Customer perception issue concerning when payouts occur for merging/splitting HashletsBefore, Hashlets that were merged/split were paid out immediately. This caused much confusion and extra bugs than anticipated. We have changed this so that merged/split Hashlets are calculated but not paid out until the following round of payouts are run
Some customers are not receiving the total sale price amount when an item is sold on the Hash Market -In progress
Double Hash events aren’t being removed after they end -In progress
Intermittent issue concerning splitting and merging Hashlets on some user accounts -In progress but still unable to replicate consistent behavior
Some customers are reporting that they are not always able to initiate certain Amps at certain legitimate times -In progress

On top of these items, there are about 20+ other small backend issues that have been worked on and are currently being addressed.

A note and apology from the CTO:

I am truly sorry for the events that have led to such poor performance from our software release this past week as well as the past few weeks. This has been embarrassing for me personally and for my company. We have grown past the point of being able to push minimally tested software and you have my word that any software from this point forward will go through a normal QA process in the staging environment before being released into production (as it should).

One of the struggles here has been that we feel the pressure to release Prime Hashlet features as promised. We have been working hard to do so and will continue to make good on this promise. We also realize that in order to improve the trust and confidence that you as the customer has in our ability to provide a stable and secure platform, is of the utmost importance above anything else.

That said, the changes mentioned above may delay the rapid feature releases but I believe it is more important to be sure customers are taken care of by ensuring new features/upgrades get paid out correctly in order to preserve our company brand and integrity.

Thank you for your business and continued support during this challenge. I will update this post when we have more information on the remaining items (along with additional ones that appear during the week).