all but one pool is on the chain you didn't choose....
3 explorers, Exchanges, most masternodes are on the chosen chain. This was not a quick choice in which chain to choose as valid. We went with the more active chain when it came to consensus.
Edit:
The chain that was chosen was picked cause it had the majority of the masternodes on it, all 3 explorers were on it. Pool was the last thought in our minds as we don't know who is updated to 2.0.0.5 yet and that's what caused the fork. 2.0.0.5 has IPv6 support and was a mandatory update, so far almost everything on 2.0.0.5 is on the chosen side of the chain other than a few outliers. In the end it came to Have a few Pools resync or have a hundred + Masternode operators resync.
