From: "Jorge Timón" <jtimon@jtimon•cc>
To: Tier Nolan <tier.nolan@gmail•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] [BIP draft] Motivation and deployment of consensus rules changes ([soft/hard]forks)
Date: Sun, 21 Jun 2015 12:31:34 +0200 [thread overview]
Message-ID: <CABm2gDrs6XwG5imH3pFFDB71kx2dSfhR7kjc6Pw8hvDKqGvTPQ@mail.gmail.com> (raw)
In-Reply-To: <CAE-z3OVM8vwjo_-FOggSoOWR78w=Rmm+GS7Xv9uSK0jdx1_zdw@mail.gmail.com>
On Sun, Jun 21, 2015 at 12:08 AM, Tier Nolan <tier.nolan@gmail•com> wrote:
> The off by 1 bug could be fixed by a soft fork. Since the point is to show
> how a non-controversial hard fork works, it doesn't matter much.
You mean the timewarp fix can be coded as a softfork instead of a
hardfork? How so?
If that's the case, do you have a better candidate?
next prev parent reply other threads:[~2015-06-21 10:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-20 21:22 Jorge Timón
2015-06-20 22:08 ` Tier Nolan
2015-06-21 10:31 ` Jorge Timón [this message]
2015-06-21 10:54 ` Tier Nolan
2015-07-23 11:10 ` [bitcoin-dev] " Jorge Timón
2015-07-31 17:40 ` Thomas Kerin
2015-07-31 20:37 ` Jorge Timón
2015-08-29 21:21 ` Jorge Timón
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=CABm2gDrs6XwG5imH3pFFDB71kx2dSfhR7kjc6Pw8hvDKqGvTPQ@mail.gmail.com \
--to=jtimon@jtimon$(echo .)cc \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=tier.nolan@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