From: LORD HIS EXCELLENCY JAMES HRMH <willtech@live•com.au>
To: "bitcoin-dev@lists•linuxfoundation.org"
<bitcoin-dev@lists•linuxfoundation.org>
Subject: [bitcoin-dev] List of proposals for hard fork/soft fork
Date: Sun, 14 Apr 2019 14:44:53 +0000 [thread overview]
Message-ID: <PS2P216MB01792E6227170E85F95A2BB49D2A0@PS2P216MB0179.KORP216.PROD.OUTLOOK.COM> (raw)
[-- 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 --]
next reply other threads:[~2019-04-14 14:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-14 14:44 LORD HIS EXCELLENCY JAMES HRMH [this message]
2019-04-15 2:59 ` ZmnSCPxj
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=PS2P216MB01792E6227170E85F95A2BB49D2A0@PS2P216MB0179.KORP216.PROD.OUTLOOK.COM \
--to=willtech@live$(echo .)com.au \
--cc=bitcoin-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