bitHopper: Python Pool Hopper Proxy

[organofcorti]

New prop pool UnitedMiners.com

Here is the config for the pool

Code:

[unitedminers]
name: unitedminers.com
mine_address: pool.unitedminers.com:8332 
user: 
pass: 
api_address:http://www.unitedminers.com/?action=statistics
api_method:re
api_key:align="right">Shares for current round:</th><td>([,0-9]+)</td></tr></table></div><div
api_strip:','
role:mine

I think you should let the pool owner know his pool will go from 4Ghps to 150Ghps before you post a config. It might not handle it.

[1715055323]

1715055323

[1715055323]

1715055323

[1715055323]

1715055323

[1715055323]

1715055323

[jkminkov]

I think you should let the pool owner know his pool will go from 4Ghps to 150Ghps before you post a config. It might not handle it.

but it's a....

A reliable and fault tolerant mining pool.

[Sukrim]

He'll find out the hard way anyways!

And hey, they claim to be easily extensible, expandable, have failovers/redundancy and whatnot...

[organofcorti]

I think you should let the pool owner know his pool will go from 4Ghps to 150Ghps before you post a config. It might not handle it.

but it's a....

A reliable and fault tolerant mining pool.

Hmmmm: 'fault tolerant' vs 'smashed by hoppers'?  He may need to take "Reliable" off the front page after his first block ends, all I'm sayin'.

If you're a member of this pool be nice and warn them now.


I hope he has json api so we don't regex him up the wazoo as well.

[organofcorti]

He'll find out the hard way anyways!

And hey, they claim to be easily extensible, expandable, have failovers/redundancy and whatnot...

Sukrim, you've seemed somewhat bitter lately ..... 

[hawks5999]

Looks like polmine just went live with a new website. I think regex is broken.

Code:

[polmine]
name: Polmine
mine_address: polmine.pl:8347 
api_address:https://polmine.pl/?action=statistics 
role:mine  
api_method:re
api_key: szystkich: &nbsp; </b> <br/>([ 0-9]+)<br/>
api_strip:' '

and for ryouiki:

Code:

    def polmine_sharesResponse(self, response):  #wszystkich: &nbsp; </b> <br/> 198 431 <br/> kopalni to<b> 192.29</b>
        output = re.search(r"wszystkich: &nbsp; </b> <br/>([ 0-9]+)<br/>", response)
        output_speed = re.search(r"kopalni to<b>([ 0-9\.]+)</b> Ghash", response)
        if output != None and output_speed != None:
            round_shares = int(output.group(1).replace(' ',''))
            speed = float(output_speed.group(1))
            server = self.servers['polmine']
            server['ghash'] = speed
            self.UpdateShares('polmine',round_shares)
        else:
            self.bitHopper.log_msg('regex fail : polmine')

They are on a pretty new block BTW

[Sukrim]

Nah, just a bit tired...

Still working a bit through that longpoll dataset I got, but so far it looks promising. If someone has some time at hand, I'd LOVE to have a bitHopper version that connects to _all_ pools in the list (ideally even to all subservers, like with btcguild uswest/uscentral) and prints out the exact time to the milisecond the LongPoll arrives.

This could then evolve to be our next-gen backend to verify pool stats in general and quite reliably hop btcg and deepbit.

By the way: deepbit seems to have some quite amazing infrastructure, looking at their longpoll reaction times...

[joulesbeef]

sent unitedminers admin a email on us hopping... hopefully they will like us.

[c00w]

sukrim: I can do that in the default bitHopper if you like.

Oh and I noticed polmine and already fixed it. And added slush. Tell me how it goes.

EDIT: Oh and I'm adding united miners. The frontpage gave me a lot of confidence in them. This should be funny.

[Sukrim]

@c00w: Yes please! Long poll timings will be the next step in hopping I hope (and will also shock a few "normal" miners about the bad performance of some pool backends!). A unix style timestamp with 3 places after the comma should be fine I guess...
Oh, and I'll most likely also need the time stamp of the most recent block on blockexplorer (as a comparison and to rule out blocks that were not found by any monitored pool) by checking http://blockexplorer.com/q/getblockcount and then requesting that number via http://blockexplorer.com/b/[blocknumbergoeshere]

The best thing to have then would be a delta between LongPoll_received and Block_found for each pool, sorted from lowest to highest.
Something like:

4.123 deepbit
4.512 uswest.btcguild
5.012 mtred

etc.

[hawks5999]

EDIT: Oh and I'm adding united miners. The frontpage gave me a lot of confidence in them. This should be funny.

Now that's just cruel... 

[c00w]

I'm considering disabling them. The website is already noticeably slower... And I haven't even mined on them yet.

[joulesbeef]

got an api disabled with them.. i guess that means it was lagging?

and they only have 3 people mining right now

mtred is kicking ass today another block down.. 58 minutes

[c00w]

The website was getting slow then it sped up... I didn't get a api_disable though.

[Moussekateer]

How does one enter the payout information in this new index.html?

[c00w]

1)Payout info?
Um you don't. Flower is adding it soon or I'll add it once I get worker stuff going and the LP stuff as well.

[flower1024]

How does one enter the payout information in this new index.html?

i will add this (together with role changes)
this evening

[organofcorti]

How does one enter the payout information in this new index.html?

i will add this (together with role changes)
this evening

for the time being you can just arrow your browser back, enter the payout info then hit refresh. worked fine as a hack.

[paraipan]

let's test the load balancing and redundancy

[anty]

shouldn't we use the valid share count opposed to the total share count?

Code:

[unitedminers]
name: unitedminers.com
mine_address: pool.unitedminers.com:8332
api_address: http://www.unitedminers.com/?action=statistics
api_method:re
api_key:Valid shares for current round:</th><td>([,\d]+)
api_strip:','
role:mine
#CHANGE THIS
#unitedminers.com
user: workername
pass: workerpassword