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.
Iiuc that configuration will be going away in a future release. V30 changing the default is just the first step.
I don't expect Core to remove the config option if it's wanted. Recent quote from sipa [ptr] also says the that this config setting is unlikely to be removed anytime soon if that's controversial to remove.
If it gets removed, it's easy to patch back in too.
#1219092 / link ↩
No, that's not correct. The meaning of the datacarriersize variable is different in v30, compared to v29.
thanks. is there documentation on this new variable?
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.
https://github.com/bitcoin-core/bitcoin-devwiki/wiki/v30.0-Release-Notes-Draft
bingo!!!!
deleted by author
it has been mentioned on nostr that datacarriersize doesn't work on core since version 26, is this correct?
nostr:nevent1qqs84k8uw83qj3a6whf8t0tr59mclqvryxsal9tehy2rek0ktn4e0lgzyr70wzj9e75p064gzwum4z3ht4cn6vtf7j3870w2c02fzyklvlfhuqcyqqqqqqgy842zd
datacarrier=0