bitHopper: Python Pool Hopper Proxy

[paraipan]

A normal day for a bitcoin miner...

[1713562271]

1713562271

[djex]

So how is c00w's slicing working? Is it stable enough to switch to now?

[c00w]

@murfshake

Is it swapping to another backup from deepbit?

[Litt]

Found a few pools that seems hoppable not in the list.

Swepool.net looks to be a proportional again now as of recently and operating at around 5Gh~. And Digbtc.net is another pool that is a small proportional pool that can be added I think.

Could someone pls add these two pools to the pool.cfg/user.cfg list?

[paraipan]

Found a few pools that seems hoppable not in the list.

Swepool.net looks to be a proportional again now as of recently and operating at around 5Gh~. And Digbtc.net is another pool that is a small proportional pool that can be added I think.

Could someone pls add these two pools to the pool.cfg/user.cfg list?

thanks, digbtc is added, Swepoo would surely win the prize for the most simple and clean pool site ever, cant find nothing in there (shares for ex.)

edit: oops, now I see the shares, but not the actual round ones

[murfshake]

@murfshake

Is it swapping to another backup from deepbit?

To get it working in the new version I had to put

[deepbit]
name:deepbit
mine_address:pit.deepbit.net:8332

in pool.cfg

then also make it "backup_latehop" in the user.cfg

*Nevermind, it still only does the first 2 shares on deepbit (my only backup pool) then goes right to the lowest "mine" pool no matter how bad of a % it is at.

I can't get it to stay on my backup of deepbit no matter what I do.  Going back to the old version.

[flower1024]

i now have a working configuration for bitclockers (but it requires two different ip's)

first-ip: start a bithopper instance
second-ip: start a bithopper instance per worker on a different port (eg you have three workers just put them at ports 8000,8001,8002)
-> change pools.cfg to get stats from http://<firstip>/data
format is always json, key is servers.#poolname#.shares
(poolname does not refer to its name, it the key inside [key] in pools.cfg)

-> change users.cfg to get a unique workername for bitclockers at each port
(as this file is always read in through bithopper start, you can write a script which starts the instances all from the same directory, just switches the users.cfg)

-> you could change the stat update interval in bitHopper.py (ONLY on your worker-hopper, not on stats hopper)

now connect your worker - each to a different bithopper port

now you can mine at bitclockers again.

^^ with this your stats will be a little messed up;

[Sukrim]

Looks like Ozco.in now provides a user API key, useful?

User not, but https://ozco.in/api.php should be nice!

edit: It's already in the current version... so just upgrade.

[Litt]

Found a few pools that seems hoppable not in the list.

Swepool.net looks to be a proportional again now as of recently and operating at around 5Gh~. And Digbtc.net is another pool that is a small proportional pool that can be added I think.

Could someone pls add these two pools to the pool.cfg/user.cfg list?

thanks, digbtc is added, Swepoo would surely win the prize for the most simple and clean pool site ever, cant find nothing in there (shares for ex.)

edit: oops, now I see the shares, but not the actual round ones

Hey Para you can see the shares once you create the account and you are in the stats section while logged in.

edit: current round share that is.

[djex]

i now have a working configuration for bitclockers (but it requires two different ip's)

first-ip: start a bithopper instance
second-ip: start a bithopper instance per worker on a different port (eg you have three workers just put them at ports 8000,8001,8002)
-> change pools.cfg to get stats from http://<firstip>/data
format is always json, key is servers.#poolname#.shares
(poolname does not refer to its name, it the key inside [key] in pools.cfg)

-> change users.cfg to get a unique workername for bitclockers at each port
(as this file is always read in through bithopper start, you can write a script which starts the instances all from the same directory, just switches the users.cfg)

-> you could change the stat update interval in bitHopper.py (ONLY on your worker-hopper, not on stats hopper)

now connect your worker - each to a different bithopper port

now you can mine at bitclockers again.

^^ with this your stats will be a little messed up;

Hardly worth all that for one pool 

[paraipan]

Feature request for stats page:

1) Please add a thousand separators to stat page (Shares, User shares etc).
2) Please add a button to force mining in selected  pool and hop away only when another pool starts a new block    
3) check pool once more, before it gets a status "api_disable"
4) remove  "api_disable"  after N seconds and return the pool back to its previous status (mine etc)
5) move move backup pool to the end of the mining pools list and before disabled pools

I have something for this list. For the miner stats at the bottom left of the page could you make it so the name is red or green according to its online status based off when they submitted shares last. For example:

After 10 min if shares have not changed for x miner then color name red for offline else color green for online.

I tried to code something like this in javascript but it's probably better off being handled with the back end rather than the stats page.

Done, issue posted on git

@litt, nice to know, thanks

[flower1024]

Hardly worth all that for one pool 

yep, its just a matter of principle

[bitcoindaddy]

Found a few pools that seems hoppable not in the list.

Swepool.net looks to be a proportional again now as of recently and operating at around 5Gh~. And Digbtc.net is another pool that is a small proportional pool that can be added I think.

Could someone pls add these two pools to the pool.cfg/user.cfg list?

thanks, digbtc is added, Swepoo would surely win the prize for the most simple and clean pool site ever, cant find nothing in there (shares for ex.)

edit: oops, now I see the shares, but not the actual round ones

Hey Para you can see the shares once you create the account and you are in the stats section while logged in.

edit: current round share that is.

This is a problem- swepool only shows you the share count if you're logged in - it won't work for bitHopper unless you're logged in on the same machine.

[muyoso]

I am wondering how cherrypicker has bitclockers working.  According to some its working flawlessly.

I wonder if its that cherrypicker is using poclbm to mine.  Are we sending getworks faster than poclbm or doing anything else that would differentiate us from normal miners?  If so, is there a way we could scale it back to blend in with the crowd?

[paraipan]

made another one...

Popular mining hardware since 2011...

[Clipse]

I am wondering how cherrypicker has bitclockers working.  According to some its working flawlessly.

I wonder if its that cherrypicker is using poclbm to mine.  Are we sending getworks faster than poclbm or doing anything else that would differentiate us from normal miners?  If so, is there a way we could scale it back to blend in with the crowd?

I think as soon as we can get bithopper to act directly with miners rather than feeding work back and forth as a proxy, any and all issues like this would be resolved. That said, I have the exact same issues with bitclockers using bithopper and not using it so I still think its bitclockers that hosts a shit server rather than them screwing with bithopper users.

[c00w]

I have bitclockers working fine for myself.

[flower1024]

I have bitclockers working fine for myself.

how much mhash are you pushing?

with everything above 300mh i get way more connection errors.
with different worker they all are doing fine (still some connection errors, but not that much)

[ewibit]

Found a few pools that seems hoppable not in the list.
Could someone pls add these two pools to the pool.cfg/user.cfg list?

btcmp.com

[muyoso]

I have bitclockers working fine for myself.

Did you create a new account, get a new IP or something like that?  Did you used to have problems and then fix it in a newer version of bithopper?  Are you running one instance of bithopper and having multiple miners connect to it from various rigs?