bitHopper: Python Pool Hopper Proxy

[djex]

to slice or to not slice that is the question.

That's the problem I'm having. I can decide what is best. Since I have smaller pools enabled slicing is good but then payout is effected. If I stick with default it's all fine and good on large pools but if it gets stuck on a small pool then payout is effected. So it's turned into a job of manually moving pools around to maximize payout.

[bb]

If you are hopping pools with low hashing power, slicing reduces your variance.

I for one am not hopping micro pools at all. You are basically beta testing those pools. Also, there might always be a pool op making a run for it after the first block.

[c00w]

Um bclc shouldn't affect anything either way. In fact if you want to mine them and not deal with their messing around use re_rate and mine_deepbit and scrape them with LP. You have to change the regular expressions to supply rate instead of shares though.

[joulesbeef]

Um bclc shouldn't affect anything either way. In fact if you want to mine them and not deal with their messing around use re_rate and mine_deepbit and scrape them with LP. You have to change the regular expressions to supply rate instead of shares though.

You mean the hash rate?

[c00w]

Yeah. Preferably in Gh/s

[paraipan]

gah I'm torn between oldDefaultScheduler and DefaultScheduler
BTCServ.net is new and slow.. with old default I am stuck here until someone finds a block...crap i dont even know where to find balance or crap on that site.
to slice or to not slice that is the question.

I would recommend using penalty for that slow pool issue, wait until you have desired number of shares on there and then increase penalty slowly to convince bH leave them, after they find a block same penalty applies if they still have the same average hashrate

[djex]

So can we mine BTCGuild with re_rate and mine_deepbit?

[c00w]

Yeah btcguild will work. Anything will work although it may not be that accurate

EDIT: But really: MINE DEEPBIT. They will make you the most money. Seriously.

[joulesbeef]

ok it said two new blocks found one for monkey and one for rfc.. neither pool reset.. does that mean they are slow on stats.. liars or something else, i'm not understanding?

and yeah already doing the penalty

new phatk22 out btw

[c00w]

It only resets pools with mine_Deepbit as role. And at least one of those blocks was from btcguild and the LP based ID was probably wrong.

EDIT: And some pools push out invalid LP's So far I've noticed Monkey doing it along with some others.

[joulesbeef]

It only resets pools with mine_Deepbit as role. And at least one of those blocks was from btcguild and the LP based ID was probably wrong.

EDIT: And some pools push out invalid LP's So far I've noticed Monkey doing it along with some others.

Ok then one more question.. i have both btcguild and deepbit on mine_deepbit.. so far just the one share on deepbit.. but why arent I mining btcguild if you know it was a block they solved?

[simonk83]

Ok, sorry guys, I'm confused, again   Firstly, what's re_rate, I haven't seen that mentioned anywhere until now?

Secondly, can someone just quickly tell me which pools I need to set to info if I'm trying out the new deepbit additions?

Sorry, I know it's annoying, but I appreciate the help

[Endeavour79]

latest version brings API error with

btcg
digbtc
polmine

[djex]

Ok, sorry guys, I'm confused, again   Firstly, what's re_rate, I haven't seen that mentioned anywhere until now?

Secondly, can someone just quickly tell me which pools I need to set to info if I'm trying out the new deepbit additions?

Sorry, I know it's annoying, but I appreciate the help

re_rate is the new system based off the pools hashrate. It's ment to be used on pools that delay stats like deepbit and BTCGuild.

With c00ws latest update you no longer need to set pools to info for mine_deepbit.

[c00w]

Just start with --startLP and have deepbit in you user.cfg. No need to play with anything else. No guarantees it works however.

[simonk83]

Ok, sorry guys, I'm confused, again   Firstly, what's re_rate, I haven't seen that mentioned anywhere until now?

Secondly, can someone just quickly tell me which pools I need to set to info if I'm trying out the new deepbit additions?

Sorry, I know it's annoying, but I appreciate the help

re_rate is the new system based off the pools hashrate. It's ment to be used on pools that delay stats like deepbit and BTCGuild.

With c00ws latest update you no longer need to set pools to info for mine_deepbit.

Ok, great.

So basically, all I need to do is set deepbit and btcguild to mine_deepbit, and leave everything else as I currently have it?  

Just start with --startLP and have deepbit in you user.cfg. No need to play with anything else. No guarantees it works however.

Awesome   Thanks, that's much easier.

[joulesbeef]

latest version brings API error with

btcg
digbtc
polmine

fairly confident that those all are having issues... except not sure about digbtc


did the new useragent get put in the newest hopper?

[simonk83]

latest version brings API error with

btcg
digbtc
polmine

fairly confident that those all are having issues... except not sure about digbtc


did the new useragent get put in the newest hopper?

Well, it was changed in git to a newer chrome version, but I found that this didn't help the API issues.  I changed mine to something else and it seems to be working.

[simonk83]

Hmm.  For some reason, even though I have it set to mine in user.cfg, Nofeemining always starts up disabled when I restart bitHopper....

Is this happening to anyone else?   Happens without fail here....

EDIT: Btcguild is doing it as well.  Starts up disabled.

[paraipan]

Hmm.  For some reason, even though I have it set to mine in user.cfg, Nofeemining always starts up disabled when I restart bitHopper....

Is this happening to anyone else?   Happens without fail here....

EDIT: Btcguild is doing it as well.  Starts up disabled.

pls do a search to see if you have duplicate entries in user.cfg