From: ZmnSCPxj <ZmnSCPxj@protonmail•com>
To: LORD HIS EXCELLENCY JAMES HRMH <willtech@live•com.au>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] List of proposals for hard fork/soft fork
Date: Mon, 15 Apr 2019 02:59:44 +0000 [thread overview]
Message-ID: <uwXr_PVDhAxPgfWwqANXIj4h0dyTW8ID4H9SMr1Aw6hYGfiB722bIcmhsZtyKMkdDUN9TzJUtcFxQ_mTvbjsqDKOIX4UtkBpl_4q_EpS1Cg=@protonmail.com> (raw)
In-Reply-To: <PS2P216MB01792E6227170E85F95A2BB49D2A0@PS2P216MB0179.KORP216.PROD.OUTLOOK.COM>
Good morning LORD YOUR EXCELLENCY,
May it please you to be informed the below are likely to be included in some kind of upcoming softfork for SegWit v1:
1. Schnorr signatures.
2. MuSig.
3. Taproot.
4. `SIGHASH_NOINPUT`.
5. Signature aggregation. May it please you to be informed, that "Schnorr" enables signature aggregation, but is not signature aggregation itself.
6. MAST.
The above may or may not be an exhaustive list, your excellency.
Of these, I believe only `SIGHASH_NOINPUT` has a BIP, may it please your excellency to learn that it is BIP 118.
However, I am sorry to inform your excellency, as I understand the `SIGHASH_NOINPUT` that will eventually reach Bitcoin Core will not match the current version of BIP118.
To improve on the possibility of incorrect use of `SIGHASH_NOINPUT`, it is proposed that every input that is signed with a `SIGHASH_NOINPUT` signature additionally require a signature without `SIGHASH_NOINPUT`.
For other details, I am sorry to inform your excellency, I have no reliable knowledge.
Regards,
ZmnSCPxj
Sent with ProtonMail Secure Email.
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Sunday, April 14, 2019 10:44 PM, LORD HIS EXCELLENCY JAMES HRMH via bitcoin-dev <bitcoin-dev@lists•linuxfoundation.org> wrote:
> Is anybody keeping a list of the solid proposals > BIP's to be included in any actual future consensus-driven fork? Perhaps pre-consensus voting of what to include in the fork packages?
>
> Surely not every or each proposal ever scouted is on for consideration.
>
> This may actually help to build momentum for useful and valuable implementations that may otherwise languish.
>
> Regards,
> LORD HIS EXCELLENCY JAMES HRMH
prev parent reply other threads:[~2019-04-15 2:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-14 14:44 LORD HIS EXCELLENCY JAMES HRMH
2019-04-15 2:59 ` ZmnSCPxj [this message]
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='uwXr_PVDhAxPgfWwqANXIj4h0dyTW8ID4H9SMr1Aw6hYGfiB722bIcmhsZtyKMkdDUN9TzJUtcFxQ_mTvbjsqDKOIX4UtkBpl_4q_EpS1Cg=@protonmail.com' \
--to=zmnscpxj@protonmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=willtech@live$(echo .)com.au \
/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