bitHopper: Python Pool Hopper Proxy

[paraipan]

thanks 

[paraipan]

"We don't need grasshoppers... We need miners..."

MaGneT, when are you going to admit that we really do need grasshoppers?

 

I think he's referring to your signature MaGNeT   

[bitcoindaddy]

Will someone please explain the new scheduler to me in layman's terms? It makes no sense to me that I should spend shares on a pool that has a higher "percentage" than a lower percentage pool. I understand that people don't want to get trapped on a small GH/s pool for days at a time- if that's the case, remove the pool.

I switched back to --scheduler OldDefaultScheduler (and am being punished for it with the old color scheme) because I'm not convinced the new scheduler has a positive effect.

Right now I'm going full tilt on bithasher because it has the lowest percentage. Why should I do any different? Convince me (with math, not your gut feelings).

[Clipse]

Ive noticed something strange, my pools report constantly higher accepted shares than webui of bithopper ?

example: bithashers atm reporting 800 submitted/accepted shares in bithopper webui but the website reports 1250 accepted shares.

[ewibit]

5) ...

6) if a pool is on info and they have found a block it can be very nice if the color changes or it switches on first row etc.
TIA 

[paraipan]

Ive noticed something strange, my pools report constantly higher accepted shares than webui of bithopper ?

example: bithashers atm reporting 800 submitted/accepted shares in bithopper webui but the website reports 1250 accepted shares.

you almost surely deleted bH database... bithashers it's the total shares submitted from signup or round ones ?

[ewibit]

- It remains on pools until slice time runs out, no matter if a pool is >43.5% or in case of mine_slush >~11%, it will continue until timeslice is finish.

is mine_slush active if I start with --scheduler SliceScheduler?
because bitcoin.cz is @~4% and it stays at the pool with ~30%

[djex]

How can I make bitHopper mine longer on a certain pool with slicing? Right now there all evenly sliced but I want to mine longer on faster pools so I get more shares in.

[Clipse]

Ive noticed something strange, my pools report constantly higher accepted shares than webui of bithopper ?

example: bithashers atm reporting 800 submitted/accepted shares in bithopper webui but the website reports 1250 accepted shares.

you almost surely deleted bH database... bithashers it's the total shares submitted from signup or round ones ?

Nope didnt delete my stats.db, however I just realised the flowers poclbm mod doesnt report submitted shares to the webui, doh

[ewibit]

How can I make bitHopper mine longer on a certain pool with slicing? Right now there all evenly sliced but I want to mine longer on faster pools so I get more shares in.

perhaps it makes sense to make a priority list (e.g. 1 - 5) for priorities of pools?!

[user7516]

Just updated to v0.1-11-g689817b and get this error:

Code:

[17:43:03] received lp from: digbtc
Unhandled Error
Traceback (most recent call last):
  File "C:\Python27\Lib\c00w-bitHopper\bitHopper.py", line 298, in <module>
    main()
  File "C:\Python27\Lib\c00w-bitHopper\bitHopper.py", line 294, in main
    reactor.run()
  File "C:\Python27\lib\site-packages\twisted\internet\base.py", line 1162, in run
    self.mainLoop()
  File "C:\Python27\lib\site-packages\twisted\internet\base.py", line 1171, in mainLoop
    self.runUntilCurrent()
--- <exception caught here> ---
  File "C:\Python27\lib\site-packages\twisted\internet\base.py", line 793, in runUntilCurrent
    call.func(*call.args, **call.kw)
exceptions.TypeError: pull_lp() takes exactly 3 arguments (2 given)
[17:43:05] RPC request [56528000] submitted to DigBTC.net

I have to re-install twisted?
This error I had never received before. I use AOCLBF 1.77 with phatk 2.0 and bitHopper with --scheduler AltSliceScheduler.
And what about bitclockers? I change my ip, register new accaunt, but still have a lag issue with it.

[gnaget]

Can someone post the info for digbit?  I can't even find their URL

[Clipse]

How can I make bitHopper mine longer on a certain pool with slicing? Right now there all evenly sliced but I want to mine longer on faster pools so I get more shares in.

Right now it doesnt know the poolspeed afaik, we need dynamicpenalty adjustment that takes poolspeed/duration into consideration for this kind of adjustment with slicedscheduler.

[bitcoindaddy]

Can someone post the info for digbit?  I can't even find their URL

[digbtc]
name: DigBTC.net
mine_address: digbtc.net:8332
api_address:http://digbtc.net/
api_method:re
api_key:Round Shares: <b>([ 0-9]+)</b>
url: http://www.digbtc.net/main.php

[paraipan]

Can someone post the info for digbit?  I can't even find their URL

don't have it either, I just thought he was referring to DigBTC.net one of the last pools added

edit: name fix update on git

[joulesbeef]

Estimated Reward this Round: -0.47 BTC (has started @ -0.50 BTC)
does this "-" mean minus and why?

there coder sucks... mine with caution, no one has gotten paid from there yet.

I understand that people don't want to get trapped on a small GH/s pool for days at a time- if that's the case, remove the pool.

you can always use a different hopper. or an older version

With slicing we  found the block for the 2gighash pool digbit, and i got 1/3 a coin for about 20 minutes of work at 300mhz
No one would have mined there without slicing... too small..do you need me to do the math?

it lowers the variance and more pools is better,

I do agree eventually we need slicing to take ghashes into account

[paraipan]

Just updated to v0.1-11-g689817b and get this error:

Code:

[17:43:03] received lp from: digbtc
Unhandled Error
Traceback (most recent call last):
  File "C:\Python27\Lib\c00w-bitHopper\bitHopper.py", line 298, in <module>
    main()
  File "C:\Python27\Lib\c00w-bitHopper\bitHopper.py", line 294, in main
    reactor.run()
  File "C:\Python27\lib\site-packages\twisted\internet\base.py", line 1162, in run
    self.mainLoop()
  File "C:\Python27\lib\site-packages\twisted\internet\base.py", line 1171, in mainLoop
    self.runUntilCurrent()
--- <exception caught here> ---
  File "C:\Python27\lib\site-packages\twisted\internet\base.py", line 793, in runUntilCurrent
    call.func(*call.args, **call.kw)
exceptions.TypeError: pull_lp() takes exactly 3 arguments (2 given)
[17:43:05] RPC request [56528000] submitted to DigBTC.net

I have to re-install twisted?
This error I had never received before. I use AOCLBF 1.77 with phatk 2.0 and bitHopper with --scheduler AltSliceScheduler.
And what about bitclockers? I change my ip, register new accaunt, but still have a lag issue with it.

give it a try without "--scheduler AltSliceScheduler"
edit: the "selective" lag problems with bitclockers could appear from more factors than just low QOS account or IP ban, could be geographic location too

[gnaget]

Can someone post the info for digbit?  I can't even find their URL

[digbtc]
name: DigBTC.net
mine_address: digbtc.net:8332
api_address:http://digbtc.net/
api_method:re
api_key:Round Shares: <b>([ 0-9]+)</b>
url: http://www.digbtc.net/main.php

Thank you sir

[EskimoBob]

Hi, before I do my next git pull, I like to see what has changed. I did read the git --help but for some reason, I fail to find out any specific changes (especially in pools.cfg and user.cfg.default). I use c00w master branch.

Thank you

[Clipse]

Hi, before I do my next git pull, I like to see what has changed. I did read the git --help but for some reason, I fail to find out any specific changes (especially in pools.cfg and user.cfg.default). I use c00w master branch.

Thank you

Read up on latest commits on the github page, much easier to read there than using the commit info from the client.