Actual Changes from TML 1.11 to 1.12:
* a bit of whitespace here and there
* changed the default bitstream name from kreisel to leibniz
* fixed a misspelled parameter name in the usage info screen
* changed a couple of copyright headers
* bumped the version number to 1.12
Looks if code changed to avoid send of shares below difficulty. May be because of load on TML servers. It would be excuse for not allowing connections from older client.
Bitstreams significantly differ, but could be result of compilation of minor change. Appears some midstate java code calls simplified. Could be reason for larger bitstream, to move into fpga. Midstate changes relate to signcryption and could be server affecting as well.
I am guessing based on simple analysis of available source code and eyeball + tools of bitstreams.
Indeed, besides pushing a new bitstream he also implemented difficulty >1 support, wow!
But why on earth does this warrant a breaking protocol change AT ALL? (Not to even mention that there was no prior notice.)
Well, maybe the old bitstream contained some critical flaw in the signcryption code that was fixed in the new one? I can't think of a different (rational) explanation. But OTOH it wouldn't be the first time for ET to act in a completely irrational way.