Round 15/16 KnC Jupiter, DZ MC. Please move comments and ?s to this thread. Thx.

[thomas_s]

As we have said before we have staff and worker 4 shows that its hashing.

We have attempted to restart it multiple times.

[nicksmith]

As we have said before we have staff and worker 4 shows that its hashing.

We have attempted to restart it multiple times.

If you show it hashing on your end and the plugin is just broken on your website for the last 60 hours, why would you even attempt to restart it?

[thomas_s]

As we have said before we have staff and worker 4 shows that its hashing.

We have attempted to restart it multiple times.

If you show it hashing on your end and the plugin is just broken on your website for the last 60 hours, why would you even attempt to restart it?

Worker 4 is broken, its showing that its hashing but it isn't, every attempt to restart it shows the same thing it turns on its hashing, we check the monitor and BTCGuild and it shows its down.

[gh2k]

Worker 4 is broken, its showing that its hashing but it isn't, every attempt to restart it shows the same thing it turns on its hashing, we check the monitor and BTCGuild and it shows its down.

What, if any attempts have been made at resolving the problem using kncminer's technical support, and what answers have we had?

[railzand]

Worker 1 Hash Rate       710.407 Gh/s
Worker 2 Hash Rate       672.535 Gh/s
Worker 3 Hash Rate       679.254 Gh/s
Worker 4 Hash Rate       510.051 Gh/s
Last Update: 14 minutes ago | plugin by mootinator

snip


What, if any attempts have been made at resolving the problem using kncminer's technical support, and what answers have we had?

[gh2k]

All 4 workers are down:

WORKER 1 HASH RATE       0 Gh/s
WORKER 2 HASH RATE       0 Gh/s
WORKER 3 HASH RATE       0 Gh/s
WORKER 4 HASH RATE       0 Gh/s

[gh2k]

All 4 workers are down:

WORKER 1 HASH RATE       0 Gh/s
WORKER 2 HASH RATE       0 Gh/s
WORKER 3 HASH RATE       0 Gh/s
WORKER 4 HASH RATE       0 Gh/s

They're back again

[BorisAlt]

Thank you for addressing the issues, bringing all 4 workers on line. We are just 28% from making ROI. Please keep up your efforts on running this GB to success.

[rudyo]

as of 4:30am EST Workers 1 and 4 are down.

Could someone please tell us who gets the alert when they are not hashing? (assuming there IS an alert...)

[thomas_s]

R15/16 Update: As mentioned earlier in this thread, these Jupiters have been finicky (and still continue to be problematic).

I apologize for the inconvenience but Miner Hosting LLC has decided to ship these Jupiters to another vetted miner hosting facility in the US. They will be hosted at a DZMC vetted miner facility, with our 4th vetted miner host at a top notch hosting facility.

At the end of the month: DZMC veteran member thyatis will be taking over the hosting for these Jupiters in Florida. He has prior experience with a variety of different miners.

His setup includes:

- 120V or 220V power
- Triple network redundancy
- APC UPS units capable of 8 hours of backup time for 6 Jupiters
- Gas generators for longer outages
- Dedicated air conditioning for the miners

To compensate DZMC members for downtime during shipping and setup, on hand miners from other mfgs. will be substituted as equivalent hashrate until the Jupiters are up and running again in Florida. BTC earned from this be sent to thyatis, who will be handling payouts after some training, as part of the 1st thru 15th payout.

Please refer questions for miner in Florida. to DZMC vetted Miner Host: thyatis.

Thanks.

EDIT: Thomas will still be handling miner payouts.

Downtime will be compensated by sending BTC that would have been earned while they are down to the payout address.

[bobsag3]

R15/16 Update: As mentioned earlier in this thread, these Jupiters have been finicky (and still continue to be problematic).

I apologize for the inconvenience but Miner Hosting LLC has decided to ship these Jupiters to another vetted miner hosting facility in the US. They will be hosted at a DZMC vetted miner facility, with our 4th vetted miner host at a top notch hosting facility.

At the end of the month: DZMC veteran member thyatis will be taking over the hosting for these Jupiters in Florida. He has prior experience with a variety of different miners.

His setup includes:

- 120V or 220V power
- Triple network redundancy
- APC UPS units capable of 8 hours of backup time for 6 Jupiters
- Gas generators for longer outages
- Dedicated air conditioning for the miners

To compensate DZMC members for downtime during shipping and setup, on hand miners from other mfgs. will be substituted as equivalent hashrate until the Jupiters are up and running again in Florida. BTC earned from this be sent to thyatis, who will be handling payouts after some training, as part of the 1st thru 15th payout.

Please refer questions for miner in Florida. to DZMC vetted Miner Host: thyatis.

Thanks.

EDIT: Thomas will still be handling miner payouts.

Downtime will be compensated by sending BTC that would have been earned while they are down to the payout address.

And that BTC will be sent as soon as thyatis confirms he has them back up and running.

[rudyo]

Can you give us the schedule?  When will the miners be taken offline and shipped?
How are they being shipped and by what service level?  (FedEx Standard overnight, FedEx 2 day etc.)

[rudyo]

as of 4:30am EST Workers 1 and 4 are down.

Could someone please tell us who gets the alert when they are not hashing? (assuming there IS an alert...)

Also could someone please answer this question in the context of the new hosting?  I get that there is network redundancy, UPS units, generators, AC etc. (all of which was promised to us at the current hosting facility), but none of that really helps much with a fickle or problematic miner.  I would like to know what the response time is once a tech gets  an alert on a miner not hashing.  What is the SLA for issues that require a reboot or hands on interaction?

Given the current difficulty, the entire group of 4 miners is only hashing at around .5 BTC a day, but that is still ~$13.00 per hour that is lost and it adds up pretty quick. 

[gh2k]

What, if any attempts have been made at resolving the problem using kncminer's technical support, and what answers have we had?

I would still like an answer to this. Worker 4 would be a much more re-saleable proposition if restored to working order.

[mdude77]

I'm confused.  My payout for the 15th is half of what it was on the 1st.  Difficulty didn't increase 50% in the last 2 weeks did it?  Are our rigs doing that bad that we got 50% less than 2 weeks ago?  Also, where did the BTC/USD rate of $662 come from?  mtgox has it at $370.

M

[smooth]

Difficulty didn't increase 50% in the last 2 weeks did it?

No, and also don't forget a 50% increase in difficulty means a 33% decrease in mining output, not a 50% decrease.

EDIT: Also, I got no payout. Why?

[rudyo]

Here is my read on it.

Jan 15th - 31st calculation:

17 days in Period
2600 GH/s

8 days @ .7397 BTC per day
Diff change on Jan 24
9 days @ .5961 BTC per day
Total:  11.28 BTC (at 100% uptime)

Actual Gross Payout: 10.5 BTC
BTC lost due to downtime: .78 BTC
Actual % payout:  93%

So not too bad, I don't think all miners were up at 100% for this period, so the 93% seems about right

Feb 1st - Feb 14th calculation:
14 days in period
2600 GH/s

4 days @ .5961 BTC per day
Diff change on Feb 5
10 days @ .4988 BTC per day
Total:  7.37 BTC (at 100% uptime)

Actual Gross Payout: 6 BTC
BTC lost due to downtime:  1.37 BTC
Actual % payout:  81.3%

So based on these calcs it appears that we did lose more BTC to downtime, but not appreciably so.  The difference in the number of days had the greatest impact.
Also the drop in BTC/USD price meant that more was taken for the hosting fees.  So double whammy, less days, diff increase, more downtime, more BTC taken for fees =  much lower payout.

I estimate the next period as follows:

Feb 15th - Feb 28th (estimated)
14 days in period
2600 GH's

2 days @ .4988 BTC per day
Diff change on Feb 17 (estimated)
12 days @ .4194 BTC per day
Total: 6.03 BTC (at 100% uptime)

The actual difficulty change could skew these numbers slightly, but they are close.  

Proposed Action:

The difficulty has really become a crushing force.  When these miners started hashing difficulty was 707,408,283 and the daily revenue was 1.84 BTC per day.
The next difficulty will be close to 3,117,760,889 and the daily revenue will only be .4194 BTC per day, merely 22% of when we started.

There is nothing in the foreseeable future that will slow or halt the difficulty increase.  The daily take of .4194 will be reduced to an estimated .17 BTC per day by April 1st.
These numbers lead me to believe we should actively pursue selling the hardware and ending this GB, preferably before the next round of asic's hit the streets.

The current street value of a KNC Jupiter is  $7,000 - $10,000.   I propose that these 4 miners be sold immediately at the current street price and the proceeds distributed to the shareholders. A sale could yield $25,000 - $40,000 or $125- $200 per share.  This is far more than I believe we will receive in future payouts, given that the current payout was only .025 BTC per share.


DZ, Thomas, what action is needed by the shareholders to make a decision to sell?  Do you put it to a vote?  I hold 20% of the GB and favor a sale ASAP. I believe that a sale even as low as $5000 per unit would be the correct decision.

Thoughts?
  
Edited to correct share price upon sale... that is what I get for posting late and not checking my math!  :-)
The proceeds should be divided by the # of shares, which is 200.

Can one of the Group buy coordinators clarify please?

[railzand]

Thank you rudyo. I second your proposal. Please let's sell them now. I've 2 shares.

[rudyo]

Thank you rudyo. I second your proposal. Please let's sell them now. I've 2 shares.

I guess if we need a majority, that is 101 shares.  I hold 40 shares + your 2 = 42.

The proposal is that the 4 KNC Jupiters be sold immediately, pricing them to ensure a quick sale. Of course we would not accept a lowball offer.  Current street price can be estimated from the BTC marketplace as well as eBay.  Shareholders to approve final selling price.  Net proceeds to be distributed to the shareholders.

Shareholders, please respond with your vote.

Edit: GB coordinators; DZ, Thomas, et al, if there is a different way we should go about this, please let us know how to proceed.

[mdude77]

Thank you rudyo. I second your proposal. Please let's sell them now. I've 2 shares.

I guess if we need a majority, that is 101 shares.  I hold 40 shares + your 2 = 42.

The proposal is that the 4 KNC Jupiters be sold immediately, pricing them to ensure a quick sale. Of course we would not accept a lowball offer.  Current street price can be estimated from the BTC marketplace as well as eBay.  Shareholders to approve final selling price.  Net proceeds to be distributed to the shareholders.

Shareholders, please respond with your vote.

Edit: GB coordinators; DZ, Thomas, et al, if there is a different way we should go about this, please let us know how to proceed.

I agree, my 5 shares vote for sale.

M