I agree there is no way to completely prevent data we don't like, but segwit and taproot have enabled the inscriptions' abuse like hand in glove. In two ways:
1) inscriptions benefit from the segwit fee discount so they pay less fees for the same amount of bytes than other types of transactions and
2) having a limited OP_RETURN size and a limited amount of data per transaction on segwit means that inscriptions would have to be split among several transactions, therefore increasing the fees they have to pay for the same amount of data.
Without the segwit discount and without taproot the same inscriptions would be paying several times the fees they are paying right now.
I don't care that there might be "near universal agreement from devs", like there was near universal agreement from "experts" during the "pandemic". That is an appeal to authority. Devs aren't gods and they don't represent bitcoiners.
Limiting data on witnesses makes no sense and would break many use cases of bitcoin including those that are “purely monetary”. I’m not appealing to authority as an opt out. I’m making the point that
(a) this is not as simple as “just get rid of things I don’t like” and
(b) you would need someone to implement the type of limit you describe and if everyone that could says that’s a bad/dangerous idea, that’s a problem.
The difference about the pandemic is that experts that disagreed were silenced so it wasn’t universal agreement.
Lift the cap on OP_RETURN and no more witness discount. If it’s not just about the discount then you’re really just asking to censor data you don’t like.
By the way, do you know why there’s a witness discount?
One reason was to encourage migration to segwit. That was desirable. It came with tradeoffs but probably still worth it.
Second reason is because the witness doesn’t need to be persisted by all nodes. So this is actually better for those that don’t want to persist inscription data on their node.
I wonder what would happen if the nodes stopped saving and verifying the segwit transaction signatures. Can those UTXOs be spent by anyone? I still haven’t found a convincing answer to that question. But that’s another story.
Utxos haven’t been spent yet so they haven’t been signed. You can verify by verifying all of the blocks.
Thread collapsed
Thread collapsed
Thread collapsed
I would be pleased if the segwit discount was removed. About the OP_RETURN cap, I’d rather keep it unless there is a justification for increasing (not removing) it. You mentioned the “expresiveness”. I definitely don’t want to censor data, but I believe that transactions should be as concise as possible rather than expressive/verbose. The bitcoin blockchain is, first and foremost, an accounting ledger, not a blank canvas to paint or write novels. I am OK with short strings of text, such as the Times’ headline in the genesis block or the miners writing their name on the blocks they mine. It’s not about the contents, but about the length/size.
At some point what is concise will become a subjective value. The way we make that objective is by scarce block size and the free market. Costs encourage users to be as concise as possible.
Yes and no. The protocol is opinionated: whether to keep, alter or remove OP_RETURN, the segwit discount, and so on alter the conditions of the “free market”, i.e. the playing field that the protocol enables. Even the block size limit is opinionated. For example, with an unlimited OP_RETURN, it would be cheaper to make an inscription using it, because you wouldn’t have to split it among several transactions.
Great point. What you’re describing is a change to the protocol, which by definition would not be how it works today. But yes, removing OP_RETURN limits (which I believe is just policy anyway) and the segwit discount would make the market more free. Discriminating against data (a la current segwit discount and OP_RETURN limits does) is would not.
Thread collapsed
Thread collapsed
Thread collapsed
Thread collapsed
Thread collapsed