Bitcoin Fork Monitor
This web site looks like a good dashboard!  Although, I'm not up on the technical details of everything going on here, so some of it is confusing to me, because there's not as much background as I'd like.<p>I've spent some time reading around, and here is my <i>guess</i> as to what the site is describing:<p>Behind the scenes, achow101 (<a href="https://github.com/achow101" rel="nofollow">https://github.com/achow101</a>) is running four Bitcoin clients:<p>* `Bitcoin Core` is running the client from <a href="https://bitcoin.org/en/" rel="nofollow">https://bitcoin.org/en/</a> (<a href="https://github.com/bitcoin/bitcoin" rel="nofollow">https://github.com/bitcoin/bitcoin</a>) (<a href="https://bitcoincore.org" rel="nofollow">https://bitcoincore.org</a>).  This client does not support Segregated Witness, and it does not support larger block sizes (so blocks larger than 1 MB are ignored).<p>* `UASF (BIP 148)` is running the client from <a href="https://bitcoinuasf.org" rel="nofollow">https://bitcoinuasf.org</a> (<a href="https://github.com/UASF/bitcoin" rel="nofollow">https://github.com/UASF/bitcoin</a>).  This client supports Segregated Witness.  This client does not support larger block sizes (so blocks larger than 1 MB are ignored).<p>* `btc1 (segwit2x)` is running the client from <a href="https://segwit2x.github.io" rel="nofollow">https://segwit2x.github.io</a> (<a href="https://github.com/btc1/bitcoin" rel="nofollow">https://github.com/btc1/bitcoin</a>).  This client supports Segregated Witness, as well as changing the block size to 2 MB (blocks larger than 2 MB are ignored).<p>* `Bitcoin ABC (UAHF)` is running the client from <a href="https://www.bitcoinabc.org" rel="nofollow">https://www.bitcoinabc.org</a> (<a href="https://github.com/Bitcoin-ABC/bitcoin-abc" rel="nofollow">https://github.com/Bitcoin-ABC/bitcoin-abc</a>).  It supports blocks of <8 MB in size (initially defaulting to 2 MB).  This client does not support Segregated Witness.<p>As I understand things, right now there are two events which have hard-coded dates:<p>* At midnight UTC on August 1, the `UASF (BIP 148)` client <i>will</i> fork, in that it will start ignoring new mined blocks which do not support Segregated Witness.<p>* At 12:20 UTC on August 1, the `Bitcoin ABC (UAHF)` client <i>might</i> fork.  I say <i>might</i> because the fork will be triggered by someone mining a larger-than-1-MB block (the "trigger block") on or after 12:20 UTC.  (1 MB is the largest block that the `Bitcoin Core` and `UASF (BIP 148)` clients will recognize).  At that point, `Bitcoin ABC (UAHF)` nodes will treat the "trigger block" as valid, and the fork has occurred.<p>Also, there is another event which may take place, depending on various conditions:<p>* If—sometime soon (before midnight UTC on August 1), and for a long-enough period—enough people indicate support, then the `btc1 (segwit2x)` node will fork with the `UASF (BIP 148)` node (in that both nodes will start supporting Segregated Witness).  Sometime after that fork, the `btc1 (segwit2x)` node will fork off into its own fork, which will have support for 2 MB blocks.<p>And of course, there is one event which will happen at some point:<p>* `Bitcoin Core` will release a new version, adding support for Segregated Witness, or for a different block size, or both.  `Bitcoin Core` nodes, when they upgrade, will then join one of the forks.<p>Anyway, I _think_ that's right, but this has gotten really complicated, and I'm trying to skip over the specific details, and the rationale (since, as tempay mentioned, that's been discussed recently).<p>If I misunderstood something, please let me know!