pull down to refresh

Calling it a standardness rule seems... uncomfortable. It seems too high, in that a standard is something generally reached by consensus. I think it should be referred to as a convention, which denotes both that it is commonly adhered to, but deviation is not a significant issue.
Would there be any point in changing the naming from "standardness rules" to "conventions"? "Standardness rules" seems easier to conflate with "consensus rules" which is the most common source of confusion I've seen.
110 sats \ 1 reply \ @Murch 12h
That’s fair. Instead of referring to transactions that fail Bitcoin Core’s mempool policy as non-standard, we should really be talking about "transactions that are [not] accepted by Bitcoin Core’s mempool policy defaults". It’s a bit of a mouthful, though.
reply
42 sats \ 0 replies \ @k00b 12h
True. Explicitness tends to limit outrage memeing though.
"core is changing its tx conventions" vs "core is changing its tx standards"
idk maybe the results are similar.
reply