Re: [Lightning-dev] Improving Payment Latency by Fast Forwards
Hi Z, Thanks again for getting to the bottom of this. I think we are on the same page except for one clarification: On Tue, 8 Jun 2021 at 12:37, ZmnSCPxj wrote: > Thus, in our model, we have the property that Bob can always recover all > signatures sent by Alice, even if Carol is corrupted by Alice --- we model > the signature-deletion attack as impossible, by assumption. > (This is a strengthening of security assumptions, thus a weakening of the > security of the scheme --- if Bob does not take the above mitigations, Bob > ***is*** vulnerable to a signature-deletion attack and might have ***all*** > funds in hostage). > Only where ***all*** refers to the funds in the fast forward -- funds consolidated into the channel balance are not at risk (modulo enforcing correct state on chain). I think it should be easy to get a stream of signatures so they can't be deleted. The user "Bob" is creating and sending the invoices so they can always demand and save the signatures from "Carol the Cashier" that correspond to each payment so the "deletion attack" will be thwarted. LL ___ Lightning-dev mailing list Lightning-dev@lists.linuxfoundation.org https://lists.linuxfoundation.org/mailman/listinfo/lightning-dev
Re: [Lightning-dev] BIP118 confusion / SIGHASH_NOINPUT is now SIGHASH_ANYPREVOUT (i think)
Apologies, I found the discussion going on here: https://github.com/bitcoin/bips/pull/943 On Sat, Jun 12, 2021 at 7:52 PM Ryan Grant wrote: > > Hi, > > I have detected some definite confusion among people who are not aware > of the most recent updates to the bip118 draft. I don't know if > that's common among readers of these lists. > > Substantial edits to the bip118 draft were made through May 2019, > including changing its official name to SIGHASH_ANYPREVOUT. The > internal heading "Revisions" discusses these changes. > > > https://github.com/ajtowns/bips/blob/c7c6a58b7a66a5dc5f4435319577d26a34082a79/bip-0118.mediawiki#Revisions > https://github.com/ajtowns/bips/compare/master...ajtowns:bip-anyprevout > > https://github.com/ajtowns/bips/blob/c7c6a58b7a66a5dc5f4435319577d26a34082a79/bip-0118.mediawiki > > The version in bitcoin/bips was not modified since 2018, until it > diverged by collecting a minor fix two months ago. It still uses > SIGHASH_NOINPUT terminology. > > https://github.com/bitcoin/bips/blob/master/bip-0118.mediawiki > > AFAICT, with taproot activating, the preferred method to ease > lightning network client state requirements will now definitely be > SIGHASH_ANYPREVOUT. > > I am not aware of reasons for bip118's updated draft to sit on the > sidelines before consideration by a wider audience. ___ Lightning-dev mailing list Lightning-dev@lists.linuxfoundation.org https://lists.linuxfoundation.org/mailman/listinfo/lightning-dev
[Lightning-dev] BIP118 confusion / SIGHASH_NOINPUT is now SIGHASH_ANYPREVOUT (i think)
Hi, I have detected some definite confusion among people who are not aware of the most recent updates to the bip118 draft. I don't know if that's common among readers of these lists. Substantial edits to the bip118 draft were made through May 2019, including changing its official name to SIGHASH_ANYPREVOUT. The internal heading "Revisions" discusses these changes. https://github.com/ajtowns/bips/blob/c7c6a58b7a66a5dc5f4435319577d26a34082a79/bip-0118.mediawiki#Revisions https://github.com/ajtowns/bips/compare/master...ajtowns:bip-anyprevout https://github.com/ajtowns/bips/blob/c7c6a58b7a66a5dc5f4435319577d26a34082a79/bip-0118.mediawiki The version in bitcoin/bips was not modified since 2018, until it diverged by collecting a minor fix two months ago. It still uses SIGHASH_NOINPUT terminology. https://github.com/bitcoin/bips/blob/master/bip-0118.mediawiki AFAICT, with taproot activating, the preferred method to ease lightning network client state requirements will now definitely be SIGHASH_ANYPREVOUT. I am not aware of reasons for bip118's updated draft to sit on the sidelines before consideration by a wider audience. ___ Lightning-dev mailing list Lightning-dev@lists.linuxfoundation.org https://lists.linuxfoundation.org/mailman/listinfo/lightning-dev