Nearly every stratum pool I have seen supports the version-rolling extension. that adds a version_bits field to mining.submit. afaik It's necessary to support ASICboost.
You learn something everyday. I've not seen any reference to this extension.Quote
Where does 60x come from? every 30s is pretty leisurely compared to every 8ms @ 500 GH/s with nonce rolling alone!
I don't know where I've read that you may only increase ntime, and only upto 60 seconds. Reading ck's pool source I findQuote
/* Ntime cannot be less, but allow forward ntime rolling up to max */
if (ntime32 < wb->ntime32 || ntime32 > wb->ntime32 + 7000) {
err = SE_NTIME_INVALID;
So at least ckpool allows upto 7000x! No more xnonce2 rollover needed for small miners if (ntime32 < wb->ntime32 || ntime32 > wb->ntime32 + 7000) {
err = SE_NTIME_INVALID;
Quote
120 TH/s over 3 hashboards = 40 TH/s each, which means each hashboard can cover the 32 bit nonce space in 0.1ms. The newer ASICs have more midstates too, so that means bigger job packet. No way serial can keep up. It makes sense that they would include some sort of work generation on-chip. I'm really curious which field they are rolling.
Exactly.