bitHopper: Python Pool Hopper Proxy

[gnaget]

Just because I always get a little tickle when I see 420 anywhere...

They got that far, they should aim for >10mil atleast

I actually feel really bad for them...  we should all jump in there and get them past this horrible hump.  It'll be good PR

hurrah for self quoting..  I just did actually, set them up as my backup.  It would be really nice for others to do so as well.  If enough of us jump in there it would be a huge help, and given they are considering changing their payout structure to keep us out, maybe it would discourage them from doing so

[hawks5999]

Just because I always get a little tickle when I see 420 anywhere...

They got that far, they should aim for >10mil atleast

I actually feel really bad for them...  we should all jump in there and get them past this horrible hump.  It'll be good PR

hurrah for self quoting..  I just did actually, set them up as my backup.  It would be really nice for others to do so as well.  If enough of us jump in there it would be a huge help, and given they are considering changing their payout structure to keep us out, maybe it would discourage them from doing so

get a commitment from pool op to not change payout system and THEN I'll consider a backup option, but presumptive good will often proves ineffective.

[bb]

Why was nofee disabled again?

Edit: and poolmunity?

(Where is that wiki! )

[muyoso]

2)Issues with the graph?
refresh.

Wow, I'm an idiot.

[joulesbeef]

Why was nofee disabled again?

they were lagging bad for some folks.. I'm mining there no problem and many others.. go for it.

Edit: and poolmunity?

they implemented a new payout scheme that doesnt work for us

(Where is that wiki! )

they appear to be working on things at the hoppers den

[EskimoBob]

Just because I always get a little tickle when I see 420 anywhere...

They got that far, they should aim for >10mil atleast

I actually feel really bad for them...  we should all jump in there and get them past this horrible hump.  It'll be good PR

hurrah for self quoting..  I just did actually, set them up as my backup.  It would be really nice for others to do so as well.  If enough of us jump in there it would be a huge help, and given they are considering changing their payout structure to keep us out, maybe it would discourage them from doing so

get a commitment from pool op to not change payout system and THEN I'll consider a backup option, but presumptive good will often proves ineffective.

This will be the best PR you guy can get Help the guy who helps you. This is what small pools are all about. 

 

[gnaget]

This will be the best PR you guy can get Help the guy who helps you. This is what small pools are all about. 

Exactly, a little altruism here and there never hurt anybody, and we can probably end their block from hell, which will make us look really good.  You want to turn the negative attitudes from miners, this is the way to do it.  I guarantee you they will all appreciate it.  I'm not saying stop mining at profitable pools, but as a backup here and there, help a brother out

[gnaget]

If you spend your life only worrying about squeezing every ounce of profit, you'll end up like this guy:


I assume everyone gets the reference

[Clipse]

If you spend your life only worrying about squeezing every ounce of profit, you'll end up like this guy:


I assume everyone gets the reference

With a face like that, youd be such a hit with the ladies

[hawks5999]

Exactly, a little altruism here and there never hurt anybody,

May I introduce you to Ayn Rand, she might disagree with you on that point.

I guarantee you they will all appreciate it.

I think you don't quite understand the word "guarantee". Many miners hate hoppers on 'principle' and getting a little help won't change that view. Go ahead ask the triplemining forum if they'd like some help from the hoppers. I would wager (but not guarantee) that you'll get a response similar to "We don't need their help!"

[backburn]

FYI Hoppers:

Confirmed/habitual hoppers are flagged as such and are QoS'd dead last, you're also last for LPs. Our API used to feed bad data to habitual hoppers but this has changed to simply delaying statistics for new blocks to keep the advantage in our loyal miners hands. We will stay proportional, but we will not encourage pool hopping. Go hop somewhere else.



I'm also seeing lots of unknown-work stales coming from users of your proxy. In fact 90% of your users "stales" are unknown-work. Proxy is hopping prematurely and submitting work from other pools? Not good.

[Clipse]

FYI Hoppers:

Confirmed/habitual hoppers are flagged as such and are QoS'd dead last, you're also last for LPs. Our API used to feed bad data to habitual hoppers but this has changed to simply delaying statistics for new blocks to keep the advantage in our loyal miners hands. We will stay proportional, but we will not encourage pool hopping. Go hop somewhere else.



I'm also seeing lots of unknown-work stales coming from users of your proxy. In fact 90% of your users "stales" are unknown-work. Proxy is hopping prematurely and submitting work from other pools? Not good.

Im a loyal hopper, does that count?

Anyhow I dont see how you could delay/alter any of the public non-user specific api feed without also delaying it for loyal users as you seem to mention here.

[anty]

Anyhow I dont see how you could delay/alter any of the public non-user specific api feed without also delaying it for loyal users as you seem to mention here.

Sure he can, just like he tampers with the connection of your worker he can delay the stats for the same IP.

[Clipse]

Anyhow I dont see how you could delay/alter any of the public non-user specific api feed without also delaying it for loyal users as you seem to mention here.

Sure he can, just like he tampers with the connection of your worker he can delay the stats for the same IP.

And you think I pull stats from the same ip that I connect from ? I have a completely seperate setup for where I pull server stats from mainly so it wont hammer it nor appear all botlike.

[muyoso]

FYI Hoppers:

Confirmed/habitual hoppers are flagged as such and are QoS'd dead last, you're also last for LPs. Our API used to feed bad data to habitual hoppers but this has changed to simply delaying statistics for new blocks to keep the advantage in our loyal miners hands. We will stay proportional, but we will not encourage pool hopping. Go hop somewhere else.



I'm also seeing lots of unknown-work stales coming from users of your proxy. In fact 90% of your users "stales" are unknown-work. Proxy is hopping prematurely and submitting work from other pools? Not good.

Well, looks like I will be cycling the router and getting a new IP and setting up a new account at bitclockers.    Unless someone has a better idea how to work around this ridiculousness.

[hawks5999]

Unless someone has a better idea how to work around this ridiculousness.

There's this option:

[muyoso]

Unless someone has a better idea how to work around this ridiculousness.

There's this option:

Nah, they were a very profitable pool until they started messing around.  Also, that would be like giving up.

And also, the fact that they are sabotaging their users as "revenge" for violating a non posted and non agreed to rule is frankly ridiculous. 

[anty]

Anyhow I dont see how you could delay/alter any of the public non-user specific api feed without also delaying it for loyal users as you seem to mention here.

Sure he can, just like he tampers with the connection of your worker he can delay the stats for the same IP.

And you think I pull stats from the same ip that I connect from ? I have a completely seperate setup for where I pull server stats from mainly so it wont hammer it nor appear all botlike.

Good for you. I didn't intend to attack you, you know? In your case he can't to anything to delay the stats only for you, but you already know that.

On an unrelated matter: I need a hopperden invite, too.

Oh and c00w could you comment on this please:

I'm also seeing lots of unknown-work stales coming from users of your proxy. In fact 90% of your users "stales" are unknown-work. Proxy is hopping prematurely and submitting work from other pools? Not good.

I thought this was solved a long time ago?

[backburn]

Im a loyal hopper, does that count?

Anyhow I dont see how you could delay/alter any of the public non-user specific api feed without also delaying it for loyal users as you seem to mention here.

It went from client header based detection to just delayed for everyone, just like Deepbit does.

This way it is an incentive to mine contiguously, as you will miss out on really short blocks and get less time to mine on moderately short blocks. This reduces the "hopping bonus" somewhat.

The improper configuration/coding of many hopping clients led to this decision. Prior to recent issues,  we did not care about hopping. But when a massive amount of clients are greedily bouncing back and forth between servers and dog-piling on pools when a block is found; something had to be done.  I cant idly sit back when hoppers flood in during a fresh block affecting or miners.  I guess you could say, you are a victim of your own success.

Don't forget, you're hurting the very people who make it possible for the pools good luck, profitability and the ability for you to hop in the first place.

[Clipse]

Good for you. I didn't intend to attack you, you know?

Yeh sorry I seem to have had a brain fart posting there in all defensive mode

For some reason I thought more users would have setup a seperate method of pulling API's but I guess I assumed the unassumable