bitHopper: Python Pool Hopper Proxy

[Clipse]

no issues with cows latest version for last couple of hours since release, its slicing and dicing between digbtc and polmine nicely. (using new default slice scheduler)

[1714219147]

1714219147

[1714219147]

1714219147

[1714219147]

1714219147

[Clipse]

Para, where you from?

Exact same timezone as me

EDIT: nm its under your profile.

[djex]

no issues with cows latest version for last couple of hours since release, its slicing and dicing between digbtc and polmine nicely. (using new default slice scheduler)

Same here, it's working really well at the moment.

[paraipan]

Para, where you from?

Exact same timezone as me

EDIT: nm its under your profile.

almost 6 in the morning here keeping an eye on stuff and on hopper too

[simonk83]

something still fails... mine just sticked with slush for good, 140% atm , I just l left it to see how high could go, better mine with them until the block is found methinks

Me too.  Disabled them for now

[paraipan]

In my version?

not quite the last one, just realized you were few commits ahead, this one is ea45f10 from yesterday (my timezone), had it running the whole night without issues, until this

edit: updated and have it running smooth again, it jumped from slush in a blink

[ed64]

It looks like LP is returning a url which is "" based on that error message.

I see something similar with digbtc recently, went away though. I set a penalty of 2 or so it slices less frequently... I penalize smaller pools since their stability isn't that great.

[joulesbeef]

I know it is kinda packed all ready but it looks like there might be a tiny bit of room.. I'd like the abiliity to leave a tiny note at the end next to a pool. Things like the actual share count of the block i am on, since i have cleared the db now and then in various testing weekly eff. or just notes on connection issues, rejects.. like i keep forgetting why i have btcpool24 on info.. or the last time i made any coin from that pool so i can watch it better.  remind myself to watch bitcoinlc or clockers. maybe 20 chars if you could fit that many without horizontal scrolls or font shrinkage.

[joulesbeef]

from btcpool24

Sure you will get the 1.95BTC extra if you find the block.

calc is exactly (myshares/totalshares)*50

he is not changing prop.. so mine him if you got him off..

they are small and some connection issues now and then.. only one block found so far

they are also my highest reject rate though.. 4% with them.. .. my other highest is 0.8% most are at 0%
so be wary or penalize them if you have the ability

[macboy80]

Hello all. First, I'd like to apologize if my stats page "gave you a headache." I had hoped people had a chance to check it out. That being said, I'm not one to give up. I'm going to try to do a few of these with the help of kuler and post them over in paraipanakos' poll thread. I'm thinking, with enough of these, I could put a folder in where you could choose your skin and then we would have a ghetto skin system.
The first one is over here:

https://bitcointalk.org/index.php?topic=34369.msg430170#msg430170

I would appreciate feedback, good or bad, to try to avoid another "situation."
Also, I could really use some help making the text bold as well as possibly applying the getColor function to the linecolor of the graph.

[gnaget]

I'm seeing some very bad behavior right now:

MtRed = 7%
Bitcoins.lc = 43%

I start bitHopper up with bitcoins.lc on info, and when I mark it as mine, bitHopper leaves mtred to mine at bitcoins.lc.  When I mark bitcoins.lc back as info, it continues to mine there until I restart bitHopper. 

I'm on the latest version

[Litt]

so is anyone else noticing poolmunity json acting a little funny?

[joulesbeef]

pretty sure poolmunity changed their payout scheme and you shouldnt be hopping them

[c00w]

@gnaget
Should be fixed in latest commit.
It only reslices every 30 seconds and didn't reslice earlier if the pool had the wrong role.

[gnaget]

I see, pulled latest again.  Slicing seems to have some problems though.  When you move a pool under 43.5% from info to mine, it will start mining on it for about a minute before switching over to a better pool.  For example in my case, I switched over BTCPool24 which was at 40%, and it mined it for a minute even though mtred was at 15%

[gnaget]

It's not just when switching roles, it just switched back to BTCPool24 on me

[joulesbeef]

when starting using bitHopper.py --scheduler SliceScheduler

it says it cant find sliceschedular and reverts to default. am i using the right start up?

[djex]

Also, I could really use some help making the text bold as well as possibly applying the getColor function to the linecolor of the graph.

<b>these tags will bold html</b>

The line color looks to be set on line 300 of index.html.

when starting using bitHopper.py --scheduler SliceScheduler

it says it cant find sliceschedular and reverts to default. am i using the right start up?

The default is SliceScheduler now

[gnaget]

Ok, so BTCPool24 has a total of 18 GH and is at 41%, and MtRed has 400 GH and is at 23%.  Why would slicer choose BTCPool24?

[Clipse]

Ok, so BTCPool24 has a total of 18 GH and is at 41%, and MtRed has 400 GH and is at 23%.  Why would slicer choose BTCPool24?

Slicers main flaw atm is that it doesnt recognize poolhashrate, that is something dynamicpenalty will introduce once it gets added I assume.