summaryrefslogtreecommitdiff
path: root/67/96cb1a26f57abe9cf78a4e0d28fc91391c3363
blob: ddb4179e3c65e208ab480c03fa75b8df3a37d174 (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
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
Return-Path: <edmund.edgar@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
	[172.17.192.35])
	by mail.linuxfoundation.org (Postfix) with ESMTPS id 3BEEDB44
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Tue,  7 Mar 2017 01:07:08 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-wr0-f182.google.com (mail-wr0-f182.google.com
	[209.85.128.182])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 14074F1
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Tue,  7 Mar 2017 01:07:07 +0000 (UTC)
Received: by mail-wr0-f182.google.com with SMTP id u108so128537841wrb.3
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Mon, 06 Mar 2017 17:07:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
	h=mime-version:sender:in-reply-to:references:from:date:message-id
	:subject:to; bh=fa1654Rj/yHavMfKGExNgV6RW43WgPMu5Ys3B4k9Hgc=;
	b=fNdJT3tR+BLh2BKGaMN35RR1MQZEqwVCaMMKOLK2bLDavhbEcoHVUY2GV3doMVw02j
	oilYtVuaSp9Zq2mRcjCg8Qo1MVLnOOeSJLIPs2n/P/qt1eILh2axN5npF66wPhAbmceG
	6aHTy51R/mBfLia2IuYEXWxwPMwfzMvCI8M3VUDUYVQRQKHhkFaANDUypMDoomlzH3aE
	WAN4HAP91gTQDEZJ6HefExFwd0EIDGbI28Yiu+EEVwzLq4Qrl1qTsTVyTdMlfJaaho6Q
	ho+v+LID8kZbcJjp87g3kGtJZWgWy8w4b689LnyXLY/zIauN/tYQzpA0rrqwRDGzaIC6
	LOGw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20161025;
	h=x-gm-message-state:mime-version:sender:in-reply-to:references:from
	:date:message-id:subject:to;
	bh=fa1654Rj/yHavMfKGExNgV6RW43WgPMu5Ys3B4k9Hgc=;
	b=q+nsLvqKuf1AEtMuK3soYX3iibJYEGP3oxH0s7u9A45i6AJ/fyXifRIszjk9XSXYnS
	qaSKIPrFPdipiAjj2fQvx2/iAAVm9UsgV7tVLdlxlTQHwdon/lJSJ1P9nVNHpNVo3VTJ
	BpQ8oOBWJvY2mjKJYT6IUg3E4chUFzxvPKOTLH10AYKiWRYlAWkcl81uZVQqCpMtWD1y
	h/IoeY3qF4kkiTZ/21PX06d6c4ISpYa0PJTQy6iQ3pyGrHK2QdMpqPt4sdY4WX4bKIrn
	CX1V1weNUinICEYk8SUlQssjJ76zzE1tmNZfFqK2e1n+JqyMEeoNKCPBLder3ZQfTl4S
	sPOw==
X-Gm-Message-State: AMke39msFx4LE4ennmcaLX5idabWvb8WOgGPEXH7kThfehPKxX4606o/zPoMy3bqVvVfpTPUFGACg8tKG7MoPg==
X-Received: by 10.223.170.210 with SMTP id i18mr18264702wrc.114.1488848825604; 
	Mon, 06 Mar 2017 17:07:05 -0800 (PST)
MIME-Version: 1.0
Sender: edmund.edgar@gmail.com
Received: by 10.80.163.187 with HTTP; Mon, 6 Mar 2017 17:07:05 -0800 (PST)
In-Reply-To: <964E4801-234F-4E30-A040-2C63274D27F2@posteo.net>
References: <0ba5bf9c-5578-98ce-07ae-036d0d71046b@riseup.net>
	<CAFVRnyomgeXu2pRO=+B7bwB-bZdEL2DcpJNPMz=tAhht6eZXAQ@mail.gmail.com>
	<CANN4kmcLTcqHL53tEFk=g9o0_PsGzwArm9wgd0__ZXZpvhrs1g@mail.gmail.com>
	<CAFVRnyr4QoU5Rn2ryQ-jG8sZ18J7NKcpd3Cg+uN1sfiA=FiB+Q@mail.gmail.com>
	<CA+su7OV0Cpe=4AKdNhJXOCbYVriEN1vHSoA_0r31GXCAP1=NCA@mail.gmail.com>
	<964E4801-234F-4E30-A040-2C63274D27F2@posteo.net>
From: Edmund Edgar <ed@realitykeys.com>
Date: Tue, 7 Mar 2017 10:07:05 +0900
X-Google-Sender-Auth: 9GYDnqMORHtVVOtaJlLUSxc1a8Y
Message-ID: <CA+su7OXOfG2AsLqh-i4YZHc42tFPm+4OBqOV4jCrpADtx4U71g@mail.gmail.com>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: text/plain; charset=UTF-8
X-Spam-Status: No, score=-1.4 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	DKIM_VALID, FREEMAIL_FROM, RCVD_IN_DNSWL_NONE,
	RCVD_IN_SORBS_SPAM autolearn=no version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
	smtp1.linux-foundation.org
X-Mailman-Approved-At: Tue, 07 Mar 2017 01:15:08 +0000
Subject: Re: [bitcoin-dev] Moving towards user activated soft fork activation
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Protocol 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: Tue, 07 Mar 2017 01:07:08 -0000

On 7 March 2017 at 08:23, Gareth Williams <gjw@posteo.net> wrote:
> What you're describing is a hashpower activated soft fork to censor transactions, in response to a user activated soft fork that the majority of hashpower disagrees with.

Well, they'd be censoring transactions to prevent the thing from
activating in the first place. (As opposed to censoring a subset of
those transactions to enforce the new rule, which is the behaviour
that the people promoting the change want.) There would be no point at
which people reasonably expected that something useful would happen if
they sent funds to an address protected by the new scripting rule.

> Bitcoin only works if the majority of hashpower is not hostile to the users.

This is true. But what we're talking about here is hostility to *a
particular proposal to change the network rules* which is (in this
hypothetical case) supported by the economic majority of users. This
doesn't, in itself, break Bitcoin, although the economic majority are
of course always free to hard-fork to something new if they're
unhappy.

Edmund

-- 
-- 
Edmund Edgar
Founder, Social Minds Inc (KK)
Twitter: @edmundedgar
Linked In: edmundedgar
Skype: edmundedgar
http://www.socialminds.jp

Reality Keys
@realitykeys
ed@realitykeys.com
https://www.realitykeys.com