Topic: bitHopper: Python Pool Hopper Proxy - page 150. (Read 355816 times)

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.

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.


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

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.

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

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

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.

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.

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

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.

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?

mtred should work by default. Are you using the latest version?
Oh and mine_nmc and mine_slush are added.

Shares are stored in database as difficulty stamped (and once i add workers, difficulty and worker stamped). I'm not sure if the network code is taking that into account or if we serve the data like that. I should just serve an expected for each server. I'll take a look.

@c00w - while I've got you - are shares in the db assigned a difficulty level? My efficiency has been through the roof lately, and while this might be because I've only gone on backup once this week - today - I was just wanting to make sure that all shares weren't given the same difficulty since the efficiency will look better compared to the total coins you have and artificially elevate the efficiency. Or should we reset the db at each diff increase? Sorry if this has already been covered.

I have been mining bitcoins.lc for a while and have been monitoring it.  For the last few days I have only been able to jump to bitcoins.lc 30 minutes into a block which is like 177k shares.  I asked Jine straight up what was going on and he replied that he is randomly delaying stats 0-3600 seconds. 

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!

Excellent I'll try it on all non-XXMPS/Meni algo pools. See how we go compared to theory.

.

How are you noticing this - is it a difference between json and website? I'm at work and can't check, sorry.

with mtred: Never mined, they minted a new block!! hoppersden invite anyone 4 me plz?

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

Custom difficulty cutoffs?
Yeah. That would be pretty quick. I'll add it in. use mine_slush as role for a 10% cutoff.

32minute block.  Was awesome.