Order 220 just received. The august delivery promise was kept, but it was a close call. Got a starter kit with two H-boards, which greatly overdelivers the promised hashrate. The unit is hashing at around 40GH/s (+-3GH/s). Setup was really easy with the simple web interface, I just input my pools there and restarted the miner.
I'd like to invite everyone who is going to receive a unit to use a small pool and/or p2pool if the miner inside the unit can work with it.
There are several small pools, pools with less than 50 TH/s of capacity, which should/need to grow to be able to balance the one or two mega-pools available.
This is for the health of the bitcoin network, most of all, and given that BitFury is delivering several TH/s of hashing power this is a good moment for this call to arms
spiccioli
Could someone please provide step-by-step instructions on how to configure chainminer to run as a p2pool configuration?? I'm surprised almost nobody has documented that well enough on what needs to be done the rPi side.
I think I'm somewhat clear (although not 100% sure) on what software/steps that needs to run on my PC/host but I read somewhere that some chainminer files need to be updated on the rPi side. I'd highly appreciate it.
Sadly it does not work with p2pool because slush's stratum proxy does not and chainminer has no stratum support.
spiccioli
So in the end, under bitfury we are trapped at the mercy of countless DDoS attacks. I have, and I expect many others too, lost LOTS of coins due to this severe limitation that leaves us absolutely defenseless. :-/
Is there any documentation, however limited or partially tested, on how to compile and run bfgminer or cgminer for bitfury for p2pool???
This is getting really painful.
I haven't tried this but what is stopping you from running a p2pool node on a PC on your LAN and setting it's IP as the getwork address in jobconnect.cpp and recompiling?
