pull down to refresh

All of the debate over op_return is exhausting since the datacarriersize variable is easily added into bitcoin.conf file
datacarriersize=83 puts op_return relay size at core 29 default. right?
seems like we should just be spreading this small piece of education so people can just learn how to configure their node anywhay they want.
111 sats \ 1 reply \ @96c0b276a3 10h
Iiuc that configuration will be going away in a future release. V30 changing the default is just the first step.
reply
I don't expect Core to remove the config option if it's wanted. Recent quote from sipa 1 also says the that this config setting is unlikely to be removed anytime soon if that's controversial to remove.
It is marked deprecated, which means the option is expected to be removed in a future version, but given the current political dispute around it, I do not expect that will happen any time soon.
If it gets removed, it's easy to patch back in too.

Footnotes

reply
datacarrier=0
reply
0 sats \ 4 replies \ @000w2 3h
No, that's not correct. The meaning of the datacarriersize variable is different in v30, compared to v29.
reply
thanks. is there documentation on this new variable?
reply
245 sats \ 1 reply \ @000w2 1h
Actually, now I'm not sure. I was originally going by Luke's post, but it seems to conflict with the current release notes draft.
reply
bingo!!!!
reply
0 sats \ 0 replies \ @000w2 1h
deleted by author
it has been mentioned on nostr that datacarriersize doesn't work on core since version 26, is this correct?
reply