Rusty Russell [ARCHIVE] on Nostr: 📅 Original date posted:2018-10-19 📝 Original message: Fabrice Drouin ...
📅 Original date posted:2018-10-19
📝 Original message:
Fabrice Drouin <fabrice.drouin at acinq.fr> writes:
> 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.
Agreed, that was in the details below:
- HTLC-timeout and HTLC-success txs sigs are
SIGHASH_ANYONECANPAY|SIGHASH_SINGLE, so you can Bring Your Own Fees.
The only problem with these proposals is that it requires you have an
available UTXO to make the CPFP etc.
Cheers,
Rusty.
📝 Original message:
Fabrice Drouin <fabrice.drouin at acinq.fr> writes:
> 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.
Agreed, that was in the details below:
- HTLC-timeout and HTLC-success txs sigs are
SIGHASH_ANYONECANPAY|SIGHASH_SINGLE, so you can Bring Your Own Fees.
The only problem with these proposals is that it requires you have an
available UTXO to make the CPFP etc.
Cheers,
Rusty.