bitHopper: Python Pool Hopper Proxy

[GenTarkin]

slush just got a new block and the hopper didnt switch over to it, its still making sure the other hoppable pools slice accounts are "caught up" =(...  I want slush to take priority over those...grr

[EskimoBob]

...
This is not a big deal really but since jumping off at 43% has no purpose when there are more than three pools, change your jump off to say 'difficulty' might obscure you as a hopper, and not lose you coinage.

Do I understand you correctly, that if I set the Penalty below 1, I'll stay longer in that pool and actually lose nothing in the long run?
 

[organofcorti]

...
This is not a big deal really but since jumping off at 43% has no purpose when there are more than three pools, change your jump off to say 'difficulty' might obscure you as a hopper, and not lose you coinage.

Do I understand you correctly, that if I set the Penalty below 1, I'll stay longer in that pool and actually lose nothing in the long run?
 

If you set it for all pools, yes. It might be easier to set the threshold to 1.0*difficulty though.

[EskimoBob]

I have polmine on info until i work it out.. i will watch both numbers and see which is a lie when a block is found

What did you find out?

home page:
Current round start:  
2011-08-08 16:26:42
Current round duration:  
0 dni 7 godzin 24 minut 59 sekund
Valid round shares/total:  
124 276

BH shows: 124276 6.58% and mines

[bb]

So does this mean bclc is safe to mine on now?

Yes and no. 

I dont know if they are still delaying stats.  If they are, you will still come out ahead on most rounds but efficiency is not going to be fantastic.  If they are not delaying stats, then yes its pretty safe to mine on.

Also, the owner of the pool has not been kind to miners.  I am going to mine them but constantly keep an eye on whether they are gaming stats or not.

Does anybody have new data on this? Is bclc still delaying stats?

Also, is BTC Guild still delaying stats?

[Clipse]

Well not sure how the digbit admin correlates chrome with attackers but here is hes explaination for chrome user-agent not working:

Code:

Yes, it only limit chrome Chrome/13.0.782.109, because attack are using this.

[c00w]

I think I have fixed deepbit hopping to work. My changes to the scheduler were not set up correctly. On a visual front i forgot to reverse the byte order for the block number.

EDIT: These changes aren't on github yet. I'm still testing.

[gnaget]

Well not sure how the digbit admin correlates chrome with attackers but here is hes explaination for chrome user-agent not working:

Code:

Yes, it only limit chrome Chrome/13.0.782.109, because attack are using this.

Easy, he is associating chrome with the attackers because we are the attackers.  The stat check system in bh is being mistaken as DDOS attacks by many of the pools.  BitMinerUnion moved over today because of DDOS attacks, and I'm sure it was us

[organofcorti]

@organofcorti I don't really get what you're trying to say, all the graphs seem to indicate overall eff. > 1 and that's what really matters to me (liked the 4th one)

All I'm saying is if you have more than three pools, the only hopping you have to do is when another pool has fewer shares than the one you're on. You shouldn't have to jump to backup at  43% - this number its only useful if you have one proportional pool and one pps pool. So if any pool ops are checking for you hopping off at 43%, not hopping off then won't have an effect on your long term earnings.

[c00w]

@organ
What about slicing? Worth it or not?

[paraipan]

Well not sure how the digbit admin correlates chrome with attackers but here is hes explaination for chrome user-agent not working:

Code:

Yes, it only limit chrome Chrome/13.0.782.109, because attack are using this.

LOL , take your pick guys http://www.user-agents.org/

[Clipse]

Well that reminds me.

Why not have pool stats refresh at something more decent, 3-5mins only, or if Longpoll identified refresh all pools listed shares.

Even better, we should get a bithopper central api where everyone can point to fetch stats, then it will never get flagged as ddos since there is only one point of fetching.
It would remove alot of hammering.

[gnaget]

I have polmine on info until i work it out.. i will watch both numbers and see which is a lie when a block is found

What did you find out?

home page:
Current round start:  
2011-08-08 16:26:42
Current round duration:  
0 dni 7 godzin 24 minut 59 sekund
Valid round shares/total:  
124 276

BH shows: 124276 6.58% and mines

They're fucking with us.  Their last block was discovered at 2:26 GMT and it changed around 9:30 GMT, 6 hours later.  And, it changed after a period of downtime.  I still have them on info, don't trust them.

[bb]

The update interval could be dynamically increased on small pools with slowly changing stats.

This probably needs a few lines of code though.

[joulesbeef]

@organofcorti I don't really get what you're trying to say, all the graphs seem to indicate overall eff. > 1 and that's what really matters to me (liked the 4th one)

All I'm saying is if you have more than three pools, the only hopping you have to do is when another pool has fewer shares than the one you're on. You shouldn't have to jump to backup at  43% - this number its only useful if you have one proportional pool and one pps pool. So if any pool ops are checking for you hopping off at 43%, not hopping off then won't have an effect on your long term earnings.

ok yeah that actually makes sense until you get over 100% then they start to be worth less than PPS

and yeah you still want to slice, due to slow pools staying below everyone for so long


but we shouldnt need the 43%

[paraipan]

I have polmine on info until i work it out.. i will watch both numbers and see which is a lie when a block is found

What did you find out?

home page:
Current round start:  
2011-08-08 16:26:42
Current round duration:  
0 dni 7 godzin 24 minut 59 sekund
Valid round shares/total:  
124 276

BH shows: 124276 6.58% and mines

They're fucking with us.  Their last block was discovered at 2:26 GMT and it changed around 9:30 GMT, 6 hours later.  And, it changed after a period of downtime.  I still have them on info, don't trust them.

you're maybe right...

Current round start:   
2011-08-08 16:26:42
Current round duration:   
0 dni 8 godzin 0 minut 38 sekund
Valid round shares/total:   
202 453

Previous round start:   
2011-08-08 04:52:03
Previous round duration:
0 dni 11 godzin 34 minut 39 sekund
Total amount of shares:
93 406 617

3 round ago...

66)    97,50% (wypłacony) Tx: 6fea3409    ( ..... / 838229) * 50.04043018   ...............   2011-08-08 04:52:03   0 dni 3 godz. 57 min. 16 sek.

they managed to stuff >800.000 shares in 4 hours with "help" of course but at a stable pool rate of ~150Gh/s

[MaGNeT]

@organofcorti I don't really get what you're trying to say, all the graphs seem to indicate overall eff. > 1 and that's what really matters to me (liked the 4th one)

All I'm saying is if you have more than three pools, the only hopping you have to do is when another pool has fewer shares than the one you're on. You shouldn't have to jump to backup at  43% - this number its only useful if you have one proportional pool and one pps pool. So if any pool ops are checking for you hopping off at 43%, not hopping off then won't have an effect on your long term earnings.

ok yeah that actually makes sense until you get over 100% then they start to be worth less than PPS

and yeah you still want to slice, due to slow pools staying below everyone for so long


but we shouldnt need the 43%

I like to test for a few days.

Just put in --threshold 100 ?

[bb]

I did some heavy work on the pool status site on the wiki to make it more readable and up to date. Any help is appreciated.

[organofcorti]

@organ
What about slicing? Worth it or not?

Not sure. I haven't attempted a byteHopper simulation because I need the decision tree for slicing so i can translate to an algo in R. But mathematically speaking, the earliest shares in a round are worth the most. Knowing that 43% doesn't mean anything but that the earliest shares do, I don't think slicing will do anything other than reduce variation at the cost of reducing payout.

[Keninishna]

anyone know why my hashrate is all over the place. It goes anywhere from 300 mh/s to 1200 mh/s. polmine is going at 500 mh/s now for me.