Bitcoin Core, the user’s most used to operate full nodes on the Bitcoin Network (BTC) and independently validate transactions, has presented the latest updates.
It was released on April 15th with a new version of 29.0. Among other changes, we introduce changes aimed at optimizing communication between nodes, transaction policies and tools for developers looking to enhance system robustness and accessibility.
Changes to Mempool and Mining Policy
Bitcoin Core 29.0 introduces rules adjustments that regulate Mempool, the space where transactions are expected to be included in blocks by miners, with the aim of optimizing both user experience and Bitcoin mining operations. These changes, if implemented as expected, can balance the efficiency of transaction selection with system safety.
One notable improvement is support for version 3 transactions known as TRUC (topologically restricted transactions) as defined in the Bitcoin 431 Improvement Proposal (BIP-431). In the context of BTC, the TRUC transaction is Limit the network until it is confirmed.
Unlike standard transactions, TRUC contains certain restrictions to avoid abuse that can congested Mempool, such as sending excessively large transactions.
Bitcoin Core Version 29.0 Establish a limit on 10,000 VB size (Virtual bytes measure the impact of network transactions according to their size and complexity, and prohibiting out-of-out exit spending on long-dependent transactions. This makes TRUC transactions easier to manage, reduces the risk of Mempool saturation, and encourages transaction selection at competitive rates.
Similarly, it is proposed to improve the management of transaction packages in which the main transaction (father) and its dependents (daughter) are jointly evaluated. Version 29.0 allows you to accept low-cost transactions when accompanied by high-rate daughter transactions. Facilitate stack transaction verification Through the CPFP mechanism (“son pays for the father”). This approach would benefit users who want to accelerate their transactions without changing all fees.
According to Peter Todd, the battle won with a new version of Bitcoin Core
Starting with version 28.0, a full RBF policy (a full rate replacement) has been activated by default. This allows you to accept transactions that replace other transactions with lower rates, as explained by Cryptonoticia, without the explicit signal of exchangeability. If it complies with exchange rulesproviding a higher total rate, etc.
With the practice being generalized, the Bitcoin Core team decided that deactivating it would no longer benefit and would eliminate the option. -mempoolfullrbf Establish a complete RBF as standard behavior.
As developer Peter Todd emphasized, “The fight for the full RBF is over,” reflects the wider consensus of the Bitcoin community regarding the use of RBF.
For miners, this can do so Facilitate transaction prioritization at higher ratesIt may increase your income, but requires technical knowledge to avoid errors that disable blocks, such as including transactions that are incompatible with network rules.
Users can benefit more Flexibility to adjust rates and accelerate your confirmationespecially at the moment of traffic jams. However, if this standardization is integrated, there is a risk of unexpected exchanges, which could create challenges for services that rely on UN confirmed transactions, such as shops that accept payments without waiting for confirmation.
Combined with new TRUC transactions and optimized package management, this policy can amplify the ability of network participants to adapt to dynamic conditions, if implemented successfully.
P2P communication and network changes
A central aspect of the Bitcoin Core 29.0 update is optimization of the P2P protocol (pair communication protocol) and how to adjust the nodes of Bitcoin Red Exchange information such as blocks and transactions. Among the proposed changes, router Accept incoming connections.
Instead, the use of PCP (port control protocol for acronyms in English) and NAT-PMP (port mapping protocol for network address translation). These new protocols are compatible with IPv4 (Internet Protocol Version 4) and IPv6 (Internet Protocol Version 6). Two main criteria for assigning addresses on the Internet. IPv4 uses 32-bit addresses, such as 192.168.1.1, but with limited capacity, IPv6 uses 128-bit addresses designed to support far more connected devices.
PCP and NAT-PMP can be allowed if they are implemented correctly Nodes open more efficient and secure portswhich increases domestic and business network connectivity.
Another related adjustment affects nodes operating through TOR (“The Onion Router”), a communications network overlaid on the Internet, designed to provide anonymity and privacy to users. Tor uses a technique called “onion routing.” (Onion Routing)) for Hide user identity and location When passing data to multiple encrypted nodes. In previous versions, nodes that use the same ports as the standard connections by TOR can generate technical conflicts.
Here, Bitcoin Core 29.0 proposes to automatically configure another port for connections. onion (Onion), a term that refers to a specific direction in the TOR, designed to work on this anonymous network.
For example, if the node uses port 8333, which is commonly assigned to a regular Bitcoin connection, then the port for the connection is onion It will be 8334. This change is possible Simplify management of anonymous nodes,TOR users should update their configuration to avoid interruptions.
Additionally, it has been proposed to optimize the handling of orphan blocks received by nodes without knowing about the predecessor blocks in the chain. Instead of throwing them away immediately, a new version You can save them temporarily and request missing blocks from other nodes.
This mechanism potentially reduces delays in blockchain synchronization and enhances the network’s resilience to problems that seek to slow unstable connections and information propagation.
If expected, modifications to the P2P system could enhance the decentralization of Bitcoin in TOR use and optimization of orphan blocks. Ensures that the node remains connected..
For beginner users, this means a more stable network. Advanced offers greater flexibility in configuring nodes.
Updates on the RPC interface
RPC (call to remote procedure) is a command that developers use to interact with Bitcoin Core Nodes. Version 29.0 proposes improvements that allow for these more practical and secure interfaces.
The surprising change is the inclusion of new fields in the command getMempoolinfoprovides detailed statistics About Mempool’s trading scale and rates. For example, developers can access data about the number of TRUC transactions or the impact of fee exchange policies. This information is valuable to those who develop applications that require real data, such as digital wallets and block explorers.
Another adjustment affects the command sendrawtransaction (Send RAW Transactions). This allows you to send customized transactions directly to the network. This command, which developers use to send manually built transactions, improves the ability to process transaction packages and simplifies complex operational management with multiple parts.
Additionally, the following command errors artspent (List of undisconnected outputs), which provides more accurate information about the output available in the wallet.
These updates are possible Promotes developer workallowing you to create more robust tools. For beginner users, this will give you a more reliable application. For the advanced ones, it means having stronger control over integration with the network.
Other related changes
In addition to these major changes, Bitcoin Core 29.0 includes other improvements. In the purse area, support and recovery features are optimized. Promoting private key management.
The error has also been fixed in Bitcoin QT, Graphics Interface (GUI). Improve your user experience It lets the node work through it. From a safety standpoint, incoming data has been verified, reducing the risk of malicious attacks.
Finally, translations and documentation have been updated to make the software more accessible to users around the world. These changes do not directly change the behavior of the network, but contribute to a more fluid and reliable experience.
(tagstotranslate)bitcoin(btc)
