bitHopper: Python Pool Hopper Proxy

[amazingrando]

FYI, BTCSERV:

I have decided to stop offering Proportional Rewards after the next found block because it does not work parallelly to PPS without affecting it negatively. Even worse, it would cause losses if I would not severely cut one of the reward schemes, and thus offer significantly lower value than other pools, what is not what I want to do.

Currently I am calculating the rewards like this:

Code:

PROP: [user prop shares] / [total prop shares and pps shares] * 50
PPS: [user pps shares] * 0.000028125

Problem with both reward schemes parrallelly running is that the PPS Queue does not even out after a long round and a short round. In short rounds, which have a higher percentage of prop shares, you save only a bit with what you can feed the queue, but in long rounds, which have way higher share of pps shares, the queue is getting quite big very fast.

I have tried some different calculations but did not get an acceptable result. I dont know how other pools with PPS and PROP calculate the rewards. Maybe they experience the same flaw, maybe not. If someone has a solution for this I would be glad to hear it.

Btw, I have decided to stick to PPS since I am convinced it is the fairest of all reward schemes available. It's not in my interest to lose the hashing boost of pool hoppers, but I want to achieve a steadily increasing hash rate from regular users and not short term 150 GH/s and as soon as a round is near 43% see everyone leave.

[1713554148]

1713554148

[1713554148]

1713554148

[1713554148]

1713554148

[1713554148]

1713554148

[1713554148]

1713554148

[1713554148]

1713554148

[c00w]

Getwork issues should/may be fixed. Also we should reuse connections properly now.

[Ali]

It still requests work like mad (and therefore hangs) after a while on Eligius.

[amazingrando]

According to Coinotron, it looks like solidcoins are 20% more profitable than BTC atm.  Thus, I've added a couple of sc pools.  Currently sc difficulty is around 8000.  In the Bh stats, it shows the percentage for sc pools with respect to BTC bifficulty (1.77MM).  Does this mean that Bh will always stay on sc pools?  Should it be 43.5% of 8000? 

[johnj]

According to Coinotron, it looks like solidcoins are 20% more profitable than BTC atm.  Thus, I've added a couple of sc pools.  Currently sc difficulty is around 8000.  In the Bh stats, it shows the percentage for sc pools with respect to BTC bifficulty (1.77MM).  Does this mean that Bh will always stay on sc pools?  Should it be 43.5% of 8000? 

I think it's been updated


v0.2.4.8.zip — Oodles of bugfixes. Getwork Flooding should be gone. Miner Starvation should be reduced. Solidcoins have the correct diff and have a bunch of fixes.

[amazingrando]

According to Coinotron, it looks like solidcoins are 20% more profitable than BTC atm.  Thus, I've added a couple of sc pools.  Currently sc difficulty is around 8000.  In the Bh stats, it shows the percentage for sc pools with respect to BTC bifficulty (1.77MM).  Does this mean that Bh will always stay on sc pools?  Should it be 43.5% of 8000? 

I think it's been updated


v0.2.4.8.zip — Oodles of bugfixes. Getwork Flooding should be gone. Miner Starvation should be reduced. Solidcoins have the correct diff and have a bunch of fixes.

I am getting BH from github by cloning or pulling (I'm running Linux if that matters). Is the v0.2.4.8.zip version newer?  Where can I download it from?

[johnj]

I am getting BH from github by cloning or pulling (I'm running Linux if that matters). Is the v0.2.4.8.zip version newer?  Where can I download it from?

https://github.com/c00w/bitHopper/downloads

[amazingrando]

According to Coinotron, it looks like solidcoins are 20% more profitable than BTC atm.  Thus, I've added a couple of sc pools.  Currently sc difficulty is around 8000.  In the Bh stats, it shows the percentage for sc pools with respect to BTC bifficulty (1.77MM).  Does this mean that Bh will always stay on sc pools?  Should it be 43.5% of 8000?  

I think it's been updated


v0.2.4.8.zip — Oodles of bugfixes. Getwork Flooding should be gone. Miner Starvation should be reduced. Solidcoins have the correct diff and have a bunch of fixes.

Downloaded the v0.2.4.8 zip file.  Seems like it switched from solidcoins when it should, but the stats display is a bit confusing:

s0DigBTC.net (scc)   2,981  0.17%

Should be showing 36.15% if sc difficulty is 8,246.


EDIT:

I take back my earlier statement about switching working right.  For example, I've been stuck on mine4us even though it should have switched (the pool is at about 64% presently, when there are several other pools <43.5%)

mine-for.us (scc)   5,289 0.30%

EDIT:

I'm an idiot.  I in user.cfg I used mine, when I should have used mine_scc.  grrr    Everything appears to be working correctly

[organofcorti]

Anyone have any up to date info on Polmine? Did they end up doing the bcp-like taxing hoppers thing they were going to do, and do they still delay stats? I'm hopping them on mine_deepbit atm, and things look ok from my side, but if I can optimise the hop-point I'd like to. And I'm sure you'd all like me to, too. 

[iopq]

Anyone have any up to date info on Polmine? Did they end up doing the bcp-like taxing hoppers thing they were going to do, and do they still delay stats? I'm hopping them on mine_deepbit atm, and things look ok from my side, but if I can optimise the hop-point I'd like to. And I'm sure you'd all like me to, too. 

wait, what? I'm using just mine on it, am I behind the times?

[organofcorti]

Anyone have any up to date info on Polmine? Did they end up doing the bcp-like taxing hoppers thing they were going to do, and do they still delay stats? I'm hopping them on mine_deepbit atm, and things look ok from my side, but if I can optimise the hop-point I'd like to. And I'm sure you'd all like me to, too.  

wait, what? I'm using just mine on it, am I behind the times?

Ah, I could be - I've been busy on other related projects lately.

[HolodeckJizzmopper]

I would like to add my voice to issues hopping with 2.4.8. Last night, it refused to hop between BitClockers and MTRed despite both being <43%

EDIT: .. and just watched it ping-pong between Eligius and MTRed with MTRed being >49%, and Eligius as my backup pool, so something is... odd...

[joulesbeef]

if you have the hopper scrolling with rpc requests... are you using cgminer? cgminer above 1.61 has been causing thisw.

[phase]

if you have the hopper scrolling with rpc requests... are you using cgminer? cgminer above 1.61 has been causing thisw.

I also had this problem about a week ago when I tried it out, it would run fine for a couple of hours, then it would start flooding the screen with mumbo-jumbo and stop doing useful work. Does the problem still persist with cgminer 2.0? Any chance of this getting fixed?

[Rino]

I just had getwork spam again on current version  only using phoenix miners

[leveer]

Proxy shuts down periodically, with this coming at the end of both log files:

[21:55:06] Exception in wsgi server loop, restarting wsgi in 60 seconds

Any advice?

[c00w]

leveer can you post what exceptions appears?

And versions are just git tags. So if your are pulling you'll be on the latest version.

[leveer]

From logfile-errors:

Traceback (most recent call last):
  File "bitHopper.py", line 289, in <module>
    main()
  File "bitHopper.py", line 284, in main
    bithopper_instance.log_msg("Exception in wsgi server loop, restarting wsgi in 60 seconds\n%s") % (str(e))
TypeError: unsupported operand type(s) for %: 'NoneType' and 'str'

[leveer]

I should also ask why I might be getting this type of reject rate from slush:

4454 / 3754
84.28%

Might running 5 GH through a single instance of the proxy have anything to do with it?

[tysat]

I should also ask why I might be getting this type of reject rate from slush:

4454 / 3754
84.28%

Might running 5 GH through a single instance of the proxy have anything to do with it?

I had a similar issue when running that much power through the proxy.