Sammy Libre

Extranonce is not needed we have uint256 space for it, please don't add any bs like that.

Last version (5.0) pushing bad shares before new block appears on a network and server sends `notify`.

@Genoil I believe the simple solution is to check if miner received target and job after `mining.authorize` before sending second immediate `mining.subscribe` request.

@the-Arioch I am not interested in your bs please never reply to me. @Genoil could you publish stratum sources, I am not asking about whole miner. Or at least reply...

6.0 ``` 14:43:38 pool : Connected! 14:43:38 pool : subscribed 14:43:38 pool : authorized worker X 14:43:38 pool : received new target: 0x01ffffffffffff... !!! stratum sent `mining.notify` right after `mining.set_target`...

After I connected to a pool I see 0 sol/s then after new job from pool (when new block found in network) it starts hashing. Very strange. Looks like after...

``` 2016/10/30 12:42:59 Stratum miner subscribe 2016/10/30 12:42:59 Stratum miner authorization request z:z 2016/10/30 12:42:59 Stratum miner subscribe

Protocol Flow Client sends mining.subscribe to set up the session. Server replies with the session information. Client sends mining.authorize for their worker(s). Server replies with the result of authorization. Server...

So they both violate spec then, flow is simple, must set_target followed by notify right after authorize.

@Genoil your miner sends 2nd subscribe regardless received it job after first auth or no, my software works correctly and pushing target followed by new job immediately after authorization request,...