summaryrefslogtreecommitdiff
path: root/c7/4b0fcabc9cb47cba3b202308b5d7d8a1ff6f38
blob: 89abec3ce16b1012f64d39e873058463999c0929 (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
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
	helo=mx.sourceforge.net)
	by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <gacrux@gmail.com>) id 1WfUDX-000397-3l
	for bitcoin-development@lists.sourceforge.net;
	Wed, 30 Apr 2014 13:06:31 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.213.178 as permitted sender)
	client-ip=209.85.213.178; envelope-from=gacrux@gmail.com;
	helo=mail-ig0-f178.google.com; 
Received: from mail-ig0-f178.google.com ([209.85.213.178])
	by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1WfUDT-00076H-SR
	for bitcoin-development@lists.sourceforge.net;
	Wed, 30 Apr 2014 13:06:31 +0000
Received: by mail-ig0-f178.google.com with SMTP id r10so30164igi.11
	for <bitcoin-development@lists.sourceforge.net>;
	Wed, 30 Apr 2014 06:06:22 -0700 (PDT)
X-Received: by 10.50.119.132 with SMTP id ku4mr4269470igb.35.1398862815970;
	Wed, 30 Apr 2014 06:00:15 -0700 (PDT)
Received: from [192.168.1.150] (60-240-212-53.tpgi.com.au. [60.240.212.53])
	by mx.google.com with ESMTPSA id on9sm5699892igb.11.2014.04.30.06.00.14
	for <bitcoin-development@lists.sourceforge.net>
	(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
	Wed, 30 Apr 2014 06:00:15 -0700 (PDT)
Message-ID: <5360F3D6.4040002@gmail.com>
Date: Wed, 30 Apr 2014 23:00:06 +1000
From: Gareth Williams <gacrux@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
	rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
References: <CANEZrP3obO9rXKcX+G7bs2dd3AqEFOsO8pCUF6orrkGeZyr9Ew@mail.gmail.com>	<CAC1+kJPxwTm6qvh2GYT2XMJAPD5O4WHLOGBTRmchRmZ2wS4MSg@mail.gmail.com>	<CANEZrP2PZFVvH3oJyLW80e9W_Fa4bvqQ25E7T-ZFFuG9u-q1hQ@mail.gmail.com>	<5359E509.4080907@gmail.com>	<CANEZrP0bKe-=T5ps0myLZjo60tv2mkm3Bw0o4e-9y7zb1h5eDg@mail.gmail.com>	<535A60FE.10209@gmail.com>	<CANEZrP0y45eSVgbzXYmvYy1WEQNyd=tmC2EpZgGSB28poXSzDw@mail.gmail.com>	<535BA357.6050607@gmail.com>	<CANOOu=_T82zuV79DWZFGK0Nomhp-Y4tqOhw6ZHhCLb2uGtdR5w@mail.gmail.com>	<535CFDB4.1000200@gmail.com>	<20140428214102.GA8347@netbook.cypherspace.org>
	<CANEZrP0E=i6gyJwvLZRTeKvqaVrxR69=UzJWsAqaK2=QSdtn_A@mail.gmail.com>
In-Reply-To: <CANEZrP0E=i6gyJwvLZRTeKvqaVrxR69=UzJWsAqaK2=QSdtn_A@mail.gmail.com>
X-Enigmail-Version: 1.6
OpenPGP: id=378E4544
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="9WfBTFTM6mxSSVirKtmTGvSwQ2fekDwlB"
X-Spam-Score: -1.6 (-)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
	sender-domain
	0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
	(gacrux[at]gmail.com)
	-0.0 SPF_PASS               SPF: sender matches SPF record
	-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
	author's domain
	0.1 DKIM_SIGNED            Message has a DKIM or DK signature,
	not necessarily valid
	-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1WfUDT-00076H-SR
Subject: Re: [Bitcoin-development] Coinbase reallocation to discourage
 Finney attacks
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Wed, 30 Apr 2014 13:06:31 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--9WfBTFTM6mxSSVirKtmTGvSwQ2fekDwlB
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On 30/04/14 00:13, Mike Hearn wrote:
> I do think we need to move beyond this idea of Bitcoin being some kind
> of elegant embodiment of natural mathematical law. It just ain't so.=20

I haven't seen anybody arguing that it is.

Bitcoin is the elegant embodiment of /artificially contrived/
mathematical rules, which just so happen to be very useful in their
current configuration :-P

Nobody is saying those rules are immutable. Just that it isn't sensible
to undermine them by introducing imprecise and unpredictable elements
like human politics.


> Every time miners and nodes ignore a block that creates >formula() coin=
s
> that's a majority vote on a controversial political matter

No it isn't. That's the node enforcing the protocol. It isn't a matter
of opinion, and it isn't a vote. The protocol is clearly defined: you
either follow it or you're not running a Bitcoin node. If 51% don't
follow it tomorrow /they're/ not running Bitcoin.

Contrast with your "vote to reinterpret the meaning of arbitrary blocks"
mechaism - you're free to vote either way while remaining within the
protocol. That's a /real/ vote - majority decides what the Bitcoin
protocol /and every node that follows it/ will recognise as valid.
Nothing like that currently exists. Thank $deity.




--9WfBTFTM6mxSSVirKtmTGvSwQ2fekDwlB
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJTYPPWAAoJEEY5w2E3jkVEDPEH/38jqqPTvak+OIwsHUPaZ9od
ja5usk8i/vYdzLrTds35Uy2LyHUT9m8eTsQ1W9y7vkRdPKysXfWYYXa2suyJLt8x
xX6pADQKP0yBLKBhH+ScIgl7RV9UbZ+n4T82Biw3Ehx1UopH+101ey5JqR50Uwvk
uBX91Y2/U5AtgtePikqH4PBCkHKngoZjL1sy6k3dHFLZT/766nCwslrA24QHSXbc
aL8Eo1X9TqgwcqqI+zk/cBoe85cT4I3+gTrmr20xunB2mHGa2A6th7aVY9nZOv+b
IuSnRdEbOengvu1FiEF1C2M3gTIFqiz6U2VIrFMO/UKRK1jQTUxLikklZqh1JIE=
=AZIt
-----END PGP SIGNATURE-----

--9WfBTFTM6mxSSVirKtmTGvSwQ2fekDwlB--