pull down to refresh
210 sats \ 1 reply \ @Murch 20h \ parent \ on: Quick questions about OP_RETURN? Quick answers here. bitcoin
You are welcome, thank you for taking the time to read my comments.
I would perhaps quibble with "seeks to encourage", but overall we agree.
Yes, a data payload embedded per OP_RETURN would be cheaper than fake public keys or pubkey hashes. I calculate that it would save at least 5–10 bytes of overhead for a small data payload, and much more for larger data payloads.
My read is that Citrea provides a concrete example of detrimental behavior that could be mitigated by raising the OP_RETURN limit. Since there is a concrete description of their scheme it makes an easy to communicate example.