RFC: simplifications and suggestions on open/accept limits.

Posted by Rusty Russell

Nov 1, 2018/01:03 UTC

Gert-Jaap Glasbergen has shared his opinion on the removal of htlc_minimum_msat. He believes that it is the only protection measure against producing trimmed HTLCs and should not be removed. He recommends setting the safe default above the dust limit to prevent trusted in-flight payments that can't be enforced on-chain. While non-dust outputs may still be uneconomic to collect, he suggests varying the definition of "dust" with fees. He also suggests defining minimum_depth per chain instead of a fixed number in the standard. Gert-Jaap proposes adding either transaction_min_msat_multiple or accept_subsatoshi to enable users to opt-out of parts below 1000 msat that cannot be enforced on-chain.Rusty agrees with Gert-Jaap's suggestion about minimum_depth being chain-dependent but disagrees with opting out of parts below 1000 msat. Rusty thinks that it would render one inoperable in practice since fees are frequently sub-satoshi. He believes that on-chain enforcement is not a panacea as probabilistic payments can still be gamed.

Link to Raw Post
Bitcoin Logo

TLDR

Join Our Newsletter

We’ll email you summaries of the latest discussions from authoritative bitcoin sources, like bitcoin-dev, lightning-dev, and Delving Bitcoin.

Explore all Products

ChatBTC imageBitcoin searchBitcoin TranscriptsSaving SatoshiBitcoin Transcripts Review
Built with 🧡 by the Bitcoin Dev Project
View our public visitor count

We'd love to hear your feedback on this project?

Give Feedback