Entire contract. I think that the argument of others and myself here for
this option is that the contract wasn’t delivered as promised. But
appreciative of your efforts to remedy the situation. But this wasn’t a
formal request rather than an echoing of @ohweoh . Open to alternatives and
very much appreciate the work you and your team are putting in to right the
ship (and of the hash rate increases).
1 Like
We had a delay in the start of full delivery on our contracts of about 0.5% to 2% of the full contract duration. This would likely be considered a minor breach of contract in court. In a minor breach, the non-infringing party is entitled to compensatory damages, but the remainder of the contract is still valid. The breach would need to be considered a material breach before it would make the entire contract invalid.
As it was not a material breach, the contracts stand.
@jtoomim I’m surprised you still come back to the forums to take this constant abuse. I’m sorry if people lost money on speculation of magic internet money, but that was a risk they were all too willing to take when it looked like they might profit out of it. When it turns out bad, they want to backpedal and act like they’re in no way at fault for their financial loss. I think you’ve been a reasonable person, at least as far as I’ve read your posts, and while you may be at fault for the delay, I don’t see you trying to avoid that. Just wanted to say that I’m sorry you’re being hated on by a ton of people who are nothing but reasonable.
Why have you taken my hash off of Suprnova and decided apparently upon your on decision to point to flypool where I am getting shit for all rewards. Please point hash at Suprnova where I requested. Thank you.
Otherwise, I need your public IP to change the flypool settings apparently…fuck this
Our code noticed frequent problems staying connected to your primary pool, so it switched over to your backup pool.
If you want us to only hash on your primary pool and ignore occasional connectivity problems with it, you could delete your backup pools from your account.
I’ll also look into making our code more aggressively prefer your primary pool even when there are occasional errors with it.
Edit: We’ve made some changes to our backup pool handling code. We should now prefer primary pools more strongly. Let me know if the issue persists.
Breasal, don’t cuss.
When your primary pool fails, we hash to the backup pool you gave us.
Well, I understand you may not be able to compensate for the full loss, but I would expect that you return as much as you could from the original contract purchases, as I’m sure you would agree that it would not be fair for you to profit from this situation. If you have sunk some of the funds raised into additional hardware, then that should put to work generating the shortfall for users (and hopefully some income for you guys).
Yeah, mining slow start combined with all the hype made for some crazy trading prices, it’s clear who the winners are and anyone looking to buy hashing from cloud mining need look no further.
Nicehash is awesome 
You spend way too much time and effort explaining yourself. Your investors spend way too much time complaining.
1 Like
Our contracts were not specified to start at T0; they were specified to start on October 28th. If they had started up to 14.7 hours after the genesis block was published, they would still have started on October 28th, and would still have satisfied our legal obligations. I have decided to exceed our legal obligation and have offered to compensate our customers with 2000% of the ZEC they would have mined starting from T0. I am not going the extra parsec and offering the amount of BTC that the ZEC that could have been mined before our contracts were required to start could have been traded for if they had been traded at the highest exchange rates possible, because (a) we weren’t obligated to be online then, (b) those exchange rates were ridiculous (“not reasonably forseeable”), and (c) we can’t afford to be that generous.
Most of the reason why our contracts were not profitable was that the Zcash network hashrate was far higher than our customers anticipated. We have voluntarily given our customers 4x to 12x extra hashrate to soften the impact of this misprediction. We are already allocating much more hardware to our customers than we would have needed to if we were still using our own software at the originally specified hashrates.
We should not profit (and are not profiting) off of a failure to deliver on the first two days of our contracts. We are overdelivering on 98% to 99.5% of the contract durations, and it is fair for us to keep the revenue we made for the portions of the contracts that are being delivered faithfully, after compensation for the downtime has been subtracted.
Not 20 dollars bro
20 dollars
You would probably be better off if you offered refunds, which would be the correct thing to do considering you didn’t deliver as promised.
I’m not a customer and have no bias
We ask for refund because you failed deliever hashrate at lanuch day ,which is the most important time for mining . You only started offerring weak hashrate two days after launch ,which is so pathetic
just refund me
My refund btc address: 1C4yyZhQCAkfWanMAACiJBTYj7CUKM828W
1 Like
you know we all bought your cloud mining for starting mining at the first time of launch, we all died of your launch failing ,you did say you were very sad when you failed to deliver hashrates at the first two days ,so you know you have failed to fullfill the contracts and asked customers to give you sometime to fix your owns problem and then disscuss refund , but you lied,
now I still ask you to take your responsibility , just refund me !
my refund btc address: 1C4yyZhQCAkfWanMAACiJBTYj7CUKM828W
2 Likes
Reading this thread is like listening to a broken record…
6 Likes
yes ,Toomim broke the record from the start
That’s what happens when you sell a product to people that don’t understand what they are buying.
1 Like
ppl know what they are buying , when ppl buy cloud mining service they are especially buying lanuch day minning
it is possible that there was no issue apart from the price been so ridiculous first day they took the decision to earn a quick buck for themselves
We did not mine ourselves for the first few weeks, and we have a witness who attests to that:
what’s going on with these cloud mining companies and poor pricing models they are most certainly taking advantage of people not in the know
We didn’t set our prices, our customers did via an auction.
they should have passed on all of the speed increases to customers
We did, and more. Our code got 42 H/s as of a couple weeks before launch. Currently, the best miner we can use (Linux) gets about 140 H/s on the same hardware. That’s 3.3x faster. We’re giving 4x to 12x as much hashrate as our customers paid for.
1 Like
What we have here is a few people trying to get a refund by holding our reputation hostage. They are hoping that if they complain frequently enough, that we will give in and give them a refund on their non-refundable contracts.
eastwind_ja said this to me via email on Nov 1st:
but you should know I have made up my mind for a refund and I will not give up . I have promised if you refund for me , i will not say a word about refund of mine on forum.
if you don’t refund ,then you just make me keep sending email and posting on forum. This not good for both you and me ,and I don’t think this is nessesary .