|
Yes, Manual payouts are still disabled at this time. An update now that I've had a day to work on it:
Yesterday, a significant number of coins were stolen from the pool. The exact method this was done is not yet known. Most of my time yesterday was spent doing a full audit on all SQL queries and RPC calls. No immediate issues were apparent, so a full rewrite was done on significant amounts of code, including a full overhaul on frontend interface with the backend. The frontend is no longer responsible for any payout calls, nor is it capable of editing/deleting/inserting information into the database related to earnings or payouts. Additionally, the frontend is no longer capable of making RPC calls to the backend at all.
This is why manual payouts are still currently disabled. At this time, the frontend is not capable of making modifications to payouts, or sending payouts. I'm working on a new process to get manual payouts working again soon. It's currently a 2nd priority, as I'm falling very far behind on packing & testing of erupters. Going to be spending the first half of today getting 1/3 of the units shipped, while I think about all the double checks, sanity checks, etc., that will be needed in order to restore manual payouts in the new system.
|
|
|
|
|
Worker speeds are currently being reported inaccurate (too high) due to some changes to the database. The script that logs speeds every 2 minutes didn't execute for about 15 minutes. As a result, your speed is including an extra ~15 minutes worth of shares. It should clear up once the old data is expired.
UPDATE: Worker speed history was cleared out to avoid the inaccurate reporting. Speeds will show 0 MH/s for a few minutes. Expect speeds to vary a bit for the next 20 minutes due to variance/luck in submitting shares.
|
|
|
|
Have you heard from Friedcat? i saw that he was in touch with canary and he is starting another group buy.  Some new units are being ordered, yes. Store should be open (US Only until I catch up, I'm very sorry international users) later in the week once I get a tracking #. |
|
|
|
|
The majority of larger pools pay transaction fees to miners. The ones that don't are generally smaller pools, PPS only, or run a no-fee payment system where blocks are assumed 25 BTC and the pool fee = transaction fees.
BTC Guild (PPLNS)
BitMinter
Slush
OzCoin (DGM)
bitparking is working on transaction fees being included, and temporarily removed their fee until they get it working to make up for the lack of transaction fees.
|
|
|
|
Payments are temporarily paused. Something happened last night and somebody was paid a lot more than they should have been. All failed payouts will be resent once funds are transferred back to the hot wallet and I find out what happened.
Thanks for update, do you have a timeframe on fixing the situation? Broken payouts (bad txid) have been removed from payout history. I've manually issued two automatic payout runs (one for large and one for small). I'm expecting manual payouts and automatic payouts to resume normally within the next 2 hours. |
|
|
|
|
Payments are temporarily paused. Something happened last night and somebody was paid a lot more than they should have been. All failed payouts will be resent once funds are transferred back to the hot wallet and I find out what happened.
|
|
|
|
|
An email went out recently to high speed users informing them of private server access details for DDoS mitigation/protection. This server has been around a long time, and with the exception of a few early attacks when the private server wasn't properly isolated, it has kept high end users online during attacks. This post is just confirming that those emails did originate from BTC Guild.
Additional invites will go out to private servers more regularly in the future.
|
|
|
|
Did you get new stock in on Friday? Are you expecting to start shipping again on Monday?
I got the first part of the next batch (~75% of the units on order) yesterday. I only did limited testing yesterday, but I'm starting to test all the units today and tomorrow. I expect to be shipping out a large bulk of orders Monday. I expect most (if not all) backordered units to be shipped out by Wednesday (remaining units won't be here til Monday). |
|
|
|
I saw on a screen-shot posted recently, that someone with a bunch of block erupters
was still running with lowest "Minimum Difficulty", sending found shares each second.
I think that is quite a waste of network ressources and might even reduce your asics'
performance.
BTC Guild utilizes variable difficulty, so even if you don't do these steps, you don't stay at diff=1 for more than a minute if you're a fast miner. The pool allows miners to fluctuate between 12 and 40 shares per minute before adjustment. The target is 20~25 shares per minute. However, if you do run a large farm, or extremely fast ASIC, setting a minimum difficulty is useful in preventing the initial burst of traffic you would see otherwise prior to a diff adjustment (although the pool is quite aggressive with adjusting new connections to proper difficulties). |
|
|
|
I use mostly Anker hubs, but also run a couple of cheap hubs using an upgraded 4 Amp power supply. For some reason, my Raspberry Pi doesn't seem to like the more expensive Anker hubs. I've had no problem running 9 Erupters (plus a USB fan) in a cheap 10 port USB hub after upgrading to one of these power adapters: http://www.siig.com/it-products/usb/accessories/5v-4a-power-adapter-for-usb-3-0-hubs.htmlA word of warning, though - the brand of hub you use DOES matter. As one example, I can't get D-Link 7 port hubs to work with the Raspberry Pi, or with any of the direct USB zadig installed libusb drivers on a Windows box. I would recommend against running 10 devices on a 5v 4A adapter. While it might work...you're really playing with fire there. 9 erupters + fan should be pulling 5.0-5.2A. |
|
|
|
After a few people having the same issues in IRC, here's a quick guide on some common issues:
1) Extremely high HW Error rate with virtually no hash rate. This is almost always due to power issues. The chip is not receiving full power from your hub/port most likely. If you're running many chips, unplug them all, plug them in one at a time, run it for a few minutes, and confirm that it's getting shares. All ASICs will have HW Errors to some degree, but anything over 1-2% after 10 minutes is where there may be something very wrong.
2) Chips not showing up in bfgminer/cgminer. This is the same as #1. Cheap powered hubs will not be providing enough power to each port, and as a result the chips won't be acknowledged by bfgminer/cgminer.
USB Hubs:
There are virtually no hubs out there under $50 that will power more than 4 or 5 Block Erupters at once. If you are determined to buy cheaper hubs, you will need to plan on running only 4 per hub. The only hubs I have confirmed as being safe to run more than 4 miners are:
Rosewill 10-port hubs: These are 4A @ 5v. This means it is safe to run 7 Block Erupters. You do not want to push the hub to the max power supply rating!
Anker 10-port hubs: These run 4A @ 12v. This means it is safe to run a full 10 Block Erupters without worry.
On any other hub: Look at the power rating. Factor in 0.6A per Block Erupter to give it safety. Running a low grade PSU at it's max rating could eventually result in damaging any or all chips plugged into the hub, and undesirable performance even if it does not actually damage the chips.
Quoting this on a new thread page just so nobody misses it. |
|
|
|
|
After a few people having the same issues in IRC, here's a quick guide on some common issues:
1) Extremely high HW Error rate with virtually no hash rate. This is almost always due to power issues. The chip is not receiving full power from your hub/port most likely. If you're running many chips, unplug them all, plug them in one at a time, run it for a few minutes, and confirm that it's getting shares. All ASICs will have HW Errors to some degree, but anything over 1-2% after 10 minutes is where there may be something very wrong.
2) Chips not showing up in bfgminer/cgminer. This is the same as #1. Cheap powered hubs will not be providing enough power to each port, and as a result the chips won't be acknowledged by bfgminer/cgminer.
USB Hubs:
There are virtually no hubs out there under $50 that will power more than 4 or 5 Block Erupters at once. If you are determined to buy cheaper hubs, you will need to plan on running only 4 per hub. The only hubs I have confirmed as being safe to run more than 4 miners are:
Rosewill 10-port hubs: These are 4A @ 5v. This means it is safe to run 7 Block Erupters. You do not want to push the hub to the max power supply rating!
Anker 10-port hubs: These run 4A @ 12v. This means it is safe to run a full 10 Block Erupters without worry.
On any other hub: Look at the power rating. Factor in 0.6A per Block Erupter to give it safety. Running a low grade PSU at it's max rating could eventually result in damaging any or all chips plugged into the hub, and undesirable performance even if it does not actually damage the chips.
|
|
|
|
Linux guide was added at the bottom of http://www.btcguild.com/index.php?page=support§ion=blockerupter . Just a note: Lots of people are getting chips and plugging them in. Please be very careful with underpowered/generic brand hubs! Very few hubs can actually power every port at max draw. Most of the cheaper ones can only power half of their ports when pulling full power. Running the chips with inadequate power will cause poor performance, and possibly cause damage to the chip if left running like that. |
|
|
|
4x Block Erupters received. They are merrily hashing away on a Raspberry Pi system along with the one I had running there initially.
Yay! I think we're going to see a lot of happy people today. A huge bulk of the orders that shipped out on Tuesday are supposed to arrive today. Close to 75-80% based on the sample I took. Of course, that's USPS Expected Date, so it may not take rural areas into account properly. Luckily, USPS delivers on Saturday too! |
|
|
|
worst comes to worst, he mines with them.
He's already got 39GH/s not sure he needs more ;-) 39 GH/s? Not sure where that came from unless you were checking my speed under Team America (User ID 1). It's closer to 80, been playing with Avalon firmware/overclocks today. Until yesterday I only had 2 GH/s  |
|
|
|
eleuthria, what are you going to do if you order 1000 pieces, then friedcat drops the price in half again. Then you're stuck with a bunch of those things.
I won't be keeping huge inventories after the initial rush. Once they have inventory available again, I'll be ordering [Backorder Queue + 10%] each time I place an order. |
|
|
|
why not take me up on my offer to help you ship out? At the moment, I can handle 1000 /day in my facility.
Because I can receive, unpack, test, and ship 500-700/day on my own. Update for USB Miner Customers: Guides are a little delayed, but will be posted up soon on how to properly setup your Block Erupter on both Windows and Linux. Taking desktop screen caps now as I go step by step on Windows. Linux will be limited to Ubuntu/Debian compatible guides. |
|
|
|
|
I used Anker 10-port USB 3.0 hubs for all my testing. Had no issues, and was very confident since they weren't running at or above the power rating of the power supply.
|
|
|
|
|
I just got my Avalon today. BTC Guild almost immediately showed 70-72 GH/s. Please note that the dashboard for BTC Guild uses an hour long average if there is any historical data. So if you added your Avalon to an existing worker, it won't reflect the Avalon's full speed for an hour.
|
|
|
|
|
Show Posts
