bitHopper: Python Pool Hopper Proxy

[organofcorti]

I'm still not sure how you would tell - if stats are delayed by an hour, then you'd still get a full amount of shares because bitHopper would still hop off at the point that it thought was correct. It sounds like what you're talking about is more like delaying an update to let everyone know a block has started?

Either way, is the website total shares the same as or different to the json total shares?

What happens is this.  Say a round is six hours and 30 minutes long.  Well the website will report the round as 7 hours long, and then suddenly report that round as six hours and 30 minutes long and report the new round as starting 30 minutes ago.  So then the hopper switches usually because its only like 170k shares but you have essentially missed out on the most valuable mining that there is.  You still make money over Ars on short to normal length rounds, but on long rounds your shares are essentially worthless.

ok, but then wouldn't the total shares on the website not increase?

[macboy80]

Just wanted to share a few things with you...

1) c00w: You are awesome. Thank you for spending the night trying to figure out my issue that I should have found.
    BitQuarter for your hard work.
2) Can someone figure what pool.cfg works for bitclockers? That was the above issue that completely killed stats when set to mine.
3) With regards to Bitcoins.lc : Is c00w fork using the same method ryouiki was/is using? That seemed to work well for me. Of course, it may have had the same stats delayed problem.

I had some rookie errors while running bitHopper on Windows 7 x64. Things that helped me are:

1) I wasn't sure how to run bH, so I ran from the IDLE GUI. When I exited the GUI, it force closed the program leaving the database locked. Several things worked in order from worst to first: Restart computer; Kill python task in Task Manager; Press "Ctrl+Alt+C" while focused on the GUI console.
2) The best option which escaped me until tonight was to create a shortcut of "python.exe" , and edit it to look like this:
"C:\Python27\python.exe C:\bitHopper\bithopper.py"
This makes it easy to double click to create an instance of bH and click X to close cleanly.

Thanks to all who write code, contribute config, beat up on trolls, and pool ops who amicably discuss pros and cons of pool hopping. You all have made this a hobby.

[hawks5999]

I had some rookie errors while running bitHopper on Windows 7 x64. Things that helped me are:

I had a non-rookie last Friday. Downloaded an updated Ryouiki build, removed .default from the password file. Compared to my existing password file. Check.
Then forgot to copy my existing password file into the folder. 4 hours and lightning fast round on mtred later I discovered my error.

Consider it a tip Ryouiki.

[rampone]

Is there something special to get mtred working? I keep getting error decoding json, and it shows up as red on the stats page, and won't switch.

Thanks!

Have a older ryouki fork, but mtred should work outof da box. they didnt change anything.

[c00w]

rampone:
Red means it lagged out. Are you sure you didn't accientally change the api_address?

[bigbeerjr]

rampone:
Red means it lagged out. Are you sure you didn't accientally change the api_address?

I didn't change the address, and of course now it's no longer red... I'll have to watch it again the next time they hit a block.

[OCedHrt]

are you sure you switched to the api method suggested by mrsam?
for me its working.

and he already announced HERE that he will fake stats when accessed through the https site (which i am fine with and which i can understand)

Well, it's not about fake stats through https. The stats are correct in the  browser but incorrect in bitHopper. I assume they are filtering by user agent - changing the user agent got the correct stats.

I go out for a day a triplemining is faking stats to BitHopper. I'm sure someone noticed, but thought I'd give a warning before catching up on the reading.

Finally had to apply the commit mentioned earlier to fake the user agent: https://github.com/ryouiki/bitHopper/commit/e8fa81053efa238c062d03603c44eeecf4a87523

There isn't a ryouiki release with the correct api pull for triple.

It just parses the website. Seeing as there is a json for the round shares, I just updated my local copy to use that.

[macboy80]

Can we do a re-assessment of bitclockers? I seem to be getting good results with them, but some are saying there is a problem. Can anybody enlighten me?

P.S. c00w has completely fixed the stats issue regarding enabling bitclockers.

[organofcorti]

Can we do a re-assessment of bitclockers? I seem to be getting good results with them, but some are saying there is a problem. Can anybody enlighten me?

P.S. c00w has completely fixed the stats issue regarding enabling bitclockers.

for me, bitclockers ~ 140% eff. since July 12th. I don't think I ever disabled it.

[hawks5999]

I'm a fan of bitclockers in general. They were my first pool <sigh>. Lots of good people there. V2-V3 and Backburn are both solid and they have built a very strong backend and nice stat representation on the front end (maybe even too much). But I would support them and should they ever go PPS make them one of my primary backups.

[organofcorti]

What is the general purpose of custom cutoffs? (Wasn't there someone showing what the ideal cutoff was?)

Search this thread for username 'streblo'.

[flower1024]

Bithopper is a Bitcoin Pool Hopper which supports around 13 pools at last count.
Its still in beta but works pretty well.

https://github.com/c00w/bitHopper

Instructions:

1) Download the project

<-------IMPORTANT---------->
2) Move pool.cfg.default to pool.cfg and modify it to use your accounts instead of mine for mining.
<-------IMPORTANT---------->

3) Install twisted python. http://twistedmatrix.com/trac/
4) Then run bitHopper.py
5) Direct your miner to localhost:8337
6) Tell me if anything breaks at https://github.com/c00w/bitHopper/issues
6a) Or use the forums.
7) Look at stats and control pool at localhost:8337/stats

Current Features:
* Pool Hopping
* LP (Client and Server)
* Low Reject Rate
* Stats with a website and control from said stats.
* Automatically adjusts API polling times.
* Pool Config File, Supposed to be easy to use

Planned features:
Individual Miner Stats. Based on username/IP.
Optional bitcoind integration for payout tracking.
Password protect the website
Dropdown lists for role selects
Flower's slicing...

Pool.
Deepbit.
Re-license.

Think this is cool? Want me to hurry up and add more features?:
1HEmzeuVEKxBQkEenysV1yM8oAddQ4o2TX

nice work.
could you also include my pool-round share graph from github? its very useful to detect pool fraud.
if you've done that, i'll switch to your version

[flower1024]

• Merged flower's time slicing mod
• Added startup options to enable slicing (off by default) and set slicing size
• Also showed slice (seconds) left in web stats as well
• Refactored backup server into it's own function
• Added additional parameters to log_msg and log_dbg to prefix log messages

Available in my tree for now: https://github.com/echiu64/bitHopper

Feel free to pull back into your respective trees.

Only tested it briefly... more changes to come.

Tested it for a few hours now, made a few more changes pushed to git (penalty wasn't being factored in the initial commit). Looks like it works. Threw in btcg for fun, time slicing between 3 pools now...

nice
could you also add my pool-stats graph? i use it for pool-fraud-detection - it really makes it a lot easier

i mean the blue line to the right (which is round shares per pool)

[Clipse]

Is anyone else having issues with nofeemining ?

I cant for the life of me keep a stable connection to it, it keeps lagging out after only a few submitted shares. My latency to the server is within check , tested it on another setup from a friend in country closer to the server <80ms and having same issues.

[jkminkov]

pool is crap, simply it can't handle 80-100Ghash/s ...

[organofcorti]

1. NoFeeMining - yep me too. But unless they have a sophisticated antihopping strategy, I don't think they're handling the heat well.

2. Anyone spot the problem with this? I can't figure why it's not working. Something dumb I've missed probably.

Code:

api_address:http://api.bitcoin.cz/stats
api_method:re
api_key:<tr><td><strong>Shares contributed in current round:</strong></td><td>(\d+)</td></tr>

I'd welcome any help

[Clipse]

Im thinking they have some "sophisticated" antihopping strategy, new block found and pool hashrate doesnt remain as high as it used to.

What im thinking some hoppers figured out how to get around the dropped connections, whereas most hoppers havnt.

I will have to look into this.

[anty]

1. NoFeeMining - yep me too. But unless they have a sophisticated antihopping strategy, I don't think they're handling the heat well.

2. Anyone spot the problem with this? I can't figure why it's not working. Something dumb I've missed probably.

Code:

api_address:http://api.bitcoin.cz/stats
api_method:re
api_key:<tr><td><strong>Shares contributed in current round:</strong></td><td>(\d+)</td></tr>

I'd welcome any help

Regex should be correct, must be something else.

[organofcorti]

1. NoFeeMining - yep me too. But unless they have a sophisticated antihopping strategy, I don't think they're handling the heat well.

2. Anyone spot the problem with this? I can't figure why it's not working. Something dumb I've missed probably.

Code:

api_address:http://api.bitcoin.cz/stats
api_method:re
api_key:<tr><td><strong>Shares contributed in current round:</strong></td><td>(\d+)</td></tr>

I'd welcome any help

Regex should be correct, must be something else.

K thx anty

[Keninishna]

Im thinking they have some "sophisticated" antihopping strategy, new block found and pool hashrate doesnt remain as high as it used to.

What im thinking some hoppers figured out how to get around the dropped connections, whereas most hoppers havnt.

I will have to look into this.

nofee is showing like 25% stales for me this round.