* [bitcoin-dev] List of proposals for hard fork/soft fork
@ 2019-04-14 14:44 LORD HIS EXCELLENCY JAMES HRMH
2019-04-15 2:59 ` ZmnSCPxj
0 siblings, 1 reply; 2+ messages in thread
From: LORD HIS EXCELLENCY JAMES HRMH @ 2019-04-14 14:44 UTC (permalink / raw)
To: bitcoin-dev
[-- Attachment #1: Type: text/plain, Size: 419 bytes --]
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
[-- Attachment #2: Type: text/html, Size: 1503 bytes --]
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [bitcoin-dev] List of proposals for hard fork/soft fork
2019-04-14 14:44 [bitcoin-dev] List of proposals for hard fork/soft fork LORD HIS EXCELLENCY JAMES HRMH
@ 2019-04-15 2:59 ` ZmnSCPxj
0 siblings, 0 replies; 2+ messages in thread
From: ZmnSCPxj @ 2019-04-15 2:59 UTC (permalink / raw)
To: LORD HIS EXCELLENCY JAMES HRMH, Bitcoin Protocol Discussion
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
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2019-04-15 2:59 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-04-14 14:44 [bitcoin-dev] List of proposals for hard fork/soft fork LORD HIS EXCELLENCY JAMES HRMH
2019-04-15 2:59 ` ZmnSCPxj
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox