[vc_row full_width=”stretch_row” css=”.vc_custom_1531732107238{background-color: #fcc118 !important;}”][vc_column]

[/vc_column][/vc_row][vc_row css=”.vc_custom_1531730959461{border-bottom-width: 1px !important;background-color: #f9fafb !important;border-bottom-color: #eef3f7 !important;border-bottom-style: solid !important;}”][vc_column css=”.vc_custom_1531891416301{margin-bottom: 0px !important;}”][bsfp-cryptocurrency style=”widget-6″ align=”auto” columns=”2″ scheme=”light” coins=”top-x-coins” coins-count=”8″ coins-selected=”” currency=”USD” title=”Cryptocurrencies” show_title=”0″ icon=”” heading_color=”” heading_style=”default” bs-show-desktop=”1″ bs-show-tablet=”1″ bs-show-phone=”1″ css=”.vc_custom_1531730265600{margin-bottom: 0px !important;}” custom-css-class=”” custom-id=””][/vc_column][/vc_row]

Bitcoin Core 24, Bitcoin’s controversial upgrade is now live


Bitcoin Core 24, the long-awaited but controversial upgrade was activated on Nov. 26, opening the door for the Bitcoin memory pool that will serve as a waiting room for unconfirmed transactions.  

The memory pool will activate full RBF (Replace-by-Fee) logic, which is a way for nodes to either accept or refuse conflicting transactions if one transaction has a high fee. 

Before this upgrade, Bitcoin Core nodes implemented the “opt-in RBF” logic, where miners replaced a conflicting transaction in the memory pool if that transaction was signaled as replaceable. The RBF standard was introduced in 2016 and activated on the Bitcoin Network through the BIP 125 update. Prior to RBF, the memory pool accepted transactions on a first-seen basis.

Meanwhile, the new release features a Full-RBF, which the Bitcoin community has debated as controversial due to fears of making zero-confirmation transactions obsolete. Besides, the majority of critics feel the new feature will encourage double-spend attacks, and cause zero confirmation applications such as Muun to disable the feature for thousands of users.

According to Appolo’s co-founder, Thomas Fahrer, introducing the Full RBF to Bitcoin makes zero-confirmation transactions riskier because it increases the chances of facing double-spend attacks when accepting such payments.

Zero confirmation loosely translates to the blockchain accepting a Bitcoin transaction before validation by miners. In most cases, these transactions are not only safe but also useful. The upgrade negatively impacts these types of transactions since miners will now easily replace them for higher fee transactions.

Muun wallet, for example, packages unconfirmed transactions into blocks to create submarine swaps, thus enabling bulk lightning payments. 

The goal of the full Replace by Fee mechanism is to increase transaction fees. This will not only benefit miners but set an industry standard for the blockchain’s fee market. Merchants and Bitcoin ATMs relying on zero-confirmation transactions to meet customer needs in online commerce feel the RBF will make their businesses less reliable — causing part of the community to speculate that core developers are trying to make all transactions RBF by default.

According to Synonym CEO John Carvalho, “RBF was only going to make spending BTC more dangerous for retailers and businesses” 

When asked to provide proof of RBF double-spending, Carvalho cited zero confirmation transactions provided incentives to protect the network from a potential Sybil attack. Nearly the whole community voted NO to his argument, with most members detailing zero-confirmation transactions were unsafe, and were only profitable to merchants for a limited time.

Leave A Reply

Your email address will not be published.