I assume everyone gets the reference
Topic: bitHopper: Python Pool Hopper Proxy - page 134. (Read 355816 times)
If you spend your life only worrying about squeezing every ounce of profit, you'll end up like this guy:
I assume everyone gets the reference
I assume everyone gets the reference
This will be the best PR you guy can get 
Help the guy who helps you. This is what small pools are all about.
Help the guy who helps you. This is what small pools are all about. Exactly, a little altruism here and there never hurt anybody, and we can probably end their block from hell, which will make us look really good. You want to turn the negative attitudes from miners, this is the way to do it. I guarantee you they will all appreciate it. I'm not saying stop mining at profitable pools, but as a backup here and there, help a brother out
Just because I always get a little tickle when I see 420 anywhere...
They got that far, they should aim for >10mil atleast
I actually feel really bad for them... we should all jump in there and get them past this horrible hump. It'll be good PR
hurrah for self quoting.. I just did actually, set them up as my backup. It would be really nice for others to do so as well. If enough of us jump in there it would be a huge help, and given they are considering changing their payout structure to keep us out, maybe it would discourage them from doing so
get a commitment from pool op to not change payout system and THEN I'll consider a backup option, but presumptive good will often proves ineffective.
This will be the best PR you guy can get
Help the guy who helps you. This is what small pools are all about. 
Quote
Why was nofee disabled again?
they were lagging bad for some folks.. I'm mining there no problem and many others.. go for it.
Quote
Edit: and poolmunity?
they implemented a new payout scheme that doesnt work for usQuote
(Where is that wiki! )
they appear to be working on things at the hoppers den
Why was nofee disabled again?
Edit: and poolmunity?
(Where is that wiki!)
Edit: and poolmunity?
(Where is that wiki!
) 
Just because I always get a little tickle when I see 420 anywhere...
They got that far, they should aim for >10mil atleast
I actually feel really bad for them... we should all jump in there and get them past this horrible hump. It'll be good PR
hurrah for self quoting.. I just did actually, set them up as my backup. It would be really nice for others to do so as well. If enough of us jump in there it would be a huge help, and given they are considering changing their payout structure to keep us out, maybe it would discourage them from doing so
get a commitment from pool op to not change payout system and THEN I'll consider a backup option, but presumptive good will often proves ineffective.
Just because I always get a little tickle when I see 420 anywhere...
They got that far, they should aim for >10mil atleast
I actually feel really bad for them... we should all jump in there and get them past this horrible hump. It'll be good PR
hurrah for self quoting.. I just did actually, set them up as my backup. It would be really nice for others to do so as well. If enough of us jump in there it would be a huge help, and given they are considering changing their payout structure to keep us out, maybe it would discourage them from doing so
*cough*http://hoppersden.info/showwiki.php?title=Pool+Status*cough*
There are some reason: fields needing filled, btw.
There are some reason: fields needing filled, btw.
*couinvitegh*
Just because I always get a little tickle when I see 420 anywhere...
They got that far, they should aim for >10mil atleast
I actually feel really bad for them... we should all jump in there and get them past this horrible hump. It'll be good PR
ed64
like the merging you are doing. New hopper looks nice.
one small thing... in the password.py.default
can you copy and paste the pools that arent in use and the ones that are.... into the right section.
sure it will annoy someone who isnt away of the pools we have disabled to fill up that "pools in use" section to only find out most of them arent.. and then worse, find out that a good bit of the pools "not in use dont worry about changing the user or pass" are actually in use and you are mining for someone else.
like the merging you are doing. New hopper looks nice.
one small thing... in the password.py.default
can you copy and paste the pools that arent in use and the ones that are.... into the right section.
sure it will annoy someone who isnt away of the pools we have disabled to fill up that "pools in use" section to only find out most of them arent.. and then worse, find out that a good bit of the pools "not in use dont worry about changing the user or pass" are actually in use and you are mining for someone else.
I'm going to abandon that branch and start hacking away at c00w's. I like the new pool.cfg, thought about merging that into ryouiki's branch, but decided to just jump to c00w and merge in the hopping logic into c00w's in a pluggable fashion.
Plan is to:
- Configurable scheduler at startup (eventually runtime)
- Merge in ryouiki's round time selection
- Merge in flower's time slice
- Add hybrid roundtime + timeslice scheduler
Current work so far:
- Work done to seperate scheduling/hopping logic away from code
- Need to find a way to easily modify the website depending on the scheduler (e.g. for slicing, add in a slice column)
Will push my changes in soon, maybe someone can help out with implementing new schedulers
PS Any hoppersden invites?
Just because I always get a little tickle when I see 420 anywhere...
They got that far, they should aim for >10mil atleast
Just because I always get a little tickle when I see 420 anywhere...
3) Bitclocker sucks?
Yep. Not sure how to fix it.
Yep. Not sure how to fix it.
Sounds like a fix would be to allow multiple workers per site in the config
Ill keep testing and if possible others should do the same, but so far multiple workers seem to do the job. I do however think that its also likely not the real solution considering I see other people in bitclockers stats under worker running at >15gh so clearly they are also running multiple gpus behind one worker and not having these issues (unless they are and simply dont care and the stats wont show there reconnection drop of gh speed)
3) Bitclocker sucks?
Yep. Not sure how to fix it.
Yep. Not sure how to fix it.
Sounds like a fix would be to allow multiple workers per site in the config
Is there a way to reset the graphs? Mine are messed up now.
Also, can't stay connected to bitclockers for more than a minute at a time.
Also, can't stay connected to bitclockers for more than a minute at a time.
Hit refresh
1) Namecoins?
You switch the role to mine_nmc.
2)Issues with the graph?
refresh.
3) Bitclocker sucks?
Yep. Not sure how to fix it.
You switch the role to mine_nmc.
2)Issues with the graph?
refresh.
3) Bitclocker sucks?
Yep. Not sure how to fix it.
How is mining namecoins implemented into this? Reason I ask is that when the next difficulty increase happens namecoins are gonna be more profitable...
Right now at current nmc/btc conversion, bitcoins difficulty must increase to to just <3million to be equal in diff=price. The next namecoin difficulty which is more than a month away at current rate would make namecoins more profitable than current bitcoin difficulty.
Eitherway, bitcoins will be more profitable to mine for a long time.
From what I could figure out it seems like bitclockers is limiting the getwork requests per worker which makes it a pain in the ass to use reliably.
Ive setup multiple workers and holding stable connection now but as soon as I push all my gpus through one worker the crapshoot starts to happen.
Ive setup multiple workers and holding stable connection now but as soon as I push all my gpus through one worker the crapshoot starts to happen.
How is mining namecoins implemented into this? Reason I ask is that when the next difficulty increase happens namecoins are gonna be more profitable...
Jump to: