GAW ZenCloud ZenPool Hashlet - does it really exist? ALWAYS MAKE MONEY :-)

[suchmoon]

A psychologist could write a paper on clients reactions to negative news. You are hyping yoursevves up and they are making it worse by using words like "hack" and "delay". They should learn from cabin crews: ladies and gentlemen, we are flying through a storm front, the shaking and cracking is completely normal, please relax end enjoy a movie, while we prepare some snacks for you.

To be fair it would extremely difficult to put a truly positive spin on what happened in the last 24 hours. Maybe give everyone a free Prime? Freebies often help. But sometimes a business has to just own up to the issue, lay out a plan of dealing with it, and stick to said plan. Trouble is, that was done a couple of weeks ago (the promise to improve QA etc) and hasn't resulted in much of anything.

I guess we'll have some kind of announcement about this, should be interesting.

[suchmoon]

Looks like they fixed it by taking MH/s from marketplace buyers:

https://hashtalk.org/topic/11787/bought-2-25mh-primes-last-night-now-they-show-as-1mh

At first glance it looks like an api bug, like the one with disappearing hashlets. I can't see a reason to purposely change the picture. The first person to buy it would post the bug and stop all others from buying until it gets fixed.

Not sure what you mean by changing the picture. This seems to be one of the users who bought the "hacked" 25 MH/s primes on the marketplace yesterday for $700+. Now it looks like he/she bought 1 Mh/s (not 25) for $700. Not the kind of fix you'd expect after a ~12 hour maintenance. There is still a chance though that the buyer will get a refund for the other 24 MH/s, perhaps just delayed along with payouts.

[Mapuo]

They have too many withdrawals, after buyback enabled. My (little fish) was 3.3 BTC, 10 minutes after buy back was possible.
One hour later withdrawals was suspended.
Another hour later, josh announced some things(strike back on massive withdraws).
Later was a "hack" joke.

PS. Resellers prices actually are inspired by gaw - in their attempt to stop mass prime sells.

[alienesb]

My buyback was 5.7 BTC

[eightcylinders]

Looks like they fixed it by taking MH/s from marketplace buyers:

https://hashtalk.org/topic/11787/bought-2-25mh-primes-last-night-now-they-show-as-1mh

At first glance it looks like an api bug, like the one with disappearing hashlets. I can't see a reason to purposely change the picture. The first person to buy it would post the bug and stop all others from buying until it gets fixed.

Not sure what you mean by changing the picture. This seems to be one of the users who bought the "hacked" 25 MH/s primes on the marketplace yesterday for $700+. Now it looks like he/she bought 1 Mh/s (not 25) for $700. Not the kind of fix you'd expect after a ~12 hour maintenance. There is still a chance though that the buyer will get a refund for the other 24 MH/s, perhaps just delayed along with payouts.

What is especially interesting (in a not-so-likely-coincidence kind of way) is that for this to happen: (1) somehow GAW "mistakenly" coded 1 mhs miners as 25 mhs miners, (2) which also means that sales of hashlets through resellers are not automated, and each hashlet requires a human being (who can make a mistake) to manually generate an activation code, (3) the same mistake was made repeatedly, and (4) the folks who received this bonus immediately sold back on the market (which, coincidentally, had just been opened) at an extra low price to ensure quick buys and then cashed out knowing they would be caught otherwise.

And who is left holding the bag (or the 1mhs hashlet that was purchased for $700 by some poor schmuck)?  The innocent buyer.  

Hmmm.

All this at a time right after the prime market is reopened and there are massive sudden withdrawals, run on the bank.

Hmmmm.

If I were one of those buyers, I would be getting lawyered up and getting subpeonas out to trace the accounts of the **sellers** and get access to the true facts about how this "mistake" was made, before the evidence disappears.  It is extraordinarily unlikely that the events above transpired in the way GAW has said.  

[eightcylinders]

Here would be a great way for a cloud mining company to harvest large amounts of BTC from unsuspecting sheep:

1) Sell 25mhs units to dummy accounts (sprinkle in a few legit users for good measure), but label them as 1 mhs units and charge as 1 mhs units

2) Through the dummy accounts, resell on as 25 mhs units on the newly opened marketplace

3) Transfer out the proceeds of sale to replenish the scam's coffers

4) Announce that hackers had exploited the speedy mighty hash units and shut down the whole system for a while for "investigation"

5) Change the 25 mhs units back to 1 mhs

6) Announce that the attackers had gotten away with the theft, and there is no way to trace their accounts (which were dummy accounts).  All the BTC they took is gone, and the buyer of the 1 mhs unit (for which he paid 25x what he should have) will just have to suck it up, because theft sucks but its not the cloud mining company's fault now is it?

7) Shut down all marketplace sales because of the "hackers" and require all future purchases through "legit" resellers

problem solved!!!

[suchmoon]

If I were one of those buyers, I would be getting lawyered up and getting subpeonas out to trace the accounts of the **sellers** and get access to the true facts about how this "mistake" was made, before the evidence disappears.  It is extraordinarily unlikely that the events above transpired in the way GAW has said.  

What's that famous saying - "Never attribute to malice that which is adequately explained by stupidity" ?

I think it is likely that there was a technical/human error with the activation codes, and we've seen plenty of errors of all kinds in ZenCloud so no big leap of faith needed here. The explanation, the fix, the aftermath - that's where it's getting harder and harder to suspend disbelief.

But as far as conspiracies go - wouldn't it be great if it turned out that one of the resellers/moderators was involved  . I wonder how much control does a reseller have in issuing those codes.

[suchmoon]

6) Announce that the attackers had gotten away with the theft, and there is no way to trace their accounts (which were dummy accounts).  All the BTC they took is gone, and the buyer of the 1 mhs unit (for which he paid 25x what he should have) will just have to suck it up, because theft sucks but its not the cloud mining company's fault now is it?

Slight problem, the 10% fee and the whole idea of marketplace was supposed to shield the buyer from fraud. Granted it was mostly about credit card chargebacks and such, but it would be a pretty serious turnabout to deny that.

[Mapuo]

Resellers for "virtual" miners is ridiculous, for physical shipped to customers its ok.
But for hashlets...

[alienesb]

My payout is .12 less than yesterday's 

[NuShrike]

It's always nice they announce obvious issues a few hours-to-a-day after we already experienced it on the site.

#payoutwatch

[Tripjammer]

My payout is .12 less than yesterday's 

Yeah payouts were shit today!

What are the weekly payout avgs on LTCgear? I am thinking of going in on there soon...

[Honeycutt22]

My payout is .12 less than yesterday's 

Yeah payouts were shit today!

What are the weekly payout avgs on LTCgear? I am thinking of going in on there soon...

Yea, everything is shit today.. Payouts, no withdrawals, Market fiasco, "exploits"... what else.... Oh, HT is down now...

Now DD is half as valuable since LTC pool sucks ass.. Pretty frustrated right now with everything.

[alienesb]

Yeah some crazy shit going on but that's what happens when you fly by the seat of your pants. Maybe there's an exploit being used on HT 

[suchmoon]

I'm pretty sure that hacker's nickname is "nginx", I saw the signature on the defaced hashtalk page. They should check if hashlets were exploited by the same person. Offer a bounty on HT to catch him/her. Nothing unites the community better than some good old witch hunt.


Edited 2020-11-27 to fix a broken image

[miaviator]

I'm pretty sure that hacker's nickname is "nginx", I saw the signature on the defaced hashtalk page. They should check if hashlets were exploited by the same person. Offer a bounty on HT to catch him/her. Nothing unites the community better than some good old witch hunt.

I like it!

[Honeycutt22]

I'm pretty sure that hacker's nickname is "nginx", I saw the signature on the defaced hashtalk page. They should check if hashlets were exploited by the same person. Offer a bounty on HT to catch him/her. Nothing unites the community better than some good old witch hunt.

U just messing around about the hacker it what? Seems like a normal 502 error to me.

[alienesb]

I'm pretty sure that hacker's nickname is "nginx", I saw the signature on the defaced hashtalk page. They should check if hashlets were exploited by the same person. Offer a bounty on HT to catch him/her. Nothing unites the community better than some good old witch hunt.

I heard some guy named Apache was already after him.

[suchmoon]

I'm pretty sure that hacker's nickname is "nginx", I saw the signature on the defaced hashtalk page. They should check if hashlets were exploited by the same person. Offer a bounty on HT to catch him/her. Nothing unites the community better than some good old witch hunt.

http://i.snag.gy/ve2hO.jpg

U just messing around about the hacker it what? Seems like a normal 502 error to me.

Sorry, I always forget to add the appropriate number of these newfangled yellow thingies, pick whichever you like:  

[Honeycutt22]

I'm pretty sure that hacker's nickname is "nginx", I saw the signature on the defaced hashtalk page. They should check if hashlets were exploited by the same person. Offer a bounty on HT to catch him/her. Nothing unites the community better than some good old witch hunt.

http://i.snag.gy/ve2hO.jpg

U just messing around about the hacker it what? Seems like a normal 502 error to me.

Sorry, I always forget to add the appropriate number of these newfangled yellow thingies, pick whichever you like:  

I like you "O" face one