So I can just tell my miner to use the GBT protocol?

I would be happy provide some context.

Solo mining against the Bitcoin-QT client results in allot of shares being leaked over to backup pools.  So it seems something needs to be done at some point so that folks with high hash rate ASIC's can solo mine without the need to setup there own pool software to do it. 

Currently I have about 20Ghs of ASIC's and when I solo mine I get this behavior.

My thought was to implement the stratum protocol as an option for the mining software to communicate with the Bitcoin Client in server mode.  Right now that is done with the old getwork protocol.

My other thought was to implement variable difficulty, but after thinking about that I realized that was probably silly since, I think, the mining software is only going to submit shares that meet or exceed the current difficulty anyway.

So does that explain what I'm thinking better?
Thanks,
Sam

When will there be variable or use defined difficulty and stratum support in the Bitcoin client?  It seems it is needed very badly.

OK, lets read it again.


So your saying now that BTC Guild's portion "of the network hashing power" is just peachy?

At any rate BTC Guild hash rate is accountable to it's miners so therefore much safer for the network.  These other hashing entities are unaccountable to anyone so they can do whatever they want and they are growing very fast.  So if BTC Guild is now a smaller percentage of the network I'm not so sure that's a good thing overall as reputable pools are not taking up that slack.

I haven't load balanced since my GPU days.  It's just too easy to setup multiple instances now with the usb devices now I just have no need to load balance.  But when I did it with my GPU's my stales increased, but no where near 20%.  Maybe 1 or 2%.

I don't think so.  You stated that DDoS'ing BTC Guild was a good thing because you are of the opinion it's hash rate was too high.  The reality is BTC Guild hash rate increased dramatically during the DDoS.

You can set a hash rate quota per pool.  Such as set one pool to 30% another to 20% and another to 50%.  Something like that.  Haven't really looked into it myself yet.  It's the the CGMiner readme I'm sure.

That is way higher than my experience.  My problem with load balancing was that the split was very uneven.  But now with the new quota method it may be better.

CGMiner can so I suppose BFGMiner maintained that capability when it was forked.  That is one of their main strengths is to have multiple pools for failover, balancing or one of several other mining strategies.

My snarky remark wasn't wasn't meant to imply that I thought it was a bad idea.  And if they incorporated it into CGMiner again I would certainly use it.

But, if I remember correctly, it ended up increasing the development workload for ckolivas dramatically more than the revenue it brought in was worth plus it ticked off allot of people.

But maybe it would be a different story now with the increased value of bitcoin and the stratum protocol?

I just would hate to see ckolivas and kano's workload increase with little or no benefit.  But hey who knows.

Good thing the attack has decreased BTC Guilds overall hashrate.

Too bad your *opinion* doesn't quite square with reality.

Because..., it was such a huge success the last time it was tried?

Sorry!

All I was trying to say was *If* you wanted to use some other driver for *anything* you changed with Zadig you could always change it to something else.

You should never need to change the driver again.  As far as I know.

You only need to run Zadig to install the WinUSB driver once.  On reboot they should come up to WinUSB every time.  If you need to use a different driver you can run Zadig again and select a different driver.

Uh, no.

3.1.1 uses the serial drivers.

3.2.x and later requires the WinUSB driver in Windoze.  And Zadig can install that for you.  Usually you remove all of your BE's but one, have Zadig install the WinUSB driver for it and then add your remaining BE's and they should all default the the WinUSB driver after that.

Easy peasy.
Sam

I have 38 BE's running with no issues.

I haven't heard that Zadig is keeping 3.5.0 from working.  I'm still at 3.4.3.  I haven't gotten around to updating but that version has been fine for me.

People keep saying stuff like that and I just don't understand it at all.

Setting up CGMiner with my Block Erupters was the easiest and most trouble free install of new mining hardware I have ever had.

I was nervous because so many other people were having problems.  But after I did my install and setup I realized that virtually nobody was reading the ASIC Readme and were doing everything the most difficult and complicated way and all for no reason.

CGMiner is very BE friendly with Win7.

Now if your using WinXP that's a completely different story.  I tried setting up one of my XP machines as a backup mining rig and that was a disaster so I used my Win7 laptop as the backup and that worked flawlessly as well.

So with not knowing what your issues are I would suggest reading the ASIC Readme and follow those instructions.  Then check the Advanced USB Options in the readme if you want to do anything out of the ordinary.

If you still have trouble please post what the problems are.
Sam

Uh, point your miner at Deepbit.

Also make sure you have failover pools setup.  Getwork may not keep it completely busy so shares will/can leak to other pools.

Add
"--usb BAS:0"

It is covered in the readme under Advanced USB Options

You need to run Zadig and install WinUSB for that device.