The debate surrounding BIP-110, Bitcoin Ordinals, inscriptions, and arbitrary blockchain data is becoming increasingly philosophical. BIP-110 proposes a temporary consensus-level soft fork that would restrict several methods of embedding large amounts of data into Bitcoin transactions. The proposal specifically argues that Bitcoin should remain focused on its primary purpose as permissionless money rather than becoming a general-purpose data-storage network.
I understand that argument, but I am not convinced Bitcoin needs to care so much about what users interpret a transaction to represent.
Consider a simple example. Someone sends another person $100 worth of Bitcoin. From the recipient’s perspective, what matters is that the transaction is valid, the sender controlled the inputs, the BTC was not double-spent, the outputs are mathematically correct, and the transaction was accepted into the Bitcoin blockchain.
Whether some external protocol describes one of those satoshis as an Ordinal, inscription, token, collectible, or something else entirely does not fundamentally change the bitcoin being transferred.
Bitcoin does not maintain separate categories such as “Ordinal Bitcoin” and “regular Bitcoin.” At the consensus level, Bitcoin nodes validate transactions, scripts, signatures, inputs, outputs, and UTXOs. Ordinals and similar systems add an additional layer of interpretation on top of that same blockchain.
The Difference Between Bitcoin and the Protocol Built on Top
This distinction is important.
A Bitcoin wallet may simply see:
Input → Bitcoin transaction → Output → Spendable BTC
Meanwhile, specialized Ordinals software may examine the exact same blockchain information and interpret particular satoshis or witness data differently.
That does not necessarily mean Bitcoin itself needs to understand or endorse that interpretation.
In other words, Bitcoin can process the transaction without knowing whether humans believe some bytes represent:
- an image,
- an inscription,
- a token,
- a financial contract,
- encrypted information,
- or nothing meaningful at all.
That is why I tend to favor a relatively simple principle:
If a Bitcoin transaction satisfies the network’s consensus rules and pays for the block space it consumes, Bitcoin should generally be concerned with whether the transaction is valid—not with deciding what the transaction is “supposed” to mean.
The Strongest Argument for BIP-110
There is, however, a legitimate technical argument on the other side.
Bitcoin block space is finite.
Every transaction included in the blockchain consumes bandwidth, disk space, validation resources, and ultimately some amount of infrastructure operated by Bitcoin nodes around the world. BIP-110’s authors argue that large arbitrary-data storage creates unnecessary external costs for node operators and competes with Bitcoin’s monetary transactions for scarce block space.
BIP-110 therefore proposes limits including a 256-byte ceiling on certain data pushes and witness items, restrictions on some Taproot structures, and an 83-byte allowance for OP_RETURN outputs. The proposed soft fork is explicitly temporary, lasting approximately one year if activated.
That reasoning should not simply be dismissed.
If storing large files on Bitcoin eventually makes running a full node significantly more expensive, proponents can reasonably argue that the consequences affect everyone—even people who have no interest in Ordinals.
There is also a legitimate question about whether Bitcoin should be optimized primarily for monetary settlement rather than becoming an expensive decentralized file-storage system.
Where I Disagree With BIP-110
My concern is where Bitcoin moves from resource management into interpreting acceptable use.
There is a major difference between saying:
“My node does not want to relay this transaction.”
and saying:
“Bitcoin consensus should make a block containing this transaction invalid.”
Relay policy gives individual node operators discretion.
Consensus rules determine what Bitcoin itself considers valid.
That distinction matters because Bitcoin Core has historically had configurable transaction-relay policies. Bitcoin Core 30, for example, increased the default -datacarriersize setting to effectively remove the previous restrictive OP_RETURN policy limit while continuing to allow node operators to configure their own limits. It also permitted multiple data-carrier outputs subject to the aggregate configured limit.
BIP-110 goes much further by proposing consensus-level restrictions.
Once Bitcoin consensus begins distinguishing between desirable and undesirable structures based partly on their perceived use, the debate becomes less about whether a transaction is technically valid and more about what Bitcoin ought to be used for.
That is where I become skeptical.
A JPEG Does Not Change the Bitcoin
Suppose someone sends me $100 in BTC from an output that Ordinals software associates with an inscription.
Unless I specifically participate in the Ordinals ecosystem, that additional interpretation may be completely irrelevant to me.
My Bitcoin wallet sees spendable bitcoin.
The blockchain sees transaction inputs and outputs.
Ordinals software may see something additional.
Those three observations can coexist.
The Bitcoin network does not necessarily need to settle which interpretation is philosophically correct.
This is one of the characteristics that makes Bitcoin powerful: different applications can derive additional meaning from the same neutral settlement layer without requiring Bitcoin consensus itself to understand every application.
Block Space Already Has a Price
There is also an economic argument against aggressively policing transaction purpose.
Bitcoin already has a mechanism for allocating scarce block space:
transaction fees.
When demand increases, fees generally increase. Users who value confirmation more highly can offer higher fees, while miners choose transactions based largely on economic incentives and their own policies.
From that perspective, an inscription transaction paying the appropriate market fee is purchasing block space just like another transaction.
Critics can reasonably respond that fees do not eliminate every externality, particularly long-term storage and node-operation costs. That is true.
But it raises an important question:
Should Bitcoin solve those externalities with neutral technical limits, or should consensus attempt to distinguish monetary activity from non-monetary activity?
I strongly prefer the first approach whenever technically possible.
BIP-110 Raises a Bigger Question Than Ordinals
Ultimately, the most important BIP-110 debate is not really about JPEGs.
It is about what Bitcoin consensus should be responsible for deciding.
Supporters of BIP-110 see arbitrary-data restrictions as protecting Bitcoin’s decentralization, affordability, and identity as a monetary network.
Opponents can reasonably view the same restrictions as unnecessary consensus intervention into transactions that would otherwise satisfy Bitcoin’s technical rules and pay their required fees.
Both arguments involve legitimate concerns.
My position is simply that Bitcoin should remain as neutral as practical.
If someone sends me $100 worth of valid Bitcoin, I generally do not care whether another piece of software calls one of those satoshis an Ordinal, a Rune, an inscription, or something else.
The BTC still moved.
Bitcoin should verify the transaction.
Miners should compete for fees.
Node operators should retain meaningful control over their own relay policies.
And whenever possible, the base protocol should avoid becoming an arbiter of what people are allowed to mean when they use it.
That may ultimately be the more important principle to protect.
BitcoinVersus.Tech Editor’s Note:
We volunteer daily to ensure the credibility of the information on this platform is Verifiably True. If you would like to support to help further secure the integrity of our research initiatives, please donate here: 3C9o19EH5HSiwEPyCTmEKzxhNCbo2X6TTb
BitcoinVersus.tech is not a financial advisor. This media platform reports on financial subjects purely for informational purposes.v
Bitcoin Versus 
Leave a comment