From: jl2012@xbt•hk
To: Bryan Bishop <kanzure@gmail•com>
Cc: Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Short review of previously-proposed exotic SIGHASH types
Date: Mon, 31 Aug 2015 12:24:21 -0400 [thread overview]
Message-ID: <f926a0895b9f8cec7f62045383bec7ea@xbt.hk> (raw)
In-Reply-To: <CABaSBazLWrmd=iKj2sM61cfU==U4zQq95auQLbbnv4HbO_H=QQ@mail.gmail.com>
Bryan Bishop via bitcoin-dev 於 2015-08-30 14:56 寫到:
>
> SIGHASH_WITHOUT_PREV_SCRIPTPUBKEY
> SIGHASH_WITHOUT_PREV_VALUE
> SIGHASH_WITHOUT_INPUT_TXID
> SIGHASH_WITHOUT_INPUT_INDEX
> SIGHASH_WITHOUT_INPUT_SEQUENCE
> SIGHASH_WITHOUT_OUTPUT_SCRIPTPUBKEY
> SIGHASH_WITHOUT_OUTPUT_VALUE
> SIGHASH_WITHOUT_INPUTS
> SIGHASH_WITHOUT_OUTPUTS
> SIGHASH_WITHOUT_INPUT_SELF
> SIGHASH_WITHOUT_OUTPUT_SELF
> SIGHASH_WITHOUT_TX_VERSION
> SIGHASH_WITHOUT_TX_LOCKTIME
> SIGHASH_SIGN_STACK_ELEMENT:
> https://github.com/scmorse/bitcoin-misc/blob/master/sighash_proposal.md
>
Thanks for your summary. This one seems particularly interesting.
However, it does not allow fine adjustment for each input and output
separately, so I wonder if it really "fully enable any seen or unforseen
use case of the CTransactionSignatureSerializer." as it claims.
next prev parent reply other threads:[~2015-08-31 16:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-30 18:56 Bryan Bishop
2015-08-31 16:24 ` jl2012 [this message]
2015-09-01 6:54 ` Peter Todd
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=f926a0895b9f8cec7f62045383bec7ea@xbt.hk \
--to=jl2012@xbt$(echo .)hk \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=kanzure@gmail$(echo .)com \
/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