bitHopper: Python Pool Hopper Proxy

[Clipse]

Im not so concerned bout the odd issues with certain fixes, atleast it speeds up development eitherway.

That said, how does the timeline look for you c00w to get a splice of slice scheduler combined with dynamicpenalty (using poolspeed/shares/duration) included in main bithopper version ?

[hawks5999]

https://bitcointalk.org/index.php?topic=34226.msg431969#msg431969

Props to c00w given in this message by the finder of the first block on digbtc...

[c00w]

Well penalty is already combined into the slice scheduler. However because it is based off of time not sharecount it won't effect much. Honestly it looks like AltSliceScheduler will become the default once all its issues are fixed and the current default will become SimpleSliceScheduler.

[paraipan]

https://bitcointalk.org/index.php?topic=34226.msg431969#msg431969

Props to c00w given in this message by the finder of the first block on digbtc...

I wish he got a lucky find on another pool right now for being that onest

[Clipse]

btcpool24 is acting up again, json stats reset as if block were found yet the main stats still count on from previous shares.

I dont know what to believe on this site anymore, just to get get some sort of payout before i leave since its starting to feel extremely dodgy to me.

[MaGNeT]

Did BTCPool24 just find their second block? Or are they faking stats?

edit: looks like faking... They are "disable" now...
edit: stats are "normal" again... Maybe "enable" them later...

[Clipse]

Did BTCPool24 just find their second block? Or are they faking stats?

This is the 2nd stats reset after the first block were found(paid out), Im getting tired of these screwups but ive committed a ton of shares and first expect some payout before I fukoff.

[ewibit]

btcpool24 is acting up again, json stats reset as if block were found yet the main stats still count on from previous shares.

it has been now a few times that we see 3,23%  
look at his stats page how it jumps up and down  

edit:
digbtc.net is always going to api_disable...

[Clipse]

Now the json is "fixed" again, for how long anyones guess.

[jkminkov]

apply medicine

api_address: http://www.btcpool24.com/stat.php
api_method: re
api_key:<br/>Round Shares:([ 0-9]+)<br/><br/></span>
api_strip: ' '

[MaGNeT]

apply medicine

api_address: http://www.btcpool24.com/stat.php
api_method: re
api_key:<br/>Round Shares:([ 0-9]+)<br/><br/></span>
api_strip: ' '

Seems to work
Until they "fix" json this should do it...

[Clipse]

apply medicine

api_address: http://www.btcpool24.com/stat.php
api_method: re
api_key:<br/>Round Shares:([ 0-9]+)<br/><br/></span>
api_strip: ' '

My concern isnt where to get the stats but when to know that the stats are actually accurate.

[joulesbeef]

I dont know anything at all about setting up  a pool, but this is the first newb pool that said it found a block and then came back and said that was a glitch and now apparently it happened again? or did they ind a block.

yeah some of these new pools you got to be wary of. Bitcoins are money after all. It isnt out of the rhelm of possibilities for someone to scam peoples megahashes and run off with the coin.  Not saying that is what they are doing but always got to be wary of the new pools

[paraipan]

apply medicine

api_address: http://www.btcpool24.com/stat.php
api_method: re
api_key:<br/>Round Shares:([ 0-9]+)<br/><br/></span>
api_strip: ' '

My concern isnt where to get the stats but when to know that the stats are actually accurate.

I would like to know that too, until then I just watch stats, graphs and my instinct to tell if someone messing with that info

[Clipse]

json reset again lol

fucking lovely, ill just have to use the regex stats for now assuming those are correct.

[MaGNeT]

apply medicine

api_address: http://www.btcpool24.com/stat.php
api_method: re
api_key:<br/>Round Shares:([ 0-9]+)<br/><br/></span>
api_strip: ' '

My concern isnt where to get the stats but when to know that the stats are actually accurate.

I would like to know that too, until then I just watch stats, graphs and my instinct to tell if someone messing with that info

This is how it looks now... In doubt, as you can see

[btcpool24]
name: btcpool24
mine_address: min.btcpool24.com:8338
#api_address: http://www.btcpool24.com/json_stats.php
#api_method: json
#api_key: shares_this_round
api_address: http://www.btcpool24.com/stat.php
api_method: re
api_key:<br/>Round Shares:([ 0-9]+)<br/><br/></span>
api_strip: ' '
url: http://www.btcpool24.com/

[Litt]

I'm holding back on 24 and dig for a bit until they have proved themselves more. I've given them some shares for the current round as a test and that would be that. I will try all the new pools once, but after that they need to be proven worthy as Clipse is saying imo. I had similar issue with poolmunity's json, though I never sent any shares in and won't until they've paid out a couple blocks. Someone also said poolmunity wasn't good for another reason, but wasn't told what. Maybe someone can shed some light?

Trying to maximize the profit efficiency by hopping more pools is great and all, but for me it's more about the philosophy that I'm hopping and not being hopped on that matters most rather than risking too much at these new pools. I say Bithasher having 8 blocks under it's belt is a sweetspot personally to be invited for a piece of my pie slice.

[c00w]

I fixed some DB problems and LP looks fixed. So I tagged v0.1.1. If you're running a version which is moderately newish this is probably what you want to use.

[paraipan]

json reset again lol

fucking lovely, ill just have to use the regex stats for now assuming those are correct.

small request to you clipse: can you put a little bit more attention when it resets to see if it's a 0 or a sub 100 value ? (a predictable value), can be circumvented ignoring a reset when in that range

edit: I actually don't  monitor this pool anymore, but when did, I've seen that strange resets too

[simonk83]

Ok, here's the test to see if Slush is fixed

EDIT:  All good