* [bitcoin-dev] BIP118 confusion / SIGHASH_NOINPUT is now SIGHASH_ANYPREVOUT (i think)
@ 2021-06-12 19:52 Ryan Grant
2021-06-12 20:56 ` Ryan Grant
0 siblings, 1 reply; 2+ messages in thread
From: Ryan Grant @ 2021-06-12 19:52 UTC (permalink / raw)
To: lightning-dev, Bitcoin Protocol Discussion
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.
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [bitcoin-dev] BIP118 confusion / SIGHASH_NOINPUT is now SIGHASH_ANYPREVOUT (i think)
2021-06-12 19:52 [bitcoin-dev] BIP118 confusion / SIGHASH_NOINPUT is now SIGHASH_ANYPREVOUT (i think) Ryan Grant
@ 2021-06-12 20:56 ` Ryan Grant
0 siblings, 0 replies; 2+ messages in thread
From: Ryan Grant @ 2021-06-12 20:56 UTC (permalink / raw)
To: Ryan Grant; +Cc: Bitcoin Protocol Discussion, lightning-dev
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 <bitcoin-dev@rgrant.org> 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.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2021-06-12 20:57 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-06-12 19:52 [bitcoin-dev] BIP118 confusion / SIGHASH_NOINPUT is now SIGHASH_ANYPREVOUT (i think) Ryan Grant
2021-06-12 20:56 ` Ryan Grant
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox