Current bit coin SegWit2x, UASF, UAHF progress composition
Bitcoin scaling and SegWit have been summarized by 
SegWit2x v1.14.4 final candidate version release
I have a lot of bitcoin news today, so let me take a quick look. The SegWit2x (btc1) v1.14.4 final candidate version was released today because the SegWit2x was scheduled to be released on the 14th. Finalists will be used as they are if there is no bug in the code. You have just uploaded the source code without the release notes. Segwit2x Release Candy Diet If you refer to the public (add article) during this weekend, there seems to be no big problem in the code until now. As for the bug and this part, this week is the test period, so it would be nice to wait for Core team developers and other developers to review the code.
BitMain SegWit2x Support and UAHF (ABC) Progress Statement Announced
I created a tweet to run SegWit2x from all pools running on BitMain, which had previously taken a vague position. In addition, ViaBTC Mining Pool has released a statement on User Activated Hard Fork (UAHF). Simply put,
The coin of BCC (Bitcoin Cash) will be launched by activating UAHF (ABC) at 9:20 pm (KST) after 9:00 am on August 1 (KST) UASF
BCC (Bitcoin Cash) is not a bit coin, but a new coin (saying it is one of the alt coins)
BitMain and ViaBTC will support and activate SegWit2x
Open the BCC mining pool on July 22 and proceed with the S9-BCC mining contract
From July 22 (UTC), users of ViaBTC Exchange will exchange BTC 1: 1 ratio with BCC and BTC_FROZEN2
(* BTC_FROZEN2 will be paid back to BTC after listing the BTC tied up before listing.
August 1, BCC / CNY deal listed and paid to the persons who participated in the BCC and BTC_FROZEN2 (BTC).
It goes like this, but here it is worth noting that BCC (Bitcoin Cash) is not a bit coin but another coin, that is, altcoin. It is also important to proceed with BIP91 and activate SegWit before proceeding with UASF. The big block support miner is offering new options, but the current community is doing well. Personal thoughts can be felt as a very smart Uji Han's business. I am selling the mining prayer and launching my own coin (BCC, Bitcoin cash and Bit China coin); I am making the creation economy less impact on bit coin as much as possible. I feel like I'm going to BCC ICO. In the community, it is the atmosphere in which the part that has continuously returned to anxiety at UAHF is dissolved. The fact that the coin ABC (UAHF) is constantly being developed and that there is no mention of abortion seems to be going on even if the UASF is not implemented.
Problems of Big Block
Source: Bitfury Block Size White Paper 1.1.1 PDF
Please refer to the Bitcoin SegWit2x and Miners Centralization article, which explains why the previously created block size increases the threat to your network security. I have a lot of good material about block size, so I will try to write some more explanation after previous post. The problem of centralizing the nodes comes as a big bite, as big blocks are adopted. As you can see from the above image, if you adopt the 8MB block size, you will need equipment that will run a huge specification node based on current network and storage technologies. Daily traffic is close to 100GB + alpha and you need about 1GB of storage per day. If this 8MB block size is adopted, 95% of the existing normal nodes will not be able to maintain the node within 6 months. As only the top-level nodes survive, the centralization of the nodes causes a tremendous threat of block-chain network security. Of course, this 8MB is based on when it is full. In that sense SegWit's optimization of the block chain capacity seems to be an essential challenge.
If you are supporting UASF (BIP148), we recommend that you run the UASF client in advance.
Achieved 1200 UASF nodes
The number of nodes in the UASF (BIP148) is steadily increasing. In short, the UASF is against the power of the Chinese minors. Please refer to the previous post for related content. To recapture common misconceptions, BIP148 (UASF) will be on August 1st at 9:00 am (KST), and if it is activated, it will be rejected unless it is a SegWit block. UASF does not need to operate if the BIP91 is in progress before that. BIP91 is to activate the SegWit BIP91 (Bit 4) by lowering to 80% that the previous SegWit BIP141 (Bit 1) should receive a 95% approval signal. In other words, when BIP91 is activated, SegWit is activated, and BIP91 will also reject all blocks, not SegWit blocks.
To summarize, if BIP91 is activated and SegWit is successful, you do not need to worry about UASF. However, we will proceed with the demonstration to encourage the UASF to activate the SegWit unconditionally, as the minors change words such as the sudden change of the seas. UASF supporters can run the UASF node client on their personal PC. Proceeding immediately before August 1, it may take a long time to download all of the block chain data close to 120 GB, depending on network conditions. If you run a different bit coin node, you do not need to download the block chain data again. Just run the new node client.
SegWit2x node: https://github.com/btc1/bitcoin/releases
Core node: https://github.com/bitcoin/bitcoin/releases
UASF (BIP148) node: https://github.com/UASF/bitcoin/releases
UAHF (ABC) node: https://github.com/Bitcoin-ABC/bitcoin-abc/releases
BitMain's UAHF BCC statement has been somewhat resolved, but it is not too bad to always have several nodes ready for the worst. This part is optional, so you may proceed with your own judgment. Over the next two weeks, a new history will be unfolded, marking the cryptographic market. Within three months after SegWit activation, a block size hard fork (second leg) is ready. For those who are trading, we recommend that you take flexible action in anticipation of various scenarios.