Topic: bitHopper: Python Pool Hopper Proxy - page 23. (Read 355768 times)

optimal for efficiency, variance, or the best of both? Also what size pools are you using and how many of each?

Witch Switches/parameters do I need to start BH in a "optimal" state?

At the moment (0.1.8-8) I got: --auth user,pass --startLP --p2pLP
(& suppose nothing for --scheduler means "DefaultScheduler", or is better to set it with "OldDefaultScheduler")

 

In relation to that joulesbeef - can you explain why some SMPPS doesn't pay full share? I thought the payout might take longer but you always got the full amount eventually (if the pool doesn't fold). But from what I've read lately this might not be the case. Is that right?

BTW, another plus for abcpool is that it looks like there's no wait for confirmations of the block, although I don't see how that would work.

Edit: and they pay for stales, too, and specifically welcome hoppers. I hope they survive their first round of bad luck! Upside is they've gone from 90 to (now) 120 Ghps overnight.

not bad and they pay full share value.. pretty surprising..ars does as well but they are bigger.

http://www.abcpool.co/

no fee PPS with instant payout. Currently 118 Ghps.

Use 'em as backup before they fold!

lots of no json can be decoded errors.. from a multitude of sites.

otherwise running fine

v0.1.8 is tagged. It should be quite stable and the auth bug is fixed. --p2pLP is still a mess.

Updated AltSliceScheduler to allow for round time biasing. Available at:
https://github.com/echiu64/bitHopper

Tested for a few hours, everything looks like it works. Tested with startLP enabled.

New options:
 --altsliceroundtimebias Bias slicing slightly by round time duration with respect to round time target (default false)
 --altsliceroundtimetarget Round time target based on GHash/s (default 1000 Ghash/s)
 --altsliceroundtimemagic' Round time magic number, increase to bias towards round time over shares (default is 10)

@paraipanakos: that works, thanks! I run it without --auth, then I´ll try to set up my workers with the same user/pass as in the auth command just to see if work

@joules your post made my day man, should be a first post or in a wiki page I swear

Yeah I wish this thread was some what organized but you can look at the past two pages to see our debates on these issues. And chart porn.(i'm constantly questioning  th small pools but the math tends to prove me wrong) Wow 2ghz, that is small huh, what was the share percentage at? You probably didnt look did you? Why do I ask?

How much ghs do you think they will have when that share percentage = 0%

we can turn a small pool into a medium sized pool, pretty darn quick.

second, you saw quite a few pools in our cfg, no? not just that 2ghs?

Did you know the paper written on hopping that found a 128% increase in rewards was a study on hopping one prop pool and having one pps pool? 2 POOLS!!!!!

Cant find one single solitary pool in our list fast enough for ya?

Snarkiness aside there is a reason why this thread is so long, and why there is so much debate in hopping.

It isnt all flowers and chocolate though.

The hopper is in middle of constant development.  And not like firefox or something where you get the releases after extensive testing, YOU ARE THE TESTER. There will be bugs.(learning how to properly report bugs will be an asset.. first see if you are up to date, second see if someone reported it, if not you probably want to turn on debuging and try to catch the bug in the debug logs and post that for c00w and the crew)

the pools are also in a constant state of flux, especially the small pools. Many small pools use us, to get bigger, and then shut us out when they do.

I enjoy hopping, I like the concept, I like the math and chart porn, I like the debate, and I even like the constant updating. and oh yeah the rewards arent too bad either. It's not for everyone but it is rewarding for those of us that want to do this.

same as r2edu, try using same auth for your miner as in --auth user,pass param of bH if your using that or run bH without --auth

In the latest version (ca5def9fb22871680d562d8e75eb4b6650f36321) I have some problems with connecting my miners. They seem to not find the proxy anymore and in the bh-log I can see, that the miner is answered with status code 401. Apparently the miners have to connect now to ":8337/LP" or do I understand the code wrong? But even then it takes very long until the miner (phoenix 1.50) actually starts to do something.

to complement organofcorti quick answer you could visit the wiki page to make an idea of pools speeds

edit: @r2edu try using same auth for your miner as in --auth user,pass param of bH, if your using that of course

I can´t make it work neither of the two latest versions of bh I download (0.1.7.2-65 / 81). Both starts ok but then my miner, guiminer, doesn´t connect... I don´t get any getwork

I go back with the 0.1.7.2-53 and works fine... any suggestions?

There are real problems with only hopping slow pools but you will still get increased efficiency from hopping. The problems I can think of are:

• hugely increased variance
• With long solve times you have to wait quite a while for the pay off
• you have to have a very large number of small pools to hop to so you can stay below your hop point
• new pools have changed payout schemes mid round to make hopping non-viable
• new pools could be a scam

However pool hopping still works and can bring in significant dividends if you're patient and can deal with the variance somehow (eg slicing).

Edit: After rereading your post and giving it a bit more thought, I realise I missed your point - if your hashrate makes a significant portion of the pool hashrate then it would seem to approach mining solo. Interesting point and I had to give it some thought, but I still think a tiny pool is hoppable because after you leave it still keeps looking for the block. That doesn't happen when you go solo.

lol a pool with 2 gh/s is more like a puddle. That is too slow for me to considering hopping.

organofcorti,

I did even better, I went to their home page were I found out about the speed, now, to be clear, I have nothing against slow pools and even fast ones were slow when they started.

I was questioning pool-hopping if the only hoppable pools are slow ones.

I was asking myself and this forum, is hopping very slow pools ( there is a pool which has 2 GH of capacity, so it is slower than my three righs together ) still giving some real advantage? Isn't it, in the end, like going solo?

best regards.

spiccioli.

quick reply - go to pools section of forum, check off the available pools against hashrate.

wtfman,

it is a big downside.

hopping promises me a few % more in gains but then I have to hop pools that find a block in a month or more... well, maybe I'd better be going solo than hopping.

spiccioli.