Thread
Please don’t run 28 over some overblown drama. At least run 29 (or if you’re running Knots please tweak the default configuration to not block Lightning).
npub185h9...wrdp
Please recommend 29, not 28. 29 enables zero-fee-commitments for lightning, which is a really important feature in some cases!
View quoted note →
Replies (6)
I'd imagine this only matters if you are running a lightning node yourself. A quorum of people running Bitcoin Core 28 or lower won't have negative effects on OTHER people sending out zero fee transactions right?
What tweak needs to be made to knots to not block lightning?
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?
What are the datacarrier changes in v29?
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
29.2 knots 🪢 datacarrier=0
ok?
