Original | Odaily Planet Daily
Author | Nan Zhi
Bitcoin Core Developers Want to Eliminate Inscription?
At 9 a.m. this morning, Bitcoin Core developer Luke Dashjr posted on X platform stating: "Inscription is using a vulnerability in the Bitcoin Core client to send garbage information to the blockchain. Since 2013, Bitcoin Core has allowed users to set an additional data size limit ('-datacarriersize') when relaying or mining transactions. By blurring its data into program code, Inscription bypasses this limit. This vulnerability was recently fixed in Bitcoin Knots V25.1. Due to severe disruptions to my workflow at the end of last year (V24 was completely skipped), the fix took longer than usual. In the upcoming V26 release, Bitcoin Core still has the vulnerability. I can only hope it will be finally fixed before V27 next year."
It is not difficult to see that in Luke's eyes, Inscription, which has been wildly popular recently, is essentially a bug. Regarding Luke's remarks and judgments, the following key points are worth noting:
What changes will occur after the fix for Ordinals?
Luke: Ordinals and BRC-20 will no longer exist. By setting the data carrier size to zero.
What is '-datacarriersize'?
In Bitcoin transactions, OP_RETURN is a script opcode that allows attaching some data to the transaction. '-datacarriersize' allows setting the upper limit of the payload size for the OP_RETURN opcode. By default, the data carrier size limit for Bitcoin Core nodes is 80 bytes. By using '-datacarriersize', this limit can be changed to allow larger payloads. Luke Dashjr sees this as a bug that needs to be fixed.
Does Bitcoin Core v27 have a specific release date?
There is no specific date, so even if a decision is made to make changes, it will not happen in the near future.
What impact does it have on regular Bitcoin holders?
Luke: It affects the efficiency and integrity of the blockchain, indirectly impacting security and value.
Which other protocols will be affected?
According to Bitcoin ecosystem developer @wooooer, after Luke's code research in knots, some key details were discovered. In knots, Luke set two main parameter restrictions for filtering so-called Bitcoin fraudulent transactions:
The parameter 'datacarriersize' mainly limits the size of the data carried by OP_RETURN, i.e., those that write data in the output part of UTXO. If this restriction is enabled, the affected protocols will include: Colored coins, OmniLayer, Runes, etc.
The parameter 'maxscriptsize' limits the Inscription protocol based on TaprootScript, with its data engraved in the witness field of UTXO. If this restriction takes effect, the affected protocols will include Ordinals, BRC-20, etc.
wooooer further stated that if Luke's opinion is ultimately implemented, the default limit values of these two parameters may result in only Taproot Asset and RGB remaining in the Bitcoin ecosystem with the smallest on-chain footprint.
Community Opinion: Opposition is Invalid, Support for Ecological Diversity
Bitcoin is not developer-led
Shen Yu: Bitcoin is not Ethereum. What developers say doesn't count. Upgrades require miner voting. If there is opposition, the upgrade cannot proceed unless a fork occurs. (Note: F2Pool ranks third in Bitcoin computing power, with Foundry USA ranking first and AntPool ranking second.)
In response to a user's comment "But most miners will choose to record Inscription transactions because it makes more economic sense," Luke himself believes: "The operating assumption of Bitcoin is that most miners are honest and not malicious. Your ideology of pursuing short-term profits is just another ideology, and a bad one at that," indicating that miners may not accept this transaction because Inscription is considered malicious behavior.
There is a three-party game, but a fork has never truly overturned Bitcoin
BV DAO founder Chen Mo: Bitcoin Core developers believe Inscription is a bug, and fixing it in the next version means BRC-20 will disappear. Inscription stakeholders believe that what developers say doesn't count, and if necessary, miners will fork. In fact, it's all about whose position prevails. In the world of Bitcoin, miners, developers, and capital balance each other, and it's hard to say who truly has the power of speech. There have been many forks in Bitcoin's history, and many have received miner support, but in reality, BTC has always remained singular. Inscription ecology miners are indeed significant beneficiaries, so it is highly likely that they hope Inscription will continue to exist. However, whether capital is truly willing to foot the bill for Inscription is another matter. From another perspective, can the Inscription army really create a thriving Bitcoin fork?
Taproot has brought vitality to the Bitcoin ecosystem
SlowMist Cosine: Personally, I don't think it's necessary to patch this. The impact brought about by accidentally opening this Pandora's box due to the introduction of Taproot (a good thing) is not just a bunch of spam, but also the vitality of the Bitcoin ecosystem. This ecosystem is not just about Ordinals/Inscription.
In summary, the main voice in the community still sees the Bitcoin ecosystem in a positive light, believing that Ordinals have opened up a new path for development and will continue to evolve under the joint drive of multiple interests.
Conclusion
In fact, since the birth of Ordinals, FUD has never stopped. PoW inventor Adam Back urged attacks on Ordinals in February; Luke stated in May that Ordinals are worthless; JAN3 CEO Samson Mow stated that the latest hype surrounding Bitcoin Ordinals and BRC-20 tokens is unsustainable and will disappear in a few months.
The development of the Bitcoin ecosystem is not a one-size-fits-all solution and requires multi-party efforts. However, history always spirals upward. These FUDs have never stopped the progress of Ordinals, but have further prospered, evolved into multiple protocols, and expanded to multiple chains. The spring of the Bitcoin ecosystem will continue.
免责声明:本文章仅代表作者个人观点,不代表本平台的立场和观点。本文章仅供信息分享,不构成对任何人的任何投资建议。用户与作者之间的任何争议,与本平台无关。如网页中刊载的文章或图片涉及侵权,请提供相关的权利证明和身份证明发送邮件到support@aicoin.com,本平台相关工作人员将会进行核查。