đź“… Original date posted:2018-10-20
đź“ť Original message:
Good morning everyone,
> We could also use SIGHASH_ANYONECANPAY|SIGHASH_SINGLE
> for HTLC txs, without adding the "OP_TRUE"
> output to the commitment transaction
Doesn’t this require a non-zero number of HTLCs on the commitment txn? We
would still require the OP_TRUE if there are no HTLCs, right?
>From my recollection, HTLC txns with an absolute timeout won’t be accepted
in the mempool until the expiry has matured. So the commitment would have
to be held until that time before it’s descendants can bump the fee rate I
think.
I agree that we should probably modify the HTLC sighashes regardless,
though I wonder if it is a standalone replacement for OP_TRUE.
> 3. The CLTV timeout should be symmetrical to avoid
> trying to game the peer into closing. (Connor IIRC?).
I believe Jimpo proposed this :)
Best,
Conner
On Fri, Oct 19, 2018 at 03:43 Rusty Russell <rusty at rustcorp.com.au> wrote:
> 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.
>
> _______________________________________________
> Lightning-dev mailing list
> Lightning-dev at lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/lightning-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/lightning-dev/attachments/20181020/a6c610be/attachment.html>;
Conner Fromknecht [ARCHIVE] /
npub1za…uua2a
2023-06-09 12:51:51
in reply to nevent1q…96p4
Author Public Key
npub1za0a9afyj7um5feva0d5xmhfsah3zxm252hna2duq0numa952frqvuua2aPublished at
2023-06-09 12:51:51Event JSON
{
"id": "ca74c168adf537f39f60772e0a817f12d73a20478c225e6188e82710ad23e3d3",
"pubkey": "175fd2f52497b9ba272cebdb436ee9876f111b6aa2af3ea9bc03e7cdf4b45246",
"created_at": 1686315111,
"kind": 1,
"tags": [
[
"e",
"c396150541b93fd7dcbb99733d0101c5012b71f16be611915f67f9ed8b9c1baa",
"",
"root"
],
[
"e",
"91732a9e8bf599810406dd8a35fca6ae3c891ea907647bedb14653cf859c57bc",
"",
"reply"
],
[
"p",
"13bd8c1c5e3b3508a07c92598647160b11ab0deef4c452098e223e443c1ca425"
]
],
"content": "📅 Original date posted:2018-10-20\n📝 Original message:\nGood morning everyone,\n\n\u003e We could also use SIGHASH_ANYONECANPAY|SIGHASH_SINGLE\n\u003e for HTLC txs, without adding the \"OP_TRUE\"\n\u003e output to the commitment transaction\n\nDoesn’t this require a non-zero number of HTLCs on the commitment txn? We\nwould still require the OP_TRUE if there are no HTLCs, right?\n\n\u003eFrom my recollection, HTLC txns with an absolute timeout won’t be accepted\nin the mempool until the expiry has matured. So the commitment would have\nto be held until that time before it’s descendants can bump the fee rate I\nthink.\n\nI agree that we should probably modify the HTLC sighashes regardless,\nthough I wonder if it is a standalone replacement for OP_TRUE.\n\n\u003e 3. The CLTV timeout should be symmetrical to avoid\n\u003e trying to game the peer into closing. (Connor IIRC?).\n\nI believe Jimpo proposed this :)\n\nBest,\nConner\n\nOn Fri, Oct 19, 2018 at 03:43 Rusty Russell \u003crusty at rustcorp.com.au\u003e wrote:\n\n\u003e Fabrice Drouin \u003cfabrice.drouin at acinq.fr\u003e writes:\n\u003e \u003e Hello,\n\u003e \u003e\n\u003e \u003e\u003e 1. Rather than trying to agree on what fees will be in the future, we\n\u003e \u003e \u003e should use an OP_TRUE-style output to allow CPFP (Roasbeef)\n\u003e \u003e\n\u003e \u003e We could also use SIGHASH_ANYONECANPAY|SIGHASH_SINGLE for HTLC txs,\n\u003e without\n\u003e \u003e adding the \"OP_TRUE\" output to the commitment transaction. We would still\n\u003e \u003e need the update_fee message to manage onchain fees for the commit tx (but\n\u003e \u003e not the HTLC txs) but there would be no reason anymore to refuse fee\n\u003e rates\n\u003e \u003e that are too high and channels would not get closed anymore when there's\n\u003e a\n\u003e \u003e spike in onchain fees.\n\u003e\n\u003e Agreed, that was in the details below:\n\u003e\n\u003e - HTLC-timeout and HTLC-success txs sigs are\n\u003e SIGHASH_ANYONECANPAY|SIGHASH_SINGLE, so you can Bring Your Own Fees.\n\u003e\n\u003e The only problem with these proposals is that it requires you have an\n\u003e available UTXO to make the CPFP etc.\n\u003e\n\u003e Cheers,\n\u003e Rusty.\n\u003e\n\u003e _______________________________________________\n\u003e Lightning-dev mailing list\n\u003e Lightning-dev at lists.linuxfoundation.org\n\u003e https://lists.linuxfoundation.org/mailman/listinfo/lightning-dev\n\u003e\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/lightning-dev/attachments/20181020/a6c610be/attachment.html\u003e",
"sig": "1b122a19067b8698b40b343b92e340771ff52a6f1104fe94f31f25abe38210262c7ed2d92027b6a7106eb433c3d94a85a64e426eb9eba446139eeb9e42e788e5"
}