lol no HTTP - GBT uses HTTP coz (as you said) it was too hard for you to do such an enhancement

Adding an 'options' to Stratum is a minor thing - pity you can't even take the step past HTTP to see that's all it is.

"Isn't providing work fast enough" (even with BFGMiner) is most likely a problem with your miner, not the protocol. Con intentionally designed GBT support in cgminer to work inefficiently, but as a side-effect of this particular inefficiency, there is no excuse it should ever be starving for more work.

As usual - you don't even know what you are talking about.

So ... do we assume you are just stupid enough to make that comment?

... or lying to try and attack cgminer in a way that is completely false?

The "not providing work fast enough" message comes pretty quickly after long poll - may not be a big deal.

Yes, we have GBT testing on port 9000 now and Stratum testing will begin soon.

If I put GBT on main port now then users with cgminer with GBT support but earlier version than 2.9.4 will get 100% rejects. I need to add a workaround for this bug before enabling GBT on the main port, otherwise it could be pretty painful for some users.

I hope to move GBT and Stratum to main port within a week's time, if not before. Maybe before the weekend is over, if testing goes well.

Yeah, it will be GBT and getwork on the regular port and Stratum on a different one. But the GBT/getwork responses will have an HTTP header informing the miner where to find the Stratum port.

Ah, that makes sense. The solution I've used in the past with older bugger miner versions is the check the User-Agent.

BFGMiner interprets the Stratum header as "prefer Stratum over the current protocol", so IMO it would be better if it were only offered to getwork requests.

Don't forget Doc https://bt.irlbtc.com/view/27062.msg1218046;topicseen#msg1218046

The 5050 is fine

Don't you just 'love' how our luck got better AFTER the block reward drop ... bah

Sure, I'll add one of those ports. What's special about them anyway?


Hmm. So cgminer tries GBT first, and if it sees no Stratum header it stays on GBT?

In order of priority, cgminer will try to mine on stratum first, gbt second and getwork if all else fails, based on what order I think mining should occur. As far as I'm concerned, it's up to the pool operator to decide what they think is most important to prioritise. If you want to put a stratum redirect header in your GBT based pool, that's entirely your choice, knowing that cgminer will then use stratum preferentially. You can see the way cgminer prioritises the different protocols based on what I think is best for miners and pools, and the rest is up to you.