There are also other good technical reasons which I have chosen to retain the lower default in Bitcoin Knots, and no justification for increasing it. It is not my intention, nor that of my team at @bitcoinocean.bsky.social, to filter coinjoins.
Core subsequently increasing the default to 80 bytes was an entirely voluntary decision and in no way contradicts the design objective that OP_RETURN creates a provably-prunable output to minimise damage caused by data storage schemes, which have always been discouraged as abusive.
At that time, 40 bytes was the default max datacarriersize limit across all node implementations; this was and still is sufficiently large for tying data to a transaction (32 bytes for a hash and 8 bytes for a unique identifier).
The OP_RETURN discussion is not new and dates back to 2014 when Bitcoin Core 0.9.0 was released with the OP_RETURN policy included which was intended to discourage more egregious forms of spam.
This bug was recently fixed in Bitcoin Knots v25.1. It took longer than usual due to my workflow being severely disrupted at the end of last year (v24 was skipped entirely). Bitcoin Core is still vulnerable in the upcoming v26 release. I can only hope it will finally get fixed before v27 next year.
Master key: 93CB4961F69A65082D4410802CBA8253089655C3 Codesigning key: 1A3E761F19D2CC7785C5502EA291A2C45D0C504A Security comms key: FAC098FE8DF9975F902418813666E2B1782A18E1
- master key signing codesigning key (used for Knots v25.1) - master key signing security communication key (for email about security issues) - codesigning key signing master key
If you were waiting for me to publish my new "master" OpenPGP key announced at #FutureOfBitcoinMiningkeyserver.ubuntu.com along with signatures:
As announced at the #FutureOfBitcoinMining#Bitcoin@bitcoinocean.bsky.socialwww.prnewswire.com/news-release...
/PRNewswire/ -- Mummolin, Inc., announced today that it has raised $6.2million in seed funding, led by Jack Dorsey, Accomplice, Barefoot Bitcoin Fund,...