- Debate over Bitcoin Core v30 intensifies as Knots nodes protest upcoming changes to mempool policy.
- A pro-v30 mining pool consultant discussed, but did not actually carry out, a potential Denial of Service (DoS) attack against Knots nodes.
- Knots opposes Bitcoin Core v30’s plan to increase default limits for OP_RETURN data in the mempool.
- Developers explained that no real attack took place after a mischaracterization spread on social media.
- Knots lead developer Luke Dashjr shared advice for node operators to defend against possible future attacks.
The ongoing disagreement between supporters of Bitcoin Core version 30 and users of Knots software has escalated, with Knots node operators actively protesting proposed mempool policy changes. The current stable Bitcoin Core release is version 29.0, while 30.0 is scheduled for release in October 2025. Knots, a fork of Bitcoin Core, is the primary tool for those objecting to the v30 changes regarding data handling.
Over the weekend, a consultant advising pro-v30 mining pools described a hypothetical Denial of Service (DoS) attack strategy against Knots nodes during an online discussion. The scenario involved identifying Knots node operators using residential internet and repeatedly requesting Initial Block Downloads (IBD) from their nodes. This type of attack can slow down or disrupt node operations by overloading their data connections. Several developers associated with v30 found the hypothetical situation amusing, with some discussing the details publicly on X.
A misinterpretation about the event later gained traction on social media. However, a co-host of the discussion later clarified that no actual DoS attack was performed. The clarification emphasized that the described attack was not real and no Knots nodes reported disruption.
The core of the disagreement is how each software version treats OP_RETURN, a Bitcoin transaction feature that allows attaching data to the blockchain. Bitcoin Core v30 plans to accept larger data sizes—up to 1 megabyte—by default in its mempool, which is the pool of unconfirmed transactions. In contrast, Knots keeps the traditional, much lower limits, only allowing OP_RETURN data to take up about 0.01% of that size. Supporters of v30 argue that the mempool should match the underlying technical protocol, while Knots users caution that relaying more arbitrary data increases burdens for ordinary node operators.
Luke Dashjr, lead developer for Knots, shared a recording of the discussion and offered instructions for protecting nodes from future hypothetical attacks. He recommended that operators using residential internet should limit their daily data uploads to avoid exceeding their internet service provider’s limits.
The public exchange illustrates the ongoing tension between the two camps, with both sides preparing for the formal release of Bitcoin Core v30 later this year. For now, Knots node operators are urged to follow Dashjr’s advice as the debate over mempool filtering and network resilience continues.
✅ Follow BITNEWSBOT on Telegram, Facebook, LinkedIn, X.com, and Google News for instant updates.
Previous Articles:
- Football Dot Fun Surges: $25.7M Volume, 10K+ Users in Two Weeks
- Ripple’s XRP Slides 2%: Can It Deliver 5x Returns for Investors?
- Bitcoin Plunges $4,000 in Flash Crash as Whale Dumps 24,000 BTC
- Trader Launches $2M Pressure Campaign Over MEXC’s $3M Account Freeze
- SBI Group, Chainlink Partner as Japan Eyes 20% Crypto Tax, ETFs
