From: Gregory Maxwell <gmaxwell@gmail•com>
To: Luke-Jr <luke@dashjr•org>
Cc: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Supermajority mining votes for valid->invalid changes.
Date: Mon, 3 Oct 2011 01:39:07 -0400 [thread overview]
Message-ID: <CAAS2fgSgH5eH+9eY8e=T946NRW10_aiWvDM523+HJgBL2zEgew@mail.gmail.com> (raw)
In-Reply-To: <201110030132.21646.luke@dashjr.org>
On Mon, Oct 3, 2011 at 1:32 AM, Luke-Jr <luke@dashjr•org> wrote:
> Perhaps as a safeguard:
> (3) Before applying the new rule, require 50% of the last Y blocks contain a
> coinbase with a "I am upgraded" code
> (4) Until the new rule is active, include an "I am upgraded" code in every
> block; after it's active, this can be turned off
(4) is a nice idea.
I was hoping to avoid (3) simply because for any one of these upgrades
hopefully 95% of the network is neutral wrt the change because they
won't mine either form of the transactions.
The active statement has the benefit that it constitutes a proof: You
know with specific confidence (based on the window size) how likely a
fork of length X will be if a newly invalid transaction is announced
at the time of the activation.
prev parent reply other threads:[~2011-10-03 5:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-03 4:53 Gregory Maxwell
2011-10-03 5:32 ` Luke-Jr
2011-10-03 5:39 ` Gregory Maxwell [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='CAAS2fgSgH5eH+9eY8e=T946NRW10_aiWvDM523+HJgBL2zEgew@mail.gmail.com' \
--to=gmaxwell@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=luke@dashjr$(echo .)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