This is nowhere near adequate. You have completely botched the release of the S7 and screwed over your loyal customer base of early adopters.

Bitmain has enjoyed a lot of good will with this community. You have burned through that now and are well on your way to ruining your reputation.

Prior to this debacle, I would have no problem placing orders with you for early batches. Now I have no intention of being an early adopter of future products.

You should change your plans and truly make us whole. Once you destroy our trust, it will be hard to earn back.

PM sent...

If you want people to hate you forever, all you have to do is use an emoticon on almost every single line of all your posts.

Thanks Phil. I had that stick in the wrong pile. Now I've moved it from "donators" to "workers".

TRS, I think the list is correct now. But if you see another problems, please PM me again. Thanks for your help cleaning up the list.

My order from 9/5 (paid with bitcoin) is still unshipped.

But they still have about 17 hours before it's the end of the day on the 10th in China. Maybe they'll pull it off.

Currently the script doesn't email that field, but it would be easy to add.

One concern I would have though is that CK said that field never resets (if I'm remembering correctly). If we ever hit a block then wouldn't we also want that field to be reset for each worker? Otherwise historical shares for a given worker would be taken into account in the next block (like we'll ever hit two blocks )

Also, is the shares field adjusted for difficulty, or is it a raw number of accepts?

If we do happen to hit a block, my script will email Phil and myself. That email should contain the hash rate stats for all of the club members at that time.

I realize that through the beta period, it's one share per person, so the hash rate is not that relevant. But it could be useful to determine if a given worker is active or not at the time the block is hit.

Currently I'm duplicating Phil's worker list in a text file published on DropBox. The script uses that DropBox URL to obtain the member list. The nice thing about this approach is that I can update the published text file and the running script automatically knows about the changes.

Mine was September 5th. Still no indication of shipping.

The other cat is getting excited! But I told her that a lot could happen in a week...

As an alternative, Minera automatically starts your miner. You can optionally specify a number of seconds to delay after boot, if that's interesting.

It also supports automatically restarting if the miner software crashes (which I've never seen with cgminer-gekko), or restarting if N number of units goes non-responding (again, never needed to use this with the sticks).

Minera also has a pretty GUI, if you like that

I used to feel the same way. Even through best share is basically a meaningless statistic, it does give you a sense that something is happening.

By default, my monitoring script will sent an email if any of the monitored addresses have an improved best share. The last best share is stored in a file locally, so it doesn't matter if the pool resets it or not.

When I was just monitoring my own addresses, this was cool because I'd get an email once in a while. But now that I monitor all of the club's addresses, I was getting a ton of best share emails. It was really too much so I disabled monitoring of best shares for now.

Now all I see is when someone (anyone) solves a block on CK's solo pool. So far it's always been someone else.

But where there's hash, there's hope

If you pay for your electricity, the SP20 is a great option because of its under clocking capabilities.

Sure a used Antminer S5 might be a little cheaper, but it's a lot less flexible than an SP20.

See this thread where philipma1957 calls the SP20 the best miner he's ever owned:

https://bitcointalk.org/index.php?topic=872014.0

My SP20 is still available. If you're interested, make me an offer.

That's a good point. I'm running my SP20 with free electricity, which I guess is why I wasn't thinking along those lines. S3s are a lot less hungry power wise than the PS20, so they do make more sense for solo mining.

I was half joking.

But if the price stays the same until the company comes back from vacation, then yeah, I believe that it must be a manual process.

For all I know they might need managerial approval for any material price change.

I guess they have to change that manually, and no one is there to do it

So no SP20 club? I got rid of my S3s a long time ago.

I've been running two sticks at 306 MHz powered by USB Y cables for 5 days straight with 1 HW error. Each stick is running at 16 GH/s.

Originally I was running at 150 MHz and 8 GHs each with stock USB power and a whole lot more HW errors.

If you have the available current with your USB hub, you should be able to turn up the frequency and manually increase the voltage via the pot by the USB connector to achieve a balance between frequency and performance.

Short answer: these suckers are meant to be tweaked, so have some fun and optimize the hell out of them

I mentioned this before, but these things are remarkable. I just got my first hardware error in 5d 3h 46m 37s of run time.

That's pretty damn stable!

As far as I know, the bfgminer that's included with Minera is not new enough to support the sticks. Also, when I last tried to build bfgminer 5.3 on a RPi, it had a messed up version number. This apparently was a known problem at the time.

In the end I gave up on bfgminer for the Pi and concentrated on building cgminer-gekko and getting it running as a custom miner under Minera. That has worked perfectly and is very stable.

Note that my info on bfgminer might be dated at this point. I never bothered to circle back after I got cgminer-gekko working so well.

If you're interested, I posted a Minera image that includes cgminer-gekko. All you have to do is copy the image to your SD card, boot, then set your pools. The download URL is in the first post.

The only negative aspect of my posted image is that that version of cgminer-gekko doesn't really support any other mining hardware. Ideally it would support all the normal hardware, including U3's. Unfortunately there are compile conflicts when you enable both icarus and gekko.

At some point when the cgminer sources are cleaned up, I plan to rebuild cgminer-gekko and re-post the Minera image. However, if gekko support finds its way into the main cgminer sources sooner than that, and if the Minera author rebuilds and reposts, then there will be no need for me to continue to update the image that I posted. At that point it will be part of the main Minera image.

Hopefully the above makes sense. Let me know if you have questions.

Thanks CK! Much appreciated.