bitHopper: Python Pool Hopper Proxy

[simonk83]

Only default and slice do anything. The others are placeholders.

And I think I fixed slice. Again.

Only been running for a few minutes, but it SEEMS to be working.

Edit:  Actually, before I say if its working or not, what is it SUPPOSED to do?  I have 3 pools under 43% right now.  Should it just jump through all 3 pools?  If so, is there a set time period?  What triggers the hop?

Yes, this would be good to know.   Mine seems to be stuck on BTCPool24 again.

Mine is stuck on polmine.pl for 18 minutes now

Do you have BTCPool24 enabled as a miner?    Technically mine should be on bitcoins. Lc now.

[1714169960]

1714169960

[1714169960]

1714169960

[1714169960]

1714169960

[MaGNeT]

Only default and slice do anything. The others are placeholders.

And I think I fixed slice. Again.

Only been running for a few minutes, but it SEEMS to be working.

Edit:  Actually, before I say if its working or not, what is it SUPPOSED to do?  I have 3 pools under 43% right now.  Should it just jump through all 3 pools?  If so, is there a set time period?  What triggers the hop?

Yes, this would be good to know.   Mine seems to be stuck on BTCPool24 again.

Mine is stuck on polmine.pl for 18 minutes now

Do you have BTCPool24 enabled as a miner?    Technically mine should be on bitcoins. Lc now.

Nope, still have the API_disable error when enabling BTCPool24, but if it works for you, I must have done something wrong in the config?

[c00w]

This should swap between all mine able pools evenly spending time on each of them.

If none are mineable then it swaps to a backup.

[paraipan]

mine stuck with polmine and putting it on info or disable doesn't seem to matter

edit: where is macboy80 ? I'm gonna give him a chat, he f.. up a little bit the stats page, the colors look nice but has lost functionality, grr

edit2: I retry that, sorry macboy, it's the scheduler, without it enabled changing roles in stats page works like charm, this time I freaked out

[MaGNeT]

mine stuck with polmine and putting it on info or disable doesn't seem to matter

Running on the back-up now... Wait for the next c00w update

[joulesbeef]

Ok after finally figuring out how to use gitHub I uploaded my changes and made a pull request. For anyone who wants to check it out go here https://github.com/gtrrkicw/bitHopper

edit: This scheduler will hop between pools that are <43% every 10 minutes in a round robin. Not sure if that was the intention or not but it seems logical to me.

this is working for me..it appears to jump every 10 minutes to a proper pool.

Just fired up your new one c00w and well let ya know what i see.
how often is it supposed to hope so I can get an idea of when to look?

right now it seems to have been at BTCpool24 for 4 minutes so far

edit: 11 minutes BTCpool24

[MaGNeT]

Put back my old back-up and see what the morning brings...

It's 0:27 over here... Bed time... See you later!  I hop(e) to get my 7:30 hours of sleep

[djex]

So for some reason it likes to get stuck on BTCPool24.

[muyoso]

OK, testing out the latest c00w now.  

Pools at at:

MtRed 7%
Bitcoins.lc 26%
BTCpool24 15%
Bitclockers 33%


Started mining at MtRed.  Will keep track of what it does by editing this comment.

Edit:

After 8 minutes it jumped from MtRed to Bitclockers.  


Aaaaaaaaaaaaaaand then it mined on bitclockers for 15 minutes never switching again.  Also, threw multiple errors for the first time ever from bithopper in my miner:

Code:

Deferred:
Unhandled Error
Traceback (most recent call last):
  File "twisted\internet\defer.pyc", line 361, in callback

  File "twisted\internet\defer.pyc", line 455, in _startRunCallback

  File "twisted\internet\defer.pyc", line 542, in _runCallbacks

  File "twisted\internet\defer.pyc", line 1076, in gotResult

--- <exception caught here> ---
  File "twisted\internet\defer.pyc", line 1020, in _inlineCallbacks

  File "minerutil\RPCProtocol.pyc", line 226, in _requestComplete

  File "minerutil\RPCProtocol.pyc", line 319, in handleWork

exceptions.TypeError: argument of type 'NoneType' is not iterable

[paraipan]

So for some reason it likes to get stuck on BTCPool24.

yep, something is not right, 40593 seconds from beginning of the round (11 hours) at 30Gh on average (have seen 50Gh+), has only 288422 shares...

[ed64]

So for some reason it likes to get stuck on BTCPool24.

yep, something is not right, 40593 seconds from beginning of the round (11 hours) at 30Gh on average (have seen 50Gh+), has only 288422 shares...

Try my AltSliceScheduler: https://github.com/echiu64/bitHopper
Use options like

Code:

--scheduler AltSliceScheduler --altslicesize=1200

Default is 600 "slice" or "pie" size, in that the 600 will be divided amongst the pools, weighted by their share count.

For really fast switch set it to 60. Takes about a minute or so to wait for all the stats to initialize and have the slice redistribution get set. Not sure if there is a better way to trigger this earlier.

Still using the previous stats page for the alt slice scheduler, so should be functional...

You can see the time slice count on the stats page as well and will decrement over time. The next largest slice will be selected. Once all are exhausted, slices are recalculated...

Credit goes to flowers for the original implementation

[simonk83]

So for some reason it likes to get stuck on BTCPool24.

yep, something is not right, 40593 seconds from beginning of the round (11 hours) at 30Gh on average (have seen 50Gh+), has only 288422 shares...

So disable it for now you reckon?

[paraipan]

So for some reason it likes to get stuck on BTCPool24.

yep, something is not right, 40593 seconds from beginning of the round (11 hours) at 30Gh on average (have seen 50Gh+), has only 288422 shares...

So disable it for now you reckon?

I did   just trying to find out if they're scr...g with us

[flower1024]

So for some reason it likes to get stuck on BTCPool24.

yep, something is not right, 40593 seconds from beginning of the round (11 hours) at 30Gh on average (have seen 50Gh+), has only 288422 shares...

Try my AltSliceScheduler: https://github.com/echiu64/bitHopper
Use options like

Code:

--scheduler AltSliceScheduler --altslicesize=1200

Default is 600 "slice" or "pie" size, in that the 600 will be divided amongst the pools, weighted by their share count.

For really fast switch set it to 60. Takes about a minute or so to wait for all the stats to initialize and have the slice redistribution get set. Not sure if there is a better way to trigger this earlier.

Still using the previous stats page for the alt slice scheduler, so should be functional...

You can see the time slice count on the stats page as well and will decrement over time. The next largest slice will be selected. Once all are exhausted, slices are recalculated...

Credit goes to flowers for the original implementation

really nice! thank you very much for that.

just a little suggestion:

if "reslice" occurs don't take the pool with the biggest slice. instead check if the current pool got another slice and if so stay there -> reducing hopping a little and worked well for me (i changed it in a later version, so you might not have catched it up).

i'll switch to your version now. do you want me to make the suggestion as a pull request? its really not much

[owowo]

c00w <3 just a small thingy, BTCworld.de shows up in the bitHopper-page as BTCworld.COM a little confusing... ;o)

[simonk83]

Let me just make sure I'm reading this right.  I should basically be enabling ALL the backup pools and setting them all to backup_latehop?

[djex]

Is polmine.pl down for anyone else?

[paraipan]

Let me just make sure I'm reading this right.  I should basically be enabling ALL the backup pools and setting them all to backup_latehop?

not all, only the backup pools you use

[dribbits]

Is polmine.pl down for anyone else?

Yep, not working here either.

[paraipan]

Is polmine.pl down for anyone else?

yep, down here too, ozco is back, mt.red got a lucky one, and btcpool24 posibly faking stats (collecting info) EXTRA

edit: btcpool24 changed their payout system with an unknown one and their json stats seem to have a life of their own