From: Pieter Wuille <pieter.wuille@gmail.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Version bits proposal
Date: Wed, 3 Jun 2015 13:42:44 -0700 [thread overview]
Message-ID: <CAPg+sBgGjcGO4uNQm1P77PaXS5Vj8vpcceNKMDNGxmytRc5weQ@mail.gmail.com> (raw)
In-Reply-To: <CAPg+sBg5TqQ=zjyZ7dp-d1oBGp31Krnix3zyt9suP4-AGbxW=Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 695 bytes --]
Thanks for all the comments.
I plan to address the feedback and work on an implementation next week.
On Tue, May 26, 2015 at 6:48 PM, Pieter Wuille <pieter.wuille@gmail.com>
wrote:
> Hello everyone,
>
> here is a proposal for how to coordinate future soft-forking consensus
> changes: https://gist.github.com/sipa/bf69659f43e763540550
>
> It supports multiple parallel changes, as well as changes that get
> permanently rejected without obstructing the rollout of others.
>
> Feel free to comment. As the gist does not support notifying participants
> of new comments, I would suggest using the mailing list instead.
>
> This is joint work with Peter Todd and Greg Maxwell.
>
> --
> Pieter
>
[-- Attachment #2: Type: text/html, Size: 1239 bytes --]
prev parent reply other threads:[~2015-06-03 20:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-27 1:48 [Bitcoin-development] Version bits proposal Pieter Wuille
2015-05-27 2:31 ` Douglas Roark
2015-05-27 3:46 ` Luke Dashjr
2015-05-27 3:51 ` Jorge Timón
2015-05-27 9:35 ` Tier Nolan
2015-05-27 10:15 ` Peter Todd
2015-05-27 11:26 ` Tier Nolan
2015-05-27 22:52 ` Sergio Lerner
2015-05-28 1:05 ` Patrick Strateman
2015-05-28 7:51 ` Christian Decker
2015-05-28 8:11 ` Adam Back
2015-06-01 14:50 ` Potter QQ
2015-05-27 10:15 ` Jorge Timón
2015-06-03 20:42 ` Pieter Wuille [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=CAPg+sBgGjcGO4uNQm1P77PaXS5Vj8vpcceNKMDNGxmytRc5weQ@mail.gmail.com \
--to=pieter.wuille@gmail.com \
--cc=bitcoin-development@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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