Bitcoin Ordinals community debates fix after inscription validation bug
A few solutions are being discussed to fix a code bug found in the Bitcoin (BTC)-native Ordinals protocol which has prevented over 1,200 inscriptions from being validated.
While nearly every member of the Ordinals community agrees that these inscription requests should be reincluded, the community is debating whether they should be added retroactively or not.
The bug came from the indexer function of the protocol only counting inscriptions that were in the first input of a transaction submitted up to and including version 0.5.1 of the protocol.
One prominent Ordinals member known on Twitter as “Leonidas.og” summarized the pros and cons of each solution in an April 10 tweet, coming a few days after the issue was first made public on April 5 by the GitHub user “veryordinally.”
A bug was found in the ordinals protocol that caused ~1,200 inscriptions that should have been valid to not get included. The first of these "orphan" inscriptions happened just before inscription number 420,285. The bug was caused by the ordinals protocol only counting…
The first solution involves selecting a block height to retroactively index the so-called “orphan” inscriptions from inscription number 420,285 onwards, which is roughly where the first orphan inscription was identified.
“This feels like the ‘purist’ solution because it means the ordinals protocol would correctly match the logical ordering on-chain,” Leonidas.og explained, despite acknowledging that the reshuffling “may cause other complications.”
We currently have 1206 “hidden” inscriptions that are not indexed due to https://t.co/VZHCNaBmw0 - join the discussion on GitHub on this interesting consensus and decentralized protocol evolution issue
The alternative is to not change inscription
Read more on cointelegraph.com
