From: Ryan Grant <bitcoin-dev@rgrant•org>
To: lightning-dev@lists•linuxfoundation.org,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Subject: [bitcoin-dev] BIP118 confusion / SIGHASH_NOINPUT is now SIGHASH_ANYPREVOUT (i think)
Date: Sat, 12 Jun 2021 19:52:45 +0000 [thread overview]
Message-ID: <CAMnpzfosBrAXY+kCW2ZRtsXLRCouGVak7S3mH8jXEgJNBmf8Ug@mail.gmail.com> (raw)
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.
next reply other threads:[~2021-06-12 19:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-12 19:52 Ryan Grant [this message]
2021-06-12 20:56 ` Ryan Grant
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAMnpzfosBrAXY+kCW2ZRtsXLRCouGVak7S3mH8jXEgJNBmf8Ug@mail.gmail.com \
--to=bitcoin-dev@rgrant$(echo .)org \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=lightning-dev@lists$(echo .)linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox