Redecentralizing the Web w/ @remotestorage and @kosmos. Evading winters w/ @hackerbeach. Traveling full-time since 2010. INTP.
Move slow and fix things.
| :xmpp: / ✉️ / :nostr: | raucao@kosmos.org |
| ⚡ | raucao@kosmos.org |
| Cycling, coffee, beer, food | Yes, please! |
@codewiz Context: https://github.com/bitcoin/bitcoin/pull/32359 (plus drama on X)
Which resulted in this merged solution: https://github.com/bitcoin/bitcoin/pull/32406
The statement and PR are different from what you're suggesting: if the tx is valid, then the OP_RETURN size should not be capped at an arbitrarily low limit by default, because OP_RETURN was made for storing data and can be pruned by nodes that don't care.
Why bitcoin? Because everything else has worse guarantees of persistence and integrity. Proof of Work required.
As per recent bitcoindev mailing list discussion. Also removes the code to enforce those limits, including the -datacarrier and -datacarriersize config options. These limits are easily bypassed by ...
Georgi