Ok, I can easily explain what's going on here. The ZenController was initially developed for GAW Miners to accompany their Generation A devices. GAW used these controllers in their labs and on their own devices for some time to test them and perform quality control before shipping them to customers.

It is not uncommon in this industry for a manufacturer to ship a controller with an "initial configuration" that reflects the pool the device was initially set up to use. GAW QC'd every one of these controllers using their own devices and pools prior to shipping them.

HERE is what went wrong, and the fault is ZenMiner, not GAW. The config that came shipped on the device was supposed to be wiped away upon initial activation using the 4 digit code. We had a major flaw in our activation that did not permit the devices to connect to the cloud and receive the customer's pool information. Therefore, the initial pool information did not get overwritten. This is the single issue that our developers have been working non-stop to remedy as it is the one that is diverting all of our resources, including me (help desk).

I can assure you, and the entire community that the ZenController has *zero* malicious intent to redivert your hashes. This was a launch bug that we are taking full responsibility for and doing everything we can to fix.

We will provide the community with 100% transparency from this point until total resolution.