The OP_Return size drama started because Citrea needs higher limits to inscribe ZK proofs for their layer 2

They can inscribe that extra data in other ways which require more resources from node operators, or they can bypass the node policies entirely by paying miners.

It’s reasonable to remove the limit, since it can’t prevent larger data inscriptions. If anything, it keeps the Bitcoin network honest and predictable.

But the Ocean miners/Knots node runners are the perfect example of why Bitcoin most likely won’t scale and become fungible.

Instead of addressing the issue for what it is, they talk about filtering dick pics and other kinds of undesirable jpegs.

Make no mistake: Citrea is building a financial layer for bitcoin, so it can be used as money in ways that the Bitcoin chain currently does not enable.

Ironically, the filterooors pretend that they’re saving Bitcoin’s use case as money.

You can’t make this shit up 😂

Reply to this note

Please Login to reply.

Discussion

Okay, or framed correctly, you can run a limitless OP_RETURN, others can run a limited one and the market will decide who has a better node policy. This has never been about imposing knots on everyone. It has been about imposing an unconfigurable mempool policy. This has nothing to do with current projects or their implications on fee markets.

I don't understand why this is being misconstrued so much. People have their own wants, and more configurability is the best way forward not less.

Speaking like an edgelord doesn't make your point any better.

Is it true that if citrea puts these proofs in witness data instead of op_return it will reduce tx cost? If so, why would they put it in op_return?

Because it’s less resource intensive for node runners.

Citrea will choose to make their system more expensive for its users just to help out the node runners?

And even if they did, isn’t citrea open source? I assume it wouldn’t be difficult to fork to a version that uses witness data to reduce costs. Will the market choose to pay the higher fees as a charity to node runners?

You can fork it, but you need people to work on it and build for it.

It seems likely some competitor will offer the version with lower fees. Then the market will decide if the cost is worth it to help out the node runners.

You say it’s reasonable to remove the limit. Does knots allow you to remove the limit on your node? Does core allow you to enforce the limit? What is the justification for not allowing a node runner to choose the policy for her node?