bitHopper: Python Pool Hopper Proxy

[paraipan]

@Dikidera, everyone on a forum gets pounded on every now and the -  if you're as 4-channy as you seem you know that. We've all posted things on the spur of the moment we're not proud of, and we've all has people annoy us and there is always the temptation to keep the flame burning. But there is never an excuse for using all caps. So let's just pretend page 39 edit 39 and 40 didn't happen and start again.

I'm sure you could spend time 4-channing us, but this is a really good proxy once you understand how it works and why.

1. Pool hopping currently works well only on proportional pools and only when you have access to non-delayed total shares. Neither btcguild or deepbit provide usable total share stats.
2. bitHopper provides a user stats page you can access on your browser on 127.0.0.1 which shows efficiency. You'll be able to see it work and see how far ahead you are by using it.
3. Since I've been using bitHopper I've had 140% to 200% efficiency on pools we use, for a total of 160%. Multipool's efficiency is around 120%.
4. Challenges coming up: loss of usable pools stats.

If you do have real coding skills (which is what I assume you're referring to when you recommend we don't anger you, and not that you've had an accident with a radioactive substance and go green and ragey when you get cranky) then help the project! We could do with someone helping with html scraping.

Why is there a problem with delayed stats? Pool hopping is just that. You request work, send a share, switch, send a share, switch and so on....this is not how i imagine pool hopping to be.

Sup Pinky, where is the Brain ?

Did i give you permission to speak slave?

dont't start another round of that shit, this time I will personally see that the guilty gets banned. I came here to read good stuff not the ppl's personal vendetta's

btw: if a pool delays stats you cannot hopp in blindfolded, not knowing this tells us you are 1. a script kiddie jerkin' around 2. you are a pool op looking for trouble after seeing his pool hopped. In either case i recommend you reading at least some pages of this thread or go to another part of bitcoins.org forum, it' huge and you could fit perfectly in other thread

[1714282241]

1714282241

[1714282241]

1714282241

[paraipan]

latest Mod fully supports NameCoin pools
added BitParking and NameBit



if you feel lucky, now you can donate NMC to me

yup with pleasure (btc adress not in sight )

ryouiki would be hard to implement a basic password to stat page ? If you do it , great, if not please explain how to coz having it wide open on public ip just makes me feel uncomfortable. thanks

[flower1024]

use a firewall and tunnel this port through ssh.
works fine for me (i am using my hopper on a vserver)

[paraipan]

use a firewall and tunnel this port through ssh.
works fine for me (i am using my hopper on a vserver)

I was doing that until a few friends decided to give a hand mining and they lack the patience to do advanced pc stuff
want to give some info on public ip to a select few persons (I know they could mess with enabling an setting penalty but they have been warned about that >

[dikidera]

@Dikidera, everyone on a forum gets pounded on every now and the -  if you're as 4-channy as you seem you know that. We've all posted things on the spur of the moment we're not proud of, and we've all has people annoy us and there is always the temptation to keep the flame burning. But there is never an excuse for using all caps. So let's just pretend page 39 edit 39 and 40 didn't happen and start again.

I'm sure you could spend time 4-channing us, but this is a really good proxy once you understand how it works and why.

1. Pool hopping currently works well only on proportional pools and only when you have access to non-delayed total shares. Neither btcguild or deepbit provide usable total share stats.
2. bitHopper provides a user stats page you can access on your browser on 127.0.0.1 which shows efficiency. You'll be able to see it work and see how far ahead you are by using it.
3. Since I've been using bitHopper I've had 140% to 200% efficiency on pools we use, for a total of 160%. Multipool's efficiency is around 120%.
4. Challenges coming up: loss of usable pools stats.

If you do have real coding skills (which is what I assume you're referring to when you recommend we don't anger you, and not that you've had an accident with a radioactive substance and go green and ragey when you get cranky) then help the project! We could do with someone helping with html scraping.

Why is there a problem with delayed stats? Pool hopping is just that. You request work, send a share, switch, send a share, switch and so on....this is not how i imagine pool hopping to be.

Sup Pinky, where is the Brain ?

Did i give you permission to speak slave?

dont't start another round of that shit, this time I will personally see that the guilty gets banned. I came here to read good stuff not the ppl's personal vendetta's

btw: if a pool delays stats you cannot hopp in blindfolded, not knowing this tells us you are 1. a script kiddie jerkin' around 2. you are a pool op looking for trouble after seeing his pool hopped. In either case i recommend you reading at least some pages of this thread or go to another part of bitcoins.org forum, it' huge and you could fit perfectly in other thread

Do you...understand the meaning of what script kiddie means? I don't think you do.  And no, i am not a pool operator though i did start writing my front end once only to find it a bother to maintain a pool.

[zybron]

Heh, triplemining added an odd bit of code to their stats page:

Code:

<tr style="background-color: #ECF7FA;">
<td>-</td>
<td>MINING</td>
<td>-</td>

<td>-</td>
<td>3 hours </td>
<td><!-- 1000 -->321001</td>
<td>-</td>
</tr>

I don't think it had the effect they wanted, though. Instead of bitHopper seeing the 1000 and assuming they are on a new block, it doesn't catch this line at all in the scrape and is grabbing the stats for the previous block. Or perhaps that was the intended effect?

It's funny that they have "No pool hopping protection!" on their home page, but want to start mucking with code to prevent/deter hopping?

[muyoso]

Yea, should be mining at triple right now but for some reason their stats are reporting way too high.

[organofcorti]

Heh, triplemining added an odd bit of code to their stats page:

Code:

<tr style="background-color: #ECF7FA;">
<td>-</td>
<td>MINING</td>
<td>-</td>

<td>-</td>
<td>3 hours </td>
<td><!-- 1000 -->321001</td>
<td>-</td>
</tr>

I don't think it had the effect they wanted, though. Instead of bitHopper seeing the 1000 and assuming they are on a new block, it doesn't catch this line at all in the scrape and is grabbing the stats for the previous block. Or perhaps that was the intended effect?

It's funny that they have "No pool hopping protection!" on their home page, but want to start mucking with code to prevent/deter hopping?

Except that Triplemining is now stuck on 143849 shares for me, and bitHopper won't mine them because it's been on that for so long.

[flower1024]

Except that Triplemining is now stuck on 143849 shares for me, and bitHopper won't mine them because it's been on that for so long.

change in pool.py:

re.search(r"<td><!-- 1000 -->[0-9]*</td>", statpage).group(0)[17:-5]

[frisco]

@c00w: if I update to a new version, how do I keep my stats to that point?

If you just update everything works as it should, and data is persisted.

Triplemining stats are the last block stats ( 2859868 ) and probably due to them messing the results I got the pool at a "stats api disabled" state (I can recall the actual state name).

Enabling/disabling pools on the stats page should be changed to links or selects, typing is not easy with the updater js running every few secs and reverting your writing and not everyone knows every possible state.

Also as a request, a new --log param to write directly to file (if possible a rolling file) would be great I think I have been able to configure everything as it should using logrotate but it is not easy and still the daily log files are quite big using debug.

_{I am running latest version from GH}

[gno]

One rule: Never, ever, ever make me angry, which you are doing right now.

As for the readme, i read it...not much of an explanation there.

Also, it seems it's NOT using btcguild.

Looks like we've got an e-thug here, folks...

[paraipan]

One rule: Never, ever, ever make me angry, which you are doing right now.

As for the readme, i read it...not much of an explanation there.

Also, it seems it's NOT using btcguild.

Looks like we've got an e-thug here, folks...

"we've got" you said it, let's not make it bigger than it is

[organofcorti]

@c00w: if I update to a new version, how do I keep my stats to that point?

If you just update everything works as it should, and data is persisted.

Triplemining stats are the last block stats ( 2859868 ) and probably due to them messing the results I got the pool at a "stats api disabled" state (I can recall the actual state name).

Enabling/disabling pools on the stats page should be changed to links or selects, typing is not easy with the updater js running every few secs and reverting your writing and not everyone knows every possible state.

Also as a request, a new --log param to write directly to file (if possible a rolling file) would be great I think I have been able to configure everything as it should using logrotate but it is not easy and still the daily log files are quite big using debug.

_{I am running latest version from GH}

git fetch?

[frisco]

@c00w: if I update to a new version, how do I keep my stats to that point?

If you just update everything works as it should, and data is persisted.

Triplemining stats are the last block stats ( 2859868 ) and probably due to them messing the results I got the pool at a "stats api disabled" state (I can recall the actual state name).

Enabling/disabling pools on the stats page should be changed to links or selects, typing is not easy with the updater js running every few secs and reverting your writing and not everyone knows every possible state.

Also as a request, a new --log param to write directly to file (if possible a rolling file) would be great I think I have been able to configure everything as it should using logrotate but it is not easy and still the daily log files are quite big using debug.

_{I am running latest version from GH}

git fetch?

Thats ok, I have persisted the data the last two days doing

Code:

git pull origin

from time to time.

[ed64]

Ryouiki, think you can merge in c00w's payout stats in order to show show efficiency stats? Would like to see how some of my pools that I'm hopping are performing...

I added in slush and I'm pretty sure it's performing decently, would like to have something tracked vs some adhoc calculations on my part.

[Sukrim]

Except that Triplemining is now stuck on 143849 shares for me, and bitHopper won't mine them because it's been on that for so long.

change in pool.py:

re.search(r"<td><!-- 1000 -->[0-9]*</td>", statpage).group(0)[17:-5]

Or, even better (if they change the "1000" in the code:
"-->[0-9]*</td>", as they even nicely mark the relevant line with that! Just make sure to check the slicing of the string afterwards (and if they start inserting more comments, you'll maybe need a different regex alltogether or just a real HTML parser).

Slush should be hopped out already at ~14% afaik though, their scoring algorithm is faulty - search around a bit, I think Multipool did it like this too.

[zybron]

Has anyone else seen this pop up before?

Code:

[09:05:57] LP triggered from server triplemining
[09:05:57] Reading LP Response failed

And does that mean that a long poll came in from the pool but wasn't passed on to the miner? Or did the miner not pass back a valid response?

[Clipse]

Has anyone else seen this pop up before?

Code:

[09:05:57] LP triggered from server triplemining
[09:05:57] Reading LP Response failed

And does that mean that a long poll came in from the pool but wasn't passed on to the miner? Or did the miner not pass back a valid response?

I get this error also from time to time, all I can figure out around the meaning of it is that your miner requested LP from triplemining but the request wasnt answered fast enough thus timed out/failed.

Ive noticed this afaik only on triplemining from time to time.

[ed64]

For triple, I'd suggest something more like:

Code:

def triple_sharesResponse(self, response):
        output = re.search(r"<td><!-- [0-9]* -->([0-9]+)</td>", response)
        if output != None:
            match = output.group(1)
            round_shares = int(match)
            self.UpdateShares('triple',round_shares)

And get rid of specific character positions as much as possible this way...

[jkminkov]

it would be wise to move mine_address in passwords.py, some pools offer more than one server