Bitcoin Core developers did not agree to include SegWit2x code in their protocol
The Bitcoin Core team (the official Bitcoin client) did not agree to include the SegWit2x code in the current protocol of the system. According to representatives of the “official” cue ball, the work on creating the SegWit2x was carried out without due attention to details, so it is not currently possible to use this technology.
The main point criticized by the Bitcoin Core team is the refusal of SegWit2x developers to include protection against replay attacks in the protocol code. This problem is really important for cryptocurrencies. In particular, for bitcoin, since this coin is at the top of its popularity, and its rate breaks all records, despite the fact that from time to time the price of the cue ball against the dollar still decreases.
Earlier, the SegWit2x team planned hard fork starting from block 494784. It was reported that the code would be incompatible with the current versions of Bitcoin Core and UASF. Failure to turn on the security system mentioned above means that attacks on the authentication system by recording and subsequently playing back previously sent correct messages on transactions or parts of such messages are not excluded. As a result, an attacker can use the victim’s funds by conducting a transaction with an identical recipient and the amount sent, but in a different registry.
In Bitcoin Cash, a fork of the main bitcoin, the problem with the re-attack was solvedrelatively simple. Here, when conducting a transaction, a special identifier is used that allows the system to understand that the transaction is in the Bitcoin Cash registry, and not elsewhere. So the nodes that work with the “official” cue ball will not allow the Bitcoin Cash transaction. This is the protection against repeated playback. But Bitcoin Core does not have such protection, and SegWit2x developers believe that the coin team itself should solve its problems.
In principle, it is very likely that among the developers of two teams - Bitcoin Core and Segwit2x a conflict is brewing. Some do not agree to include a new protocol in their infrastructure, others refuse to solve the problems of this infrastructure with its protection. As a result, not those and not others suffer, but system users.
The other day on the Github Bitcoin Core pageThere was a request to include SegWit2x in the original protocol of the official cryptocurrency. This was planned to be done in order to make both versions compatible. SegWit2x planned to conduct a hard fork on block 494784. Representatives of SegWit2x believe that the new software version 1.14.5 is not alpha and not beta, but release, it can be worked with without problems .
Now, Segwit2x developers accuse the Bitcoin Core team of not fulfilling the agreement signed in May by participants in a meeting in New York. These allegations are received quite regularly, despite the fact that there are simply no signatures of representatives of the Bitcoin Core group under the general agreement. The agreement (more precisely, the agreement, there were two of them) envisaged an increase in the size of the block to 2 MB.
In general, the outcome, in which three separate registries appear immediately in the Bitcoin infrastructure, is becoming more and more likely. We are talking about the emergence of the SegWit2x registry, protected from reuse attacks and the continued existence and operation of the original registry. To all this we do not forget about Bitcoin Cash(whose course has grown, and very significantly), right? If you do not take measures, then the separation, which will undoubtedly turn into temporary problems of the cryptocurrency infrastructure (both main and forks), will occur in November.
The situation so far is becoming more and more confused, and it is unlikely that conflicts between cryptocurrency infrastructure developers can lead to something good. Here, either they agree on cooperation and work together, or the infrastructure will split. Maybe this will not be very scary, but why do we all need extra problems? Bitcoin was only just beginning to be recognized and used by government agencies in various countries, when confusion and vacillation began in the main camp. I would like to hope that all differences will be resolved in the near future.
The main point criticized by the Bitcoin Core team is the refusal of SegWit2x developers to include protection against replay attacks in the protocol code. This problem is really important for cryptocurrencies. In particular, for bitcoin, since this coin is at the top of its popularity, and its rate breaks all records, despite the fact that from time to time the price of the cue ball against the dollar still decreases.
Earlier, the SegWit2x team planned hard fork starting from block 494784. It was reported that the code would be incompatible with the current versions of Bitcoin Core and UASF. Failure to turn on the security system mentioned above means that attacks on the authentication system by recording and subsequently playing back previously sent correct messages on transactions or parts of such messages are not excluded. As a result, an attacker can use the victim’s funds by conducting a transaction with an identical recipient and the amount sent, but in a different registry.
In Bitcoin Cash, a fork of the main bitcoin, the problem with the re-attack was solvedrelatively simple. Here, when conducting a transaction, a special identifier is used that allows the system to understand that the transaction is in the Bitcoin Cash registry, and not elsewhere. So the nodes that work with the “official” cue ball will not allow the Bitcoin Cash transaction. This is the protection against repeated playback. But Bitcoin Core does not have such protection, and SegWit2x developers believe that the coin team itself should solve its problems.
In principle, it is very likely that among the developers of two teams - Bitcoin Core and Segwit2x a conflict is brewing. Some do not agree to include a new protocol in their infrastructure, others refuse to solve the problems of this infrastructure with its protection. As a result, not those and not others suffer, but system users.
The other day on the Github Bitcoin Core pageThere was a request to include SegWit2x in the original protocol of the official cryptocurrency. This was planned to be done in order to make both versions compatible. SegWit2x planned to conduct a hard fork on block 494784. Representatives of SegWit2x believe that the new software version 1.14.5 is not alpha and not beta, but release, it can be worked with without problems .
Now, Segwit2x developers accuse the Bitcoin Core team of not fulfilling the agreement signed in May by participants in a meeting in New York. These allegations are received quite regularly, despite the fact that there are simply no signatures of representatives of the Bitcoin Core group under the general agreement. The agreement (more precisely, the agreement, there were two of them) envisaged an increase in the size of the block to 2 MB.
In general, the outcome, in which three separate registries appear immediately in the Bitcoin infrastructure, is becoming more and more likely. We are talking about the emergence of the SegWit2x registry, protected from reuse attacks and the continued existence and operation of the original registry. To all this we do not forget about Bitcoin Cash(whose course has grown, and very significantly), right? If you do not take measures, then the separation, which will undoubtedly turn into temporary problems of the cryptocurrency infrastructure (both main and forks), will occur in November.
The situation so far is becoming more and more confused, and it is unlikely that conflicts between cryptocurrency infrastructure developers can lead to something good. Here, either they agree on cooperation and work together, or the infrastructure will split. Maybe this will not be very scary, but why do we all need extra problems? Bitcoin was only just beginning to be recognized and used by government agencies in various countries, when confusion and vacillation began in the main camp. I would like to hope that all differences will be resolved in the near future.