With 4233:
INFO : [00:30:59] : New block #6110 received, new difficulty is 423.982
INFO : [00:31:25] : New block #1189444 received, new difficulty is 13.730
Not a VIVO
Can the hsrminer ignore blocks that go out of order? In theory, if the connection was not interrupted, then the blocks should follow strictly in order...
That's a good idea to keep working on the previous block when something like this happens, but it's highly possible that every share sent will be rejected because in that particular case bug is on the poolside. But I'll experiment with this.
P.S: altminer is good to check connection drops because every time miner reconnects pool sends welcome message.