- Michael Saylor did not take a clear stance on the current disagreement between Bitcoin Core and Knots node operators about the OP_RETURN protocol change.
- The debate centers on whether to increase the OP_RETURN data storage limit, with Bitcoin Core opting for an increase and Knots maintaining a lower limit.
- Saylor referred to the OP_RETURN debate as a “second- or third-order” protocol change, cautioning about potential unintended consequences.
- His comments were criticized by some community members for lacking technical depth or specific knowledge about the actual issues involved.
- Bitcoin Core remains the dominant node software, while Knots continues to limit arbitrary data storage as a form of protest.
Michael Saylor, the founder of the largest bitcoin treasury company, addressed questions about the ongoing dispute between Bitcoin Core and Knots node operators at the Bitcoin Treasuries NYC Unconference. The conflict revolves around a proposed change involving OP_RETURN, a protocol feature that allows data storage in bitcoin transactions.
An audience member asked Saylor about the plan by Bitcoin Core to increase the data storage limit for OP_RETURN to 100,000 bytes in its latest version, while Knots plans to maintain the limit below 90 bytes in its default settings. The question aimed to gather insight from Saylor as the executive chairman of the company holding the most bitcoin on its balance sheet.
Saylor did not directly answer the question. Instead, he commented, “I think protocol proposals, however well intentioned, can go horribly wrong.” He categorized the OP_RETURN limit change as less significant than changes to bitcoin supply or block size, saying, “This is actually a second-order or maybe even a third-order change.”
He added, “The reaction of the community, which is to reject it, an inflammatory reaction, I thought was a healthy response. It’s healthy to be skeptical of a third-order change to the protocol, because it might become a second order change. And if it’s a first-order change, it puts everything at risk.” Some community members viewed his comments as lacking detail about data storage, node operation costs, and the long opposition by Knots towards large-scale data storage unrelated to bitcoin transactions.
Critics, including Paul Sztorc, described Saylor’s answer as a “pro-ossification answer” that demonstrated “no actual knowledge of the issues.” Others on social media called it “one of the most word salad statements I have ever heard.” Saylor also cautioned about well-funded developers making changes with unintended negative effects on the Bitcoin protocol.
The disagreement between Bitcoin Core and Knots has continued for nearly a year. Bitcoin Core, which is used by more than 75% of node operators according to various trackers and statistics, has chosen to allow larger data storage through OP_RETURN, while Knots maintains stricter limits to discourage use for purposes other than bitcoin transfers.
The debate highlights divisions within the Bitcoin community over protocol changes and their potential impact on the network’s future. Saylor’s response left many seeking more technical clarity and leadership on the issue.
✅ Follow BITNEWSBOT on Telegram, Facebook, LinkedIn, X.com, and Google News for instant updates.
Previous Articles:
- Chainlink (LINK) Eyes $100 as Price Rallies 82% in Strong Q3
- Microsoft Boosts AI Data Center Spend in WI to $7B, Eyes Growth
- Ledger Finds Unpatchable Flaw in Tangem Wallet, Brute Force Possible
- First XRP, Dogecoin ETFs Launch in U.S. on Cboe BZX Exchange
- Binance’s BNB Coin Hits $1,000 for First Time, Sets New ATH
