Replying to Avatar Aaron van Wirdum

So my main takeaway from this discussion is that nostr:npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk nostr:npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk sees a legal and/or moral difference between data in OP_RETURNs and data in (say) Inscriptions.

*Even if* it’s the exact same data!

(The argument, to the best of my understanding, is that data in OP_RETURNs is “sanctioned” *as data* by Bitcoin Core now that the policy limit is lifted— whereas data in Inscriptions can only be “misinterpreted” as data.)

It does make me wonder how many people in the Knots camp actually understand that this is the level of nuance they are ultimately fighting over. (It seemed that even nostr:npub1wnlu28xrq9gv77dkevck6ws4euej4v568rlvn66gf2c428tdrptqq3n3wr kind of learned this live as they were recording…)

nostr:note19udfg096zlzxjsz6tlunq9hksjtzqfcqrgpeelgw8qc97wdht75s6fxcnp

Here is something that Aaron has never mentioned - Citrea.

Not even once. Its not a coincidence.

nostr:nevent1qqsq262k0h7kdae3pg3vd4fd6xrwgp5fpldgul58fjtjkt939s9gknqppemhxue69uhkummn9ekx7mp0qyg8wumn8ghj7mn0wd68ytnddakj7qg4waehxw309aex2mrp0yhxgctdw4eju6t09urmd9fu

Reply to this note

Please Login to reply.

Discussion

You seem to think this is some kind of smoking gun but it isn't.

Would you rather have Citrea (and potential other protocols like it) put data in fake pubkeys?

It is smoking gun. Why should we exuse one bad action with another one?

As far as I have heard there are other companies that make their technology in a way that 82 Bytes of OP_RETURN is enough.

Bitcoin is not a storage for arbitrary data.

You are trying to excuse Core devs' bad decisions no matter what. You tried excusing CSAM with the Four Horsmen.

You don't mind spam on Bitcoin. You mention that if Citrea don't abuse Bitcoin in one way they will do in another so let them just do whatever they want.

And now you are focused on Lukes argumentation. Luke has fixed inscriptions spam. Its Core devs who rejected it intentionally and we have 30GB+ of spam

for 2+ years. And fees alone have not stopped them.

nostr:nevent1qqsxx68hdxeyftg95xyaanwknccpd7s98hh3fxs6j6tqdd9cskh0tzgppemhxue69uhkummn9ekx7mp0qyg8wumn8ghj7mn0wd68ytnddakj7qgnwaehxw309ahkvenrdpskjm3wwp6kytcr6qfzy

You didn’t answer my question.

And Samson is giving the answer as well that you can't fix fake pubkeys with OP_RETURN. Its just not the fix for them. Everyone can still use them.

Now you’re outsourcing your thinking rather than answering the question. Soit.

If you truly answer the question - What does 100 000 Bytes OP_RETURN fix or what good feature it brings to Bitcoin? The answer is nothing. None. Only spam, risk of csam and abuse.

Bitcoin is Freedom Money. Not arbitrary storage. Increasing OP_RETURN does not fix fake pubkeys.