Short update here:-
1. DragonMint's have version-rolling AsicBoost support (reference).
2. Shipping will begin around March 15 - 22, but there's a lot to ship so please be patient.
3. Shipped version number will be T1, not 16T due to some mixup with Russian import documents that cannot be changed in time.
4. This picture is legit and the final version that will ship https://twitter.com/MyRig_com/status/971205544533835776
5. Phillip will get a demo machine once the shipping starts. But the reason for the secrecy was AsicBoost capability could be revealed before the patent holder opened the patent. This is unfortunate, we would have preferred more openness, but it is what it is, patents suck, but in this case, the patent can help protect the Bitcoin ecosystem. Now we're so close to shipping, we'll just give a demo machine to phillip once we ship.
Some references:-
https://blockchaindpl.org/
https://www.emergingtechlaw.org/analysis/creating-the-blockchain-defensive-patent-license420182
https://www.asicboost.com/single-post/2018/03/01/opening-asicboost-for-defensive-use/
https://blog.bitmex.com/defensive-patent-licence/
https://blog.bitmex.com/graphical-illustration-of-a-bitcoin-block/
https://bitcoinmagazine.com/articles/there-bitcoin-patent-war-going-initiative-could-end-it/
https://bitcoinmagazine.com/articles/slush-pool-now-compatible-asicboost-miners/
http://stratumprotocol.org/
The following pools are already version-rolling compatible: slushpool.com, ckpool.org, bitcoin-india.org
The following software is patched or has pull requests open or about to being worked on: btcpool, ckpool, cgminer
1. DragonMint's have version-rolling AsicBoost support (reference).
2. Shipping will begin around March 15 - 22, but there's a lot to ship so please be patient.
3. Shipped version number will be T1, not 16T due to some mixup with Russian import documents that cannot be changed in time.
4. This picture is legit and the final version that will ship https://twitter.com/MyRig_com/status/971205544533835776
5. Phillip will get a demo machine once the shipping starts. But the reason for the secrecy was AsicBoost capability could be revealed before the patent holder opened the patent. This is unfortunate, we would have preferred more openness, but it is what it is, patents suck, but in this case, the patent can help protect the Bitcoin ecosystem. Now we're so close to shipping, we'll just give a demo machine to phillip once we ship.
Some references:-
https://blockchaindpl.org/
https://www.emergingtechlaw.org/analysis/creating-the-blockchain-defensive-patent-license420182
https://www.asicboost.com/single-post/2018/03/01/opening-asicboost-for-defensive-use/
https://blog.bitmex.com/defensive-patent-licence/
https://blog.bitmex.com/graphical-illustration-of-a-bitcoin-block/
https://bitcoinmagazine.com/articles/there-bitcoin-patent-war-going-initiative-could-end-it/
https://bitcoinmagazine.com/articles/slush-pool-now-compatible-asicboost-miners/
http://stratumprotocol.org/
The following pools are already version-rolling compatible: slushpool.com, ckpool.org, bitcoin-india.org
The following software is patched or has pull requests open or about to being worked on: btcpool, ckpool, cgminer
Thanks a very nice thing to read this morning.