so users should just stomach the datacarrier code comment changes in exchange for security patches? what if users simply dont want to relay garbage (inscriptions, stamps, large op_returns, etc) as unconfirmed transactions to their peers? shit out of luck?

Replies (2)

im referring to the code comment change to datacarrier in v26 which limits datacarrier to outputs (meaning input-styled arbitrary data storage schemes like inscriptions would not be in scope) on another note, v29.1 has the minrelay fee changes (reduced from 1 to .1) backported