From: "Luke-Jr" <luke@dashjr•org>
To: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Supermajority mining votes for valid->invalid changes.
Date: Mon, 3 Oct 2011 01:32:19 -0400 [thread overview]
Message-ID: <201110030132.21646.luke@dashjr.org> (raw)
In-Reply-To: <CAAS2fgRSw8ry7wjL5Fao1U+Ps0-6hfDcme_V_OCSkKaRTm2r9w@mail.gmail.com>
On Monday, October 03, 2011 12:53:51 AM Gregory Maxwell wrote:
> Upgraded nodes get the following rules:
> (0) Never forward or mine a txn which would be invalid under the new rule.
> (1) Apply old behavior before height X unconditionally.
> (X set far enough in the future to get reasonable deployment by
> large miners)
> (2) Begin applying the new rule only after the first point in the chain
> after X when none of the last Y blocks have contained an invalid
> transaction under the new rules.
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
> After the software has been released members of the bitcoin community then
> begin _intentionally_ transmitting transactions which are invalid under
> the new rules. (What would have been an attack under simplest deployment
> plan)
Why would legitimate community members ever intentionally transmit an invalid
transaction? ;)
next prev parent reply other threads:[~2011-10-03 5:32 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 [this message]
2011-10-03 5:39 ` Gregory Maxwell
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=201110030132.21646.luke@dashjr.org \
--to=luke@dashjr$(echo .)org \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/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