Search content
Sort by
Showing 4 of 4 results by kr0
Question. I have 3 gpu's is it worth pointing at this pool or should I stay with the alts?
With GPU's you are definitely not for BTC (or any other SHA256) mining at this point, no matter which pool.Even if your power is free GPU won't get you enough for withdrawal any time soon and if you want to donate your work to some pool, then pick your own favourite.
thx for the quick reply.
BTW is the mining proxy only for this pool or is it configurable?
I believe that you have to recompile to change where the proxy points. But i might be wrong. There is a thread fro the Slush proxy.
This is the one i've been reading.
http://mining.bitcoin.cz/mining-proxy-howto
You can use it with any pool. Just run the exe with /? (if I'm not mistaken), to print the help. Then give it the necessary arguments to connect to another pool.
Good grief, look at our hashrate.... 914020.302 Ghash/s... And we're still low guy on the totem pole? Jeez...
looks like somebody bought a truckload of BTC Dozers and switched on the Data Center a few hours ago
Maybe these guys:
http://www.ciol.com/ciol/news/207653/coinseed-invests-usd5-million-bitfury-bitcoin-mining-hardware
So we got super lucky on 281626. We found it at the same time as GHash.IO, but theirs got orphaned. The weird thing is, the next block, 281627, was found by GHash.IO. So why did they not used their own 281626 instead of ours?
It's not uncommon for large pools (even slush has done it before) to have multiple bitcoind servers and pool servers. It is actually possible, due to the inefficiencies of p2p transmission, for a pool to orphan its own block. By default bitcoind ignores other blocks that come in if they already have a block at that height, so if one of GHash.io's servers saw slush's blocks before another Ghash.io block, it will build on Slush's block unless they have modified bitcoind to prioritize their own blocks in the event of a race.
Thanks. That makes sense. I need to learn more about pool mining.
So we got super lucky on 281626. We found it at the same time as GHash.IO, but theirs got orphaned. The weird thing is, the next block, 281627, was found by GHash.IO. So why did they not used their own 281626 instead of ours?