Correct. Change penalty to 1.0 for mine slush...or as the cow up dere says you can leave it set to 4.0 and change role to mine.

Three quick blocks in a row just now. Gotta love that mine_slush role. Hope you guys got some shares in there.

Penalty should be set to 1.0 not 4.0. You can change it on stats page temporarily but the longterm solution is to change it in user.cfg.

Sounds like it was actually set to mine rather than mine_slush for some reason. I heard of someone else having that problem back a few pages. I just caught the current block at slush's and it stop slicing right at 11% so it does work at least part of the time. Catching those really quick blocks with such a small time investment is gold.

Yeah if slush is under the threshold when scheduler reslices and you have several other slices then it will empty all slices irrespective of threshold limits. I have 155.4% efficiency at slush with AltSlicer so it can definitely work.

Sometimes yeah. Usually only a few shares over though. You can minimize this effect somewhat by specifying custom min/max share values for altslicescheduler. Example:

 --scheduler=AltSliceScheduler --altslicesize=100 --altminslicesize=30

Defaultslicer is a simple time based scheduler. It doesn't weight shares it just assigns slices of time. The AltSliceScheduler assigns slices based on current block shares and attempts to mine intelligently. At this it is very successful IMO. I always specify --scheduler=AltSliceScheduler

Yer godlike! Ty very much!

...how quickly the hawks become vultures...

j/k

Yeah works great now for slush. Right after a block is found it goes to processing, then to none. If you submitted shares it then goes to your reward. It's a slow process there. It appears as though it says "none" on old blocks when zero shares were submitted and 0.00000000 when shares were submitted but decayed to nothingness.

Sounds pretty good to me, though I know less than nothing about regex.

Either way it's still not working...unfortunately. I have this for pools.cfg + user.cfg:

[namebit]
name: Namebit.org
namecoin: Yep
mine_address: pool.namebit.org:10000
api_address: http://namebit.org/
api_method: re
api_key: current_share_count">(\d+)</td>
url: http://namebit.org/details?username=http%3A%2F%2Fnamebit.org%2Fmy_account%2F(user)s

[Namebit]
# Namecoin pool, use mine_nmc . Good for hopping if you want some namecoins
#http://namebit.org/
#CHANGE THIS (if you want)
role: mine_nmc
user: Nxxxxxxxxxxxxxxxxxxx
pass: x
#passwords can be anything on namebit.org

Thanx I'll give it a whirl.

I dunno, it's an https, and I read of some having issues with twisted and https', but it used to work fine. I reinstalled twisted just in case and have quadruple checked my config for them. I'm also unable to visit their webpage from any computer in the house which would seem to amount to ip=ban. Great mining site too.

I must be in the doghouse. I can't even visit their webpage.

Yeah! Finally whitelisted. To the spaminator!

Could someone with regex knowhow take a peek at namebit.org's api? Last time I had it working was in an old ryo build, but I like c00w's altslicer implementation. Here's what I ported from the last working:

#[namebit]
#name: Namebit.org
#namecoin: Yep
#mine_address: pool.namebit.org:10000
#api_address: http://namebit.org/
#api_method: re
#api_key: current_share_count>(\d+)</td>
#url: http://namebit.org/details?username=http%3A%2F%2Fnamebit.org%2Fmy_account%2F(user)s

TIA

@eskimo, have you tried --scheduler=AltSliceScheduler? It's operation is a good deal more intuitive to my mind.
 
Is Polmine.pl down for everyone or just me?

Thanx I look forward to joining the discussion. Since I've read every page, used 30 different versions of bithopper from a few different forks and interacted with several of you guys on github already I feel like I've already joined...but apparently we have to have classes, and probation first. Can't have people just willy nilly contributing without being made to feel as though they've done something wrong first. I imagine the few spammers that perpetuated this change in policy are laughing their arses off.

I'd like to be allowed to post because although I am a relative newcomer to bitcoin mining I have significant expertise in the computer hardware and software engineering fields. I read the lengthy bithopper thread while trying out various builds and feel that I have substantial resources to bring to the table and would like the opportunity to contribute to the discussion and hopefully development.

Cheers.

...yes I cannot post anything, because I'm one of those worthless "newbies". Talk about rewarding spammers for bad behavior. Lets punish 30% because .03% of new users are doucheaseauri. Security gone wrong once again.

I have a ton of ideas to add to the discussion.

How long before I can "graduate" and get my big boy pants?