{"id":1390,"date":"2025-05-13T10:12:10","date_gmt":"2025-05-13T10:12:10","guid":{"rendered":"https:\/\/nownodes.io\/blog\/?p=1390"},"modified":"2025-05-13T10:12:10","modified_gmt":"2025-05-13T10:12:10","slug":"bitcoin-update-why-bitcoin-core-v28-0-is-a-crucial-update","status":"publish","type":"post","link":"https:\/\/nownodes.io\/blog\/bitcoin-update-why-bitcoin-core-v28-0-is-a-crucial-update\/","title":{"rendered":"Bitcoin Update: Why Bitcoin Core v28.0 is a Crucial Update"},"content":{"rendered":"\n

Bitcoin and Bitcoin Core are two key components of the blockchain ecosystem. Bitcoin is the first and most popular cryptocurrency, facilitating decentralized value exchange through its network. On the other hand, Bitcoin Core is the primary software that nodes use to verify transactions and maintain the security and stability of the network. Recently, we successfully upgraded our nodes to the latest version of Bitcoin Core v28.0<\/strong>. In this article, we’ll explore the key changes brought by this Bitcoin update.<\/p>\n\n\n

Bitcoin update: A New Approach to Port Management<\/h3>\n\n\n

Previously, Bitcoin Core automatically opened ports using UPnP. In v28.0, that option has been removed. Instead, it now uses -natpmp<\/code> \u2014 a more modern and secure protocol for managing ports via PCP or NAT-PMP. This change not only reduces security risks but also makes network configuration more flexible and predictable.<\/p>\n\n\n\n

Additionally, the logic for Tor port assignment has changed. Now, the Tor port is calculated as the main port + 1. For instance, if your node is using -port=5555<\/code>, Tor will listen on 5556<\/code>. This adjustment helps avoid port conflicts when running multiple nodes and simplifies configuration for multi-node networks.<\/p>\n\n\n

Mempool and Mining: Ephemeral Dust and Block Weight Control<\/h3>\n\n\n

This Bitcoin update introduces a new concept called ephemeral dust, allowing users to make zero-fee transactions as long as they spend the outputs immediately. This mechanism can be useful for fee savings in internal transactions or testing new features.<\/p>\n\n\n\n

Additionally, the update fixes a bug related to block space reservation. Previously, the system counted the reserved space for service data twice, which limited the block size to 3,992,000 WU. Now, users can flexibly manage this parameter through -blockreservedweight<\/code>, allowing up to 4,000,000 WU per block.<\/p>\n\n\n

API and RPC Updates: More Data for Analysis<\/h3>\n\n\n

In the updated RPC API, new data fields have been introduced:<\/p>\n\n\n\n