Okay and back on topic, it looks like a showstopper bug has shown up in their segwit2x code.
They've hit the >1MB hard fork on testnet which refuses to accept a block unless it is bigger than 1MB:
https://github.com/btc1/bitcoin/issues/65At this point there aren't enough transactions to create a second block with more than 1MB of transactions on testnet, leading to a fork with 6000 blocks that aren't using the 2x code and the two forks not speaking to each other.
They argue that mainnet is busy enough that there will always be blocks with more than 1MB of transactions so it won't be a problem.
This is utter bullshit as over the past week I've seen my mempool easily get down below 1MB of transactions now that the transaction spam has ended on mainnet. Making a followup block mandatory 2MB when nothing forces mining to do so is a showstopper IMO.
Now they're all scrambling and arguing how to tackle it... This is going to be interesting. I might start selling popcorn.
that means that this segwit2x fork will activate only if miners built a block with more than 1mb? And if not the network will be stall until this happen? lol