Topic: Mining Multiple Pools to mitigate DDoS (Read 869 times)
always better to mine 2 than 1!
I currently use AOCLBF with phoenix 1.50 and the newest phatk kernel. I get 300-307 MH/s with a 6870 (core at 1GHz).
what should i use for a bitcoin miner?
I am currently using Smartcoin to do just that. It has already shown great promise.
Yea, I need something like that, but on Windows 
I am currently using Smartcoin to do just that. It has already shown great promise.
Depends on how it detects a pool that is down. One pool I am using sometimes gets 100% rejection, but the miner still works, so the idle detection of AOCLBF does not detect that.
I will try to make my own controller (or how you call it?) that would detect when the reject ratio is too high and switch to another pool.
I will try to make my own controller (or how you call it?) that would detect when the reject ratio is too high and switch to another pool.
Good Tip. The latest version of guiminer has command line options for backup pools too.
cheers
cheers
*poing*
Newbie to this forum. Evil mastermind over at bonzaikittenfurum.co.uk.org
Newbie to this forum. Evil mastermind over at bonzaikittenfurum.co.uk.org
You are one of the most helpful Newbies I have ever seen.
I saw this tip in a forum and it has worked well for me:
I've run several miners (each pointed to a different pool) for each graphics card. It has divided my overall MHash per pool, but when one gets DDos attacked the others speed up. It doesn't solve the problem from the pool end of things but it has kept mining manageable.
I've run several miners (each pointed to a different pool) for each graphics card. It has divided my overall MHash per pool, but when one gets DDos attacked the others speed up. It doesn't solve the problem from the pool end of things but it has kept mining manageable.
Jump to: