Meanwhile, controversy is on the rise, not least because among those who are taking part there are also some maximalists who are very unwilling to compromise, and generally not at all kind to those who think differently from them. Only once its use is widespread will it be possible to tell whether it has brought disadvantages to LN or not.
It is worth noting that no one can prevent Bitcoin Core developers from releasing a new version with full-opt-in RBF functionality, so it is very likely that the new version 24 will be released as it is now in its release candidate.
#Bitcoin core releases software
On one side there are LN supporters who claim that the new version of Bitcoin Core software will harm Lightning Network, while on the other side there are Bitcoin Core supporters who claim that the new version will not harm LN.įor now, since Bitcoin Core version 24 is not yet in use, there is no clear data to prove beyond doubt which side is right, and so the controversy will likely go on. Hence, the whole issue is still wide open. The controversy over Bitcoin Core’s new software version
#Bitcoin core releases update
The issue is debated, but the point of the question is whether or not adding full-opt-in RBF functionality to Bitcoin Core creates problems for LN transactions.įor example, according to Bitcoin Core developer David Harding, this update would not change the substitutability of transactions significantly. According to Sneidermanis, zero-conf apps like Muun are forced to disable zero-conf functionality, meaning that it even goes so far as to disable outgoing LN payments.
Sneidermanis says that Muun’s theme examined the Bitcoin Core 20 release candidate and found some troubling things specifically about the full-opt-in RBF implementation. The most skeptical is the founder of LN Muun, Dario Sneidermanis. It should be mentioned that such arguments have been there since version 12, but have intensified recently due to the expansion of Lightning Network (LN). According to some, this will harm the network and even facilitate double-spending attacks.
#Bitcoin core releases full
The problem is that in the new version of Bitcoin Core, full RBF logic will be built in that allows for the replacement of transactions that have not yet been confirmed. The scheme, however, works only with zero-confirmation (0-conf) transactions, that is, transactions that can be accepted even before a miner confirms them by placing them in a block.
RBF (Replace by Fee) allows users to replace an unconfirmed transaction with an alternative transaction with a higher fee until it is placed in a block. In the new version, users will be able to choose to have their nodes accept and forward any conflicting transactions if they include a higher fee than the other transactions they conflict with. Until now, Bitcoin Core nodes applied the “first seen” rule, meaning conflicting transactions were simply not accepted into the mempool. However, the controversy concerns the introduction of an additional option that will allow users to apply full replace-by-fee (RBF) logic. There will be some important new features in the new version, such as how nodes download blocks when they synchronize with the network. Version 22.0 is currently available, and the next one is already in the release candidate stage.
0 kommentar(er)
