Currently, both the first and second extra nonces are updated on new work and iterations of the mining loop and the first extra nonce uses a per-device byte to ensure unique work is being performed on each device.
However, proper stratum support requires using an extra nonce assigned by the pool for the first nonce as well as respecting a provided length for the second extra nonce.
This paves the way to be able to properly support those semantics by reworking the nonce handling to avoid modifying the first extra nonce during the mining loop, moving the per-device byte to the second extra nonce, and rolling the second extra nonce during mining loop instead.
Currently, both the first and second extra nonces are updated on new work and iterations of the mining loop and the first extra nonce uses a per-device byte to ensure unique work is being performed on each device.
However, proper stratum support requires using an extra nonce assigned by the pool for the first nonce as well as respecting a provided length for the second extra nonce.
This paves the way to be able to properly support those semantics by reworking the nonce handling to avoid modifying the first extra nonce during the mining loop, moving the per-device byte to the second extra nonce, and rolling the second extra nonce during mining loop instead.