Nostr Web Client

Ok so apparently rolling back the chain in case of a CSAM OP_RETURN is also proposed as an activation mechanism for this “anti-spam” soft fork drafted by nostr:npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk nostr:npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk.

Also, even if no such OP_RETURN is mined, they want to activate this as a UASF within ~three(!) months.

https://github.com/bitcoin/bips/pull/2017/commits/3c718237072c107ced8c3531a487354fbdae55df

zoomoutpls 2mo ago

"ArmanTheParman 3 hours ago •

How about... There should be no subjective assessment of arbitrary data's content/meaning, all arbitrary data (extra data not contributing to the movement of sats on layer 1) can just be rejected indiscriminately based on some limit, eg zero.

I acknowledge not all arbitrary data can be, or needs to be, eliminated, but the principle is objective, and rules based off that can be made. If some arbitrary data cannot be interpreted as being arbitrary, then so be it, it gets on chain.

But having a FIELD dedicated to arbitrary data can easily be objectively blocked."

Reply to this note

Discussion