From: "Jorge Timón" <jtimon@jtimon.cc>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: [Bitcoin-development] [BIP draft] Motivation and deployment of consensus rules changes ([soft/hard]forks)
Date: Sat, 20 Jun 2015 23:22:41 +0200 [thread overview]
Message-ID: <CABm2gDqPBPiDG1BUAipEsLfyE1VFyvdqdoxtYjkKvGDvBQ8qMg@mail.gmail.com> (raw)
This is an attempt to unify views on why and how hardforks can be
deployed. I would like to turn this into an informational BIP later
after gathering some feedback.
Please, do not discuss block size issues here: there's plenty of
threads to do so. The scope of this one is only hardforks and
softforks in a more abstract way. Sometimes block size changes are
used as examples because no other example came to mind
(non-blocksize-related examples for the same cases [or others] are
a user should be just ignored. But what if the welcomed), and
if we go into too much detail they stop being useful as examples. So
please, try to avoid going into too much detail about the concrete
examples when possible.
https://github.com/jtimon/bips/blob/bip-forks/bip-forks.org
Please, feel free to make suggestions or bike-shed some of the terms.
next reply other threads:[~2015-06-20 21:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-20 21:22 Jorge Timón [this message]
2015-06-20 22:08 ` [Bitcoin-development] [BIP draft] Motivation and deployment of consensus rules changes ([soft/hard]forks) Tier Nolan
2015-06-21 10:31 ` Jorge Timón
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=CABm2gDqPBPiDG1BUAipEsLfyE1VFyvdqdoxtYjkKvGDvBQ8qMg@mail.gmail.com \
--to=jtimon@jtimon.cc \
--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