Hi John,
On 2023-08-06 16:35, John Light via bitcoin-dev wrote:
is there ever a case where using OP_RETURN
to embed data actually results in fewer bytes onchain than
embedding the same data using the segwit/taproot witness space
Yes, a
Good morning John Light,
> 2. Documentation about OP_RETURN says that OP_RETURN outputs are
> "provably-prunable".[2] A question I had about this was, are there any tools
> available that a full node operator could use to prune this data from their
> nodes?
As I understand it, `OP_RETURN`
Hi Peter,
Re: https://github.com/bitcoin/bitcoin/pull/28130
I have a few questions about your proposal and its impact on full node
operators:
1. With your proposed policy change removing the OP_RETURN output count and
data size limits, is there ever a case where using OP_RETURN to embed data
https://github.com/bitcoin/bitcoin/pull/28130
Sjors Provoost suggested that I email this mailing list as notice of my intent
to get a pull-req merged that would remove the arbitrary 80-byte, 1 output /
tx, standardness restrictions on OP_Return outputs. His rationale was that
removing these
