I think I have fixed deepbit hopping to work. My changes to the scheduler were not set up correctly. On a visual front i forgot to reverse the byte order for the block number.

EDIT: These changes aren't on github yet. I'm still testing.

Hey,

So those attackers you are seeing using chrome aren't attackers. They are pool hoppers.

-c00w

Yeah. Neither have I. There were a lot of bugs. The latest version has all the ones we found fixed.

@bb
Um, I fixed a website.py bug. Not sure if that was the only one.

@zybron
thats a bug. I should fix it.

Well patch is the actual program to do the patching. I don't know if its on windows however.

Can you give me an error log with --debug?

lp error?
I think I fixed it.
Website loading error?
I think I fixed it.
Too many sockets error?
Not sure where it is coming from. But i Have a sneaking suspicion what I added to client.py is causing it.

EDIT: So if you are on the bleeding edge: UPDATE!

can you post a debug log? I just disabled ninjaex because it was bugging me. Also update to tip. I had some nasty bugs with api polling times during errors.

Errors with too many selects:
Fixed. Hopefully. I think there were rare situation where LP could duplicate calls to the server. I fixed it so it should only do one LP per server.

EDIT:
If you still get those sorts of errors, Tell me.

I made a change in the pool api error system. Can someone try and capture that error with --debug?

bb has a fix which he said he would make a pull request for tomorrow.

How is it broken? It loads for me.

Use the latest build with whatever scheduler you want.

If you want to mine deepbit you need to use the default slicer and run with --startLP as well as having deepbit set with mine_deepbit in user.cfg.

If you don't run with --startLp you won't mine deepbit.

Oh thats debug output. I left it in accidentally. I'll fix it.

And if you are on linux do ctrl+shift+c. I'm not sure how to do it on windows.

I think I fixed LP based hopping of deepbit. At the bare minimum I fixed a bunch of LP bugs. Um, it only works with the default scheduler for now. And it mines for the entire period of a block. So I'm not sure if its that great of a system.

Um, I didn't write altslicer. But the guy who wrote it doesn't appear to be maintaining it. So I'll take a look and try and fix it ignoring pools. The default slicer reslices properly.

EDIT: Oh and I'm debugging the whole deepbit hopping not working. Stay tuned.

That could work as well. People have been kicking it around for a while and well nobody ever did anything. If someone could figure out how hashrates scales to shares/second I could probably do it myself.

I only turned it on for the default. And Its looking like it doesn't work. I'm going to have to do some more debugging.

@beef
Well you have to have a LP system which supports it to hop deepbit. Which is why the bitHopper LP system got rewritten.

So there may be some lag before everyone else catches up. An implementation is always worth more than the idea.

Um, I just switched a bunch of pools to be info without setting up associated acounts & passwords. A bunch of them worked. So if you don't want to have to deal with it, don't.