Bitcoin Core v30.0, the anticipated update to the Bitcoin network, has been officially released and is now available for download by node operators.
According to the release notes shared by Bitcoin Core, this update brings performance improvements and bug fixes. However, many developers and Bitcoin supporters have opposed the OP_RETURN update, which allows users to attach up to 100,000 bytes (100KB) of data instead of the previous 83-byte limit.
What are the main changes in Bitcoin Core v30.0?
One of the major updates to Bitcoin Core is the reduction in default fees. Nodes can relay transactions between peers for as low as 0.1 sat/vB. Meanwhile, miners can include transactions in the next block with a minimum fee of 0.001 sat/vB.
OP_RETURN, let’s Bitcoin users attach data, like Special messages have room to attach more data, from 83 bytes to 100KB. OP_RETURN has multiple outputs instead of Previous single output. Increased data limit let’s Users can use hashes, certificates, and even art Metadata.
Additionally, Bitcoin Core v30.0 no longer supports BDB wallets. Users should move to descriptor wallets, which are more secure and easier to backup. Also wallet commands such as importwallet and dumpwallet. disappeared. Updates too bring TRUC trading, avoid While transactions are in conflict they are waiting For confirmation.
Another new command is bitcoin. This results in how Node operators and miners interact with Bitcoin Core. Alsobitcoin node, bitcoin gui, or bitcoin rpc will replace several older commands. Miners can connect directly to Bitcoin Core and Experimental PC mining interface. the work via local socket, make Block template requests Faster.
Graphical User Interface (GUI) has received multiple updates in the same way. The graphical toolkit has been updated from: Qt5 to Qt6. dark mode For Windows users is now supported on macOS. of Metal graphics are available for smoother performance.
Other updates include fixes for five minor bugs. Details of the bug fix will be published within the next two weeks. Nodes running Bitcoin Core v27.x will no longer receive new updates Since then According to , v27.x is labeled “End of Support.” release notes From Bitcoin Core.
What is the controversy regarding Core v30.0?
The increase in the OP_RETURN data limit from 83 bytes to 100,000 bytes (100KB) received harsh criticism from developers and Bitcoin supporters. As mentioned above, currently OP_RETURN let’s The user also attaches data, I allow it Multiple OP_RETURN outputs in be one transaction.
The Bitcoin Knots community, led by developers Luke Dashjr and Bitcoin Mechanic, opposed the new changes to OP_RETURN.
They argued that increasing data limits could force node operators to host illegal or harmful content, such as explicit content or malicious code. this This can create legal problems for node operators.
The Knots community believes that Bitcoin should be focused on transfers rather than file storage. In contrast, Bitcoin Core developers say their changes only adjust the memory pool (mempool) policy. It does not affect Bitcoin consensus rules.
In September, Bitcoin Core developers planned to remove user control over the OP_RETURN data limit. Node operators would then have been forced to accept higher data limits without the option to reduce them.
After backlash, core maintainer Ava Chow restored user configurations that exceeded data limits just before the October release window. This decision temporarily allayed concerns about mandatory settings. However, this feature may be implemented in future versions.
This update also changes how the -datacarriersize setting works. In older versions, numbers like 83 represented the 83-byte limit. v30 Allowed with the same value 9 times More data. Critics claim this silent change misleads users. v30 for now keep The new 100 KB default is still Let me User manually lowers it.
Will Bitcoin be forked?
In late September, leaked messages suggested that Luke Dashjr may consider a temporary hard fork of Bitcoin to resist changes to the new OP_RETURN data limit.
TheRage claimed that Dashjr is exploring a fork to protect node operators from the possibility of illegal data spreading through the network. However, Dashjr denied the claims, calling the reports “fake news.” He said he has no plans to fork, saying, “There will be no hard fork.” Still, he maintained his opposition to the new rules, accusing only “Core30 advocates” of proposing a fork.
TheRage publication stood by its reporting, noting that neither Dashjr nor his colleagues dispute the authenticity of the leaked messages.
