Additionally, I wanted to clear up the Aug. 1st deadline BIP 148 UASF is null if Segwit2X locks in before. The UASF is making Segwit2X happen but is not need after activation. UASF was perceived dangerous b/c it could split change in two since it requires only small minority of nodes. Segwit2X def looks like it has 90-95% of total consensus which is very very good and should be very small risk of chain split.
You are viewing a single comment's thread from: