From: Bob McElrath <bob_bitcoin@mcelrath•org>
To: joe2015@openmailbox•org
Cc: bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] Increasing the blocksize as a (generalized) softfork.
Date: Wed, 30 Dec 2015 19:00:43 +0000 [thread overview]
Message-ID: <20151230190043.GJ18200@mcelrath.org> (raw)
In-Reply-To: <f9ad1348fb7dedca35b594782fee7e0f@openmailbox.org>
joe2015--- via bitcoin-dev [bitcoin-dev@lists•linuxfoundation.org] wrote:
> That's the whole point. After a conventional hardfork everyone
> needs to upgrade, but there is no way to force users to upgrade. A
> user who is simply unaware of the fork, or disagrees with the fork,
> uses the old client and the currency splits.
>
> Under this proposal old clients effectively enter "zombie" mode,
> forcing users to upgrade.
This is a very complex way to enter zombie mode.
A simpler way is to track valid PoW chains by examining only the header, that
are rejected for other reasons.
Once a chain is seen to be 6 or more blocks ahead of my chain tip, we should
enter "zombie mode" and refuse to mine or relay, and alert the operator, because
we don't know what we're doing and we're out of date. This way doesn't require
any modifications to block structure at all.
--
Cheers, Bob McElrath
"For every complex problem, there is a solution that is simple, neat, and wrong."
-- H. L. Mencken
next prev parent reply other threads:[~2015-12-30 19:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-20 10:56 joe2015
2015-12-20 15:22 ` joe2015
2015-12-20 15:50 ` Tier Nolan
2015-12-20 18:17 ` Bryan Bishop
2015-12-21 3:04 ` joe2015
2015-12-21 4:23 ` jl2012
2015-12-21 4:41 ` joe2015
2015-12-30 19:00 ` Bob McElrath [this message]
2015-12-30 23:49 ` Jonathan Toomim
2015-12-30 23:56 ` Jonathan Toomim
2015-12-31 0:04 ` Bob McElrath
2015-12-31 4:39 ` joe2015
2015-12-31 10:39 ` David Chan
2015-12-31 11:32 ` joe2015
2016-01-04 21:53 ` Luke Dashjr
2015-12-20 17:21 joe2015
2015-12-21 3:39 ` Jeff Garzik
2015-12-21 3:58 ` joe2015
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=20151230190043.GJ18200@mcelrath.org \
--to=bob_bitcoin@mcelrath$(echo .)org \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=joe2015@openmailbox$(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