bitHopper: Python Pool Hopper Proxy

[organofcorti]

Oh, another little something:
The mine_slush pool does not draw a pretty graph...

mine_slush is a kind of backup, and graphs for backups aren't necessary. I suppose it could be turned on for all backups though, then you'd get the mine_slush graph too.

[flower1024]

Oh, another little something:
The mine_slush pool does not draw a pretty graph...

as i don't use slush i don't know why.

could you post a picture?

(I marked the area in red where the graph should be)

i'll fix it - its very easy.
i made a very simple mistake by only rendering the graph when role="mine". should be role.startsWith(mine) instead.
when i did this page i did not know about mine_slush or mine_nmc and such.

[ewibit]

try restarting bitHopper or refreshing the page

Thanks, but this does not resolve
I have had this a few times ago and on the homepage of poolmunity they are on the 2. Block since 5 days and in the graphs sometimes is showing that a new round is beginning...

[flower1024]

try restarting bitHopper or refreshing the page

Thanks, but this does not resolve
I have had this a few times ago and on the homepage of poolmunity they are on the 2. Block since 5 days and in the graphs sometimes is showing that a new round is beginning...

there is no nice way to fix this issue on client side.
i guess its the pool-api which returns zero round_shares sometimes (maybe this is even made for us hoppers).

the only way i could imagine is to sanitize data. means: if i see there were zero round shares supplied and afterwards some very high i could just change the zeros to the start value.

but this doesn't work with ozcoin invalids handling (when ozcoin gets an invalid it just make the last round longer - means no "invalid" or "unpaid" shares - there you would see the exact same behavior)

but i don't like that idea: a graph has to show what it got from the pool. nothing else.

see it as a hint that this pools tries to cheat you (which is the reason i made this graph in the first place)

i'll see how far i get this evening
if i have time left i'll implement jqPlot graphs (similar to eligius one) where you could change time-range displayed and zoom in and out. but that depends on my time.

[ewibit]

if i have time left i'll implement jqPlot graphs (similar to eligius one) where you could change time-range displayed and zoom in and out. but that depends on my time.

+1 

[organofcorti]

Has anyone tried to use Tor to get around bitclockers IP/user bans? I wouldn't care and never made many coins from them, but when someone throws down the gauntlet I don't like to bend over and just take it.

[Keninishna]

Has anyone tried to use Tor to get around bitclockers IP/user bans? I wouldn't care and never made many coins from them, but when someone throws down the gauntlet I don't like to bend over and just take it.

It seems I'm getting decent efficiency with them despite the lag at 10% stales.

[licutis]

.

[flower1024]

wouldn't it be enough to just get the stats through tor and send the getworks directly?

[licutis]

.

[organofcorti]

Has anyone tried to use Tor to get around bitclockers IP/user bans? I wouldn't care and never made many coins from them, but when someone throws down the gauntlet I don't like to bend over and just take it.

It seems I'm getting decent efficiency with them despite the lag at 10% stales.

Yeah, but what's your hashrate down to? Mine was at around half what it should be, and the the gpu would go idle every 10 - 20 secs or so - not good.

[organofcorti]

wouldn't it be enough to just get the stats through tor and send the getworks directly?

not with the ip/worker bans - it's not the stats, it's the enforced idle time from refusing getwork requests.

[flower1024]

wouldn't it be enough to just get the stats through tor and send the getworks directly?

i would really like to be able to separate the path for getworks and stats with a socks proxy, then i can send it out tor or my neighbors cable modem (with permission of course), etc.

should be easy...

just setup an apache with php (or something else) and make a redirect script (sth like this http://demo.loopip.com/integration_demo/search/php_reverse_proxy) which takes the url to retrieve (eg. http://localhost/statsproxy.php?url=#real stats page#

then change the pool.cfg to use your redirection.

[flower1024]

wouldn't it be enough to just get the stats through tor and send the getworks directly?

not with the ip/worker bans - it's not the stats, it's the enforced idle time from refusing getwork requests.

that's a different problem!
to solve this we need worker management in bithopper (both: client and pool side)

then we don't have that issue any more

[organofcorti]

wouldn't it be enough to just get the stats through tor and send the getworks directly?

not with the ip/worker bans - it's not the stats, it's the enforced idle time from refusing getwork requests.

that's a different problem!
to solve this we need worker management in bithopper (both: client and pool side)

then we don't have that issue any more

The timeouts are caused by the pool on purpose though because we're identified by IP and user/workername as offending hoppers (see burnbacks post a few pages back). How will client side worker management get around this?

[flower1024]

The timeouts are caused by the pool on purpose though because we're identified by IP and user/workername as offending hoppers (see burnbacks post a few pages back). How will client side worker management get around this?

ok, client side worker are not really needed to solve this as bithopper could just split getwork requests through its workers; but i am very sure that missing them is the reason we got currupted (NOT stale) shares)

but i think its easier to implement - as you "always" know worker 1 goes to pool worker 1 and so on.

[Xer]

flower1024, could you box in the outer edges of the graph? it would look better then leaving a space above and under them like you do now. (just extend it to the Dark Blue lines separating the different pools)

[flower1024]

flower1024, could you box in the outer edges of the graph? it would look better then leaving a space above and under them like you do now. (just extend it to the Dark Blue lines separating the different pools)

ok

[licutis]

.

[bb]

Sorry, proportional is the only fair mining method. A share is a share, no matter when it is submitted.

Why do you pay them differently then?

Anyways, at least you give a bit of challenge...

By the way, real pool DDoSing is done differently, but I won't give any hints here, because THAT would really hurt your pool I guess.

Paid differently? Not sure i follow, every share is worth the same. The other payout methods pay people differently....

Obviously its not a ddos, but it fits the definition spare the ill intent. Hence the quotes.

As a pool operator you should really have a better understanding of the probabilities involved in this.

In proportional payout structures, every share in one round is worth the same. Shares from different rounds are not. This is the very aspect that makes hopping work.