summaryrefslogtreecommitdiff
path: root/a6/9705b8a2b952ebc9be302bd8a4900e3f704124
blob: 65de3ef949e5858dd09f471e6f7ff96b07a1ea18 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
Return-Path: <joe2015@openmailbox.org>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
	[172.17.192.35])
	by mail.linuxfoundation.org (Postfix) with ESMTPS id 1A5BF106C
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Mon, 21 Dec 2015 03:59:02 +0000 (UTC)
X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6
Received: from mail2.openmailbox.org (mail2.openmailbox.org [62.4.1.33])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 8BE10ED
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Mon, 21 Dec 2015 03:59:01 +0000 (UTC)
Received: by mail2.openmailbox.org (Postfix, from userid 1004)
	id 4D8B02AC1EA8; Mon, 21 Dec 2015 04:59:00 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=openmailbox.org;
	s=openmailbox; t=1450670340;
	bh=hBkotVW4qjCjKYudVcRD3f4Yj4SpANEzc3XE4GALDMs=;
	h=Date:From:To:Cc:Subject:In-Reply-To:References:From;
	b=dp1mxYQnZumuhAJCf8XHEy2rDKH8ZVLoM/QpY4jaf8dRpYjQGbOsxL0H9Zl0GFqQH
	egor5h1rxR+Wf0nJfeAXkM+DK5SIkBZ/pV+3hMKMymnpi5wZp2KY3NCqiB/dt2X8YJ
	ywJWyWRO/AkObeRlmqmihJ0etY/NSlXAxAKvrmG4=
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
	smtp1.linux-foundation.org
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	DKIM_VALID, DKIM_VALID_AU, RCVD_IN_DNSWL_LOW,
	RP_MATCHES_RCVD autolearn=ham version=3.3.1
Received: from www.openmailbox.org (openmailbox-b1 [10.91.69.218])
	by mail2.openmailbox.org (Postfix) with ESMTP id 3355F2AC12C6;
	Mon, 21 Dec 2015 04:58:50 +0100 (CET)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII;
 format=flowed
Content-Transfer-Encoding: 7bit
Date: Mon, 21 Dec 2015 11:58:50 +0800
From: joe2015@openmailbox.org
To: Jeff Garzik <jgarzik@gmail.com>
In-Reply-To: <CADm_WcYXU6VXG034j=mD8zkmqNLB96sjvBc6qo8Sx2NepHJk8A@mail.gmail.com>
References: <dcf6dfa0f7fdcf96e9970e815e4c9b78@openmailbox.org>
	<CADm_WcYXU6VXG034j=mD8zkmqNLB96sjvBc6qo8Sx2NepHJk8A@mail.gmail.com>
Message-ID: <489826397e6b36bf68391508952042f4@openmailbox.org>
X-Sender: joe2015@openmailbox.org
User-Agent: Roundcube Webmail/1.0.6
X-Mailman-Approved-At: Mon, 21 Dec 2015 04:14:52 +0000
Cc: Bitcoin development mailing list <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Increasing the blocksize as a (generalized)
 softfork.
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Development Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
	<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
	<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Dec 2015 03:59:02 -0000

On 2015-12-21 11:39, Jeff Garzik wrote:
> On Sun, Dec 20, 2015 at 12:21 PM, joe2015--- via bitcoin-dev
> <bitcoin-dev@lists.linuxfoundation.org> wrote:

> Current hard fork implementations include / will include miner
> lock-in, just like any soft fork.  They will not activate if global
> consensus is not reached.

That's not true at all. They activate with a miner majority (e.g. 75%, 
95%, etc.), not global consensus.  Here global really means global, i.e. 
miner, economic, all clients, etc.  In the case of a hardfork there is 
nothing stopping the miner minority from continuing the old chain.  With 
a softfork the miner minority is forced to upgrade otherwise their 
blocks will be eventually orphaned.

My proposal achieves a hardfork-like blocksize limit increase but, like 
a softfork, also forces the miner minority to upgrade.

--joe.