bitHopper: Python Pool Hopper Proxy

[Clipse]

check your bitcoinpool stats, it was a lie that they don't cut 50%, even with 3% donation

is it possible to save slice in db, so it was remembered between start/stop of bithopper

or how can I disable slicing completely?

I just checked my submitted shares percentage of total shares and it still matches up with my estimated rewards.

[jkminkov]

check your bitcoinpool stats, it was a lie that they don't cut 50%, even with 3% donation

is it possible to save slice in db, so it was remembered between start/stop of bithopper

or how can I disable slicing completely?

I just checked my submitted shares percentage of total shares and it still matches up with my estimated rewards.

check previous round, how many total shares?

[Clipse]

check your bitcoinpool stats, it was a lie that they don't cut 50%, even with 3% donation

is it possible to save slice in db, so it was remembered between start/stop of bithopper

or how can I disable slicing completely?

I just checked my submitted shares percentage of total shares and it still matches up with my estimated rewards.

check previous round, how many total shares?

I wasnt in on the previous round so can only look at my current round shares compared to total share = estimate

That matches up, unless bitcoinpool makes 50% share value at round end which would be weird cause they usually decrease value of shares on the spot.

[organofcorti]

Good news everyone! 43% is dead!

We no longer have to hop at 0.43*difficulty!

I haven't been around much lately because I spent the last week running and rewriting 'byteHopper', a multiple pool hopping simulator. When when I got results I didn't want, I rewrote it from scratch. Three times.

Although I made it run faster each time the results are the same, and the cumulative distribution functions follow real world bitcoin results. So I'm finally happy with the results it gives.

I'm only posting a summary here and I'll get around to making blog posts on hoppersden to give more detail, but the gist of it is: If there are 3 or more hoppable pools, you can stay on pools as long as you want and still get the same long term reward as if you hopped on 0.43, but without needing backup and without pissing pool operators as much. Keep in mind that this is not a claim about one particular round, but over, say, 100000 rounds (which I used for the graphs below).

Of course in any given round, after total shares=diff, your shares are worth less than one. But over time the shorter rounds make up for it. Even with only 3 Prop and backup, your efficiency will always be about 1.83, unless you hop off *too soon*. With ten other pools you get about 250% over PPS - sound familiar?

tl;dr BOLD CLAIM: As long as you always hop to the pool with the lowest shares - regardless of hashspeed - you don't need to hop to backup at 0.43.

The ran up some quick graphs which show byteHopper results up to hopping at 3*diff for 0 other pools (ie one proportional pools and one PPS), 1 other pools, 3 other pools and 5 other pools, all plus pps when needed. '0 other pools' mean the same as Raulo's example, and gives the same results as his equation.

 This is basically not 'hopping' much at all. PPS only really has positive effect if you hop only one or two other pools.

                 

[creativex]

Kewl. You can tell from the LP triggers in the output window that a block has been found several seconds before pident or fasthop update. Is this common knowledge and I'm just slow?

Sweet! Chart porn! Will hafta wait till I'm actually awake.

Hey does anyone know if there's a way to force either the default or altslice schedulers to mine somewhere when they really don't wanna? For instance when Deepbit or BTCG are sitting there set to mine_deepbit 1,888,786 shares and 100% is there some way to force them to mine? I tried penalty .01 and every role combination(I think), but they just sit there like dummies.

[jkminkov]

check your bitcoinpool stats, it was a lie that they don't cut 50%, even with 3% donation

is it possible to save slice in db, so it was remembered between start/stop of bithopper

or how can I disable slicing completely?

I was wrong about bitcoinpool, earning are fine for block 140048 :x

[simonk83]

Code:

[20:22:23] Error in pool api for arsbitcoin
[20:22:23] Error in pool api for arsbitcoin
[20:22:23] Error in pool api for arsbitcoin
[20:22:23] Error in pool api for arsbitcoin
[20:22:23] Error in pool api for arsbitcoin
[20:22:23] Error in pool api for arsbitcoin
[20:22:23] Error in pool api for arsbitcoin
[20:22:23] Error in pool api for arsbitcoin
[20:22:24] Error in pool api for arsbitcoin
[20:22:24] Error in pool api for arsbitcoin
[20:22:24] Error in pool api for arsbitcoin
[20:22:24] Error in pool api for arsbitcoin
[20:22:24] Error in pool api for arsbitcoin
[20:22:24] Error in pool api for arsbitcoin
[20:22:24] Error in pool api for arsbitcoin
[20:22:24] Error in pool api for arsbitcoin
[20:22:24] Error in pool api for arsbitcoin
[20:22:24] Error in pool api for arsbitcoin
[20:22:24] Error in pool api for arsbitcoin
[20:22:24] Error in pool api for arsbitcoin
[20:22:24] Error in pool api for arsbitcoin
[20:22:24] Error in pool api for arsbitcoin
[20:22:24] Error in pool api for arsbitcoin
[20:22:24] Error in pool api for arsbitcoin
[20:22:24] Error in pool api for arsbitcoin
[20:22:25] Error in pool api for arsbitcoin
[20:22:25] Error in pool api for arsbitcoin
[20:22:25] Error in pool api for arsbitcoin
[20:22:25] Error in pool api for arsbitcoin
[20:22:25] Error in pool api for arsbitcoin
[20:22:25] Error in pool api for arsbitcoin
[20:22:26] Error in pool api for arsbitcoin
[20:22:26] Error in pool api for arsbitcoin
[20:22:26] Error in pool api for arsbitcoin
[20:22:26] Error in pool api for arsbitcoin
[20:22:26] Error in pool api for arsbitcoin
[20:22:26] Error in pool api for arsbitcoin
[20:22:26] Error in pool api for arsbitcoin
[20:22:26] Error in pool api for arsbitcoin
[20:22:26] Error in pool api for arsbitcoin
[20:22:26] Error in pool api for arsbitcoin
[20:22:26] Error in pool api for arsbitcoin
[20:22:26] Error in pool api for arsbitcoin
[20:22:26] Error in pool api for arsbitcoin
[20:22:26] Error in pool api for arsbitcoin
[20:22:26] Error in pool api for arsbitcoin
[20:22:26] Error in pool api for arsbitcoin
[20:22:26] Error in pool api for arsbitcoin
[20:22:26] Error in pool api for arsbitcoin
[20:22:26] Error in pool api for arsbitcoin
[20:22:26] Error in pool api for arsbitcoin
[20:22:26] Error in pool api for arsbitcoin

Latest version.   Happening a lot....  Not just ars, was doing the same for slush earlier as well.

[Endeavour79]

I am not sure if there is an issue or if I understand the hopping method wrong but why does the actual version stick to one pool (polmine in my case) and does not switch to other pools, even if they have very few roundshares shares and much less compared to the other pools. (<43%)

Tried default and AltSliceScheduler..

[simonk83]

I am not sure if there is an issue or if I understand the hopping method wrong but why does the actual version stick to one pool (polmine in my case) and does not switch to other pools, even if they have very few roundshares shares and much less compared to the other pools. (<43%)

Tried default and AltSliceScheduler..

Is there a number in the "slice" column of the stats page?

[simonk83]

Another issue I've just noticed with the slicing is that if a pool turns red for whatever reason, the slices are lost, so if you're in the middle of alternating between 2 or more pools, and one goes red, it drops out of the slice.    Then when it gets picked up again it has to spend however long catching up to the other pools before they get hopped again. 

Maybe try and tell it to remember the slice value it was last up to before it turned red, then add some sort of monitor so that when it's available again it resumes from where it was.

On that, it'd be really good to have a timer on api_disable as well that checks every so often if the pool API is back up.     ozcoin must have had some issues earlier and by the time I got to it (a couple of hours) it was stuck on api_disable until I manually restarted it.

[Endeavour79]

I am not sure if there is an issue or if I understand the hopping method wrong but why does the actual version stick to one pool (polmine in my case) and does not switch to other pools, even if they have very few roundshares shares and much less compared to the other pools. (<43%)

Tried default and AltSliceScheduler..

Is there a number in the "slice" column of the stats page?

No..there is no Slice count..column is empty. Efficiency stays at 0% too.
User Shares are increasing.

[simonk83]

I am not sure if there is an issue or if I understand the hopping method wrong but why does the actual version stick to one pool (polmine in my case) and does not switch to other pools, even if they have very few roundshares shares and much less compared to the other pools. (<43%)

Tried default and AltSliceScheduler..

Is there a number in the "slice" column of the stats page?

No..there is no Slice count..column is empty. Efficiency stays at 0% too.
User Shares are increasing.

Ignore efficiency, you need to manually mess with that by editing the Payout figure.  We'll get to that later.

So you obviously have polmine set up and I assume ozcoin as well.    Polmine shouldn't be touched right now as it's over 43% so I'm not sure why it's mining there...  maybe restart bithopper.

At the moment, for me, it's cycling between ozcoin, bitcoins.lc and kiwipool.   bitcoins.lc just hit 43% so it'll stop touching that in a sec.

[Endeavour79]

switched back to OldDefaultScheduler for the moment

[Endeavour79]

So you obviously have polmine set up and I assume ozcoin as well.    Polmine shouldn't be touched right now as it's over 43% so I'm not sure why it's mining there...  maybe restart bithopper.

At the moment, for me, it's cycling between ozcoin, bitcoins.lc and kiwipool.   bitcoins.lc just hit 43% so it'll stop touching that in a sec.

Yes, I have polmine and a bunch of other pools.
Somehow bithopper switches but only for a short time (let's say ~2min) and then goes back to polmine for another 10min or so..
Ozco (with lowest round shares) is completely ignored (I've set it to mine_charity).

[organofcorti]

From what I can tell, any of the slicers reduce variance at the cost of payout. I'll try to write a sim mimicking it if someone can post a non code algo for me to translate.

I'm sticking with oldDefaultScheduler - I get around 250% on average with that which is about the max efficiency for 10 pools, normally scheduled. Perfect.

[simonk83]

Hmm.  Ok, that's over my head, we'll have to wait for one of the smart people

I just got a massive super fast scrolly heap of errors and had to restart the client.   Could be coincidence but it happened right as bclc hit 43% and I hopped away.

[Endeavour79]

Would be nice if some smart guy could take some time and write a summary about the 3 different schedulers (old, default, altslice), what they do, how they (should) work and what the pros/cons are..
Development was so fast in the last days, so many changes...I feel lost with what to set and what not..I believe others feel confused too..

We need a WIKI!

[GoMaD]

some errors

Code:

2011-08-08 13:10:15+0200 [HTTP11ClientProtocol,client] Error in pool api for itzod
2011-08-08 13:10:15+0200 [HTTP11ClientProtocol,client] "[Failure instance: Traceback: <type 'exceptions.ValueError'>: No JSON object could be decoded\n/usr/lib/python2.7/dist-packages/twisted/internet/defer.py:1076:gotResult\n/usr/lib/python2.7/dist-packages/twisted/internet/defer.py:1063:_inlineCallbacks\n/usr/lib/python2.7/dist-packages/twisted/internet/defer.py:361:callback\n/usr/lib/python2.7/dist-packages/twisted/internet/defer.py:455:_startRunCallbacks\n--- <exception caught here> ---\n/usr/lib/python2.7/dist-packages/twisted/internet/defer.py:542:_runCallbacks\n/home/mgus/bitOri/pool.py:152:selectsharesResponse\n/usr/lib/python2.7/json/__init__.py:326:loads\n/usr/lib/python2.7/json/decoder.py:360:decode\n/usr/lib/python2.7/json/decoder.py:378:raw_decode\n]"
2011-08-08 13:10:16+0200 [HTTP11ClientProtocol,client] Error in pool api for digbtc
2011-08-08 13:10:16+0200 [HTTP11ClientProtocol,client] "[Failure instance: Traceback: <type 'exceptions.AttributeError'>: 'NoneType' object has no attribute 'group'\n/usr/lib/python2.7/dist-packages/twisted/internet/defer.py:1076:gotResult\n/usr/lib/python2.7/dist-packages/twisted/internet/defer.py:1063:_inlineCallbacks\n/usr/lib/python2.7/dist-packages/twisted/internet/defer.py:361:callback\n/usr/lib/python2.7/dist-packages/twisted/internet/defer.py:455:_startRunCallbacks\n--- <exception caught here> ---\n/usr/lib/python2.7/dist-packages/twisted/internet/defer.py:542:_runCallbacks\n/home/mgus/bitOri/pool.py:177:selectsharesResponse\n]"

[Endeavour79]

btw..some silly question..

I really like Ozco and would like to mine there when currently no other pool is good for mining..

Can I setup Ozco 2 times? One time as mine_charity and one time as backup? Is this supported??

[Litt]

funny right now how ozco is not releasing next set of stats for 10min when it's at 42%... 20min in now and counting still. Last one updated exactly at 10mins.  


EDIT: ok updated after 22mins stuck at 42% after I posted this.