From fabrice.drouin at acinq.fr Thu Oct 18 11:28:31 2018 From: fabrice.drouin at acinq.fr (Fabrice Drouin) Date: Thu, 18 Oct 2018 13:28:31 +0200 Subject: [Lightning-dev] Commitment Transaction Format Update Proposals? In-Reply-To: <87o9by4knd.fsf@rustcorp.com.au> References: <87in2769wc.fsf@rustcorp.com.au> <87woqn4qnq.fsf@rustcorp.com.au> <0trii6U1G6DP2SAYk75X14oPcS51ZDUJTst7xycABfWTzSB62fpx0LQ5gRR3wfbRUgIIC98_XoTYHDUz4RH97qSODlWTvJU3bX1-q8tXN5Q=@protonmail.com> <87o9by4knd.fsf@rustcorp.com.au> Message-ID: Hello, > 1. Rather than trying to agree on what fees will be in the future, we > should use an OP_TRUE-style output to allow CPFP (Roasbeef) We could also use SIGHASH_ANYONECANPAY|SIGHASH_SINGLE for HTLC txs, without adding the "OP_TRUE" output to the commitment transaction. We would still need the update_fee message to manage onchain fees for the commit tx (but not the HTLC txs) but there would be no reason anymore to refuse fee rates that are too high and channels would not get closed anymore when there's a spike in onchain fees. Cheers, Fabrice -------------- next part -------------- An HTML attachment was scrubbed... URL: