Replies (17)
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 must be done on knots to not hurt LN?
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
How do you tweak default config on knots to not block lighting?
I believe you have to set an option to remove the dust limit as it doesn’t differentiate between ephemeral dust and regular dust, but you’ll have to check the source/docs.
Ok, thanks.
Weren't you responsible for the inflation bug?
Hm, how is dust related to Lightning?
New lightning channels are moving towards zero-fee commitments, which utilize “ephemeral dust” (ie dust outputs but they’re not allowed to go into the UTXO set, they have to be spent by a second transaction in the same block).
Interesting, need to study that
29.2 knots 🪢 datacarrier=0
ok?
