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
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
|
Return-Path: <naama.kates@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 7E3DD233E
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 6 Oct 2015 19:34:42 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-pa0-f54.google.com (mail-pa0-f54.google.com
[209.85.220.54])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id E768D1A7
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 6 Oct 2015 19:34:41 +0000 (UTC)
Received: by pacex6 with SMTP id ex6so219035196pac.0
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 06 Oct 2015 12:34:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
h=content-type:mime-version:subject:from:in-reply-to:date:cc
:content-transfer-encoding:message-id:references:to;
bh=SALzjjJ+0EBE3QRqAQtuVpQ7pbKixJmKQzZQqWslSsM=;
b=rG/nejcuP+/CXH6fY5C6ObwmxDjyK5ElkxeafOir1UZFdXzF1p5nGu8AYFg66wclRn
Pv+tYz1FWhsnzORuin1XODONsScmQggd/+YhKOQm6VhHmwF8o4TPlvBWacTrsLw1qVvK
gHljWy6eLtNe0tHTjsx+yf7V41EY/ozzcFQOU1wUZK+rDXKsdHzqA8QDXNnH/nafoNce
//OyG20nGA8o0UkT9vopUL4mVL/9MPs8b73jRpquSibyMFWQe/3bZOA5lfjzRChnGdRs
NgkXJjql5twwX+wcRMv5AKsujoq0/aNbOE/qmr+ZOcjhY53ekzBvll3fIFZbYzfQ+9uN
pvRA==
X-Received: by 10.68.183.5 with SMTP id ei5mr49471689pbc.124.1444160081648;
Tue, 06 Oct 2015 12:34:41 -0700 (PDT)
Received: from [192.168.2.6] (cpe-76-91-152-174.socal.res.rr.com.
[76.91.152.174]) by smtp.gmail.com with ESMTPSA id
or6sm35187412pac.32.2015.10.06.12.34.40
(version=TLSv1/SSLv3 cipher=OTHER);
Tue, 06 Oct 2015 12:34:40 -0700 (PDT)
Content-Type: text/plain;
charset=utf-8
Mime-Version: 1.0 (1.0)
From: naama.kates@gmail.com
X-Mailer: iPhone Mail (12A405)
In-Reply-To: <561412D9.3050603@mail.bihthai.net>
Date: Tue, 6 Oct 2015 12:34:39 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <9C7B3D81-76FC-4893-8166-A184C1614D31@gmail.com>
References: <CAKzdR-rPoByn=+CgsTc1ZnLkjwtYyJnbQLbn-VHOvz0dLciefQ@mail.gmail.com>
<CA+w+GKSNa3TWgHXrp3=3gXdAbE6vVjW_uzus3_2YG9gzKJSskg@mail.gmail.com>
<561411A5.4020905@mail.bihthai.net>
<561412D9.3050603@mail.bihthai.net>
To: "venzen@mail.bihthai.net" <venzen@mail.bihthai.net>
X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, MIME_QP_LONG_LINE,
RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
Cc: "bitcoin-dev@lists.linuxfoundation.org"
<bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] This thread is not about the soft/hard fork
technical debate
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: Tue, 06 Oct 2015 19:34:42 -0000
Hey all, nice to meet you... I'm new to the community and thus, after taking=
that first step of signing up, have been reading/scanning these threads ove=
r the last few days without contributing my own two =C2=A2-- not, um, 'troll=
ing', just, you know, educating myself and getting familiar with the group e=
thos and etiquette. =20
It wasn't until I'd read ~10 posts that I understood the initial purpose of=
the thread! As few others have mentioned, I'm a bit surprised, at all the b=
ack and forth =C3=A0 la hip-hop 'battling' ;-) It certainly obfuscates-- whi=
le entertaining-- to the point where a newbie like myself might drop out... P=
erhaps this is intentional-- to maintain exclusivity and weed out the uninit=
iated. I dunno. But if not, I'm just noting, as something of an outsider, t=
hat it took a while.
But I'd like to contribute. With what little knowledge I possess, I'm incli=
ned to favor hardfork... Is there a more suitable place to address this? Pe=
rhaps to work on code? For this specific project, that is... Anyone point m=
e to a map somewhere? LOL.
Thanks to all for reading, and much admiration to you all and the work you'v=
e done, my latter comments notwithstanding! =20
Cheers,
N
> On Oct 6, 2015, at 11:28 AM, Venzen Khaosan via bitcoin-dev <bitcoin-dev@l=
ists.linuxfoundation.org> wrote:
>=20
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>=20
> That's for Mike Hearn. Sooner the better. Hong Kong, December?
> Venzen Khaosan
>=20
>=20
>> On 10/07/2015 01:23 AM, Venzen Khaosan via bitcoin-dev wrote:
>> Tell you what, eloquent guy...
>>=20
>> Give me 15 minutes in a public open mic session with you and i'll=20
>> remove you from your high horse and close your voice in Bitcoin,
>> for good.
>>=20
>> Guaranteed. You're too stupid for me to let you run loose with
>> client funds and this great innovation.
>>=20
>> Anytime, anywhere. I'm ready to dismantle your intellectual
>> bankruptcy in front of the world.
>>=20
>> I'll go for your psychological throat first.
>>=20
>> Sincerely, Venzen Khaosan.
>>=20
>>=20
>>=20
>>> On 10/05/2015 11:56 PM, Mike Hearn via bitcoin-dev wrote:
>>> Hey Sergio,
>>=20
>>> To clarify: my /single/ objection is that CLTV should be a hard=20
>>> fork. I haven't been raising never-ending technical objections,=20
>>> there's only one.
>>=20
>>> I /have/ been answering all the various reasons being brought up=20
>>> why I'm wrong and soft forks are awesome .... and there do seem
>>> to be a limitless number of such emails .... but on my side it's
>>> still just a single objection. If CLTV is a hard fork then I
>>> won't be objecting anymore, right?
>>=20
>>> CLTV deployment is clearly controversial. Many developers other=20
>>> than me have noted that hard forks are cleaner, and have other=20
>>> desirable properties. I'm not the only one who sees a big
>>> question mark over soft forks.
>>=20
>>> As everyone in the Bitcoin community has been clearly told that=20
>>> controversial changes to the consensus rules must not happen,
>>> it's clear that CLTV cannot happen in its current form.
>>=20
>>> Now I'll be frank - you are quite correct that I fully expect
>>> the Core maintainers to ignore this controversy and do CLTV as a
>>> soft fork anyway. I'm a cynic. I don't think "everyone must
>>> agree" is workable and have said so from the start. Faced with a
>>> choice of going back on their public statements or having to make
>>> changes to something they clearly want, I expect them to redefine
>>> what "real consensus" means. I hope I'm wrong, but if I'm not
>>> ..... well, at least everyone will see what Gavin and I have been
>>> talking about for so many months.
>>=20
>>> But I'd rather the opcode is tweaked. There's real financial
>>> risks to a soft fork.
>>=20
>>=20
>>> _______________________________________________ bitcoin-dev
>>> mailing list bitcoin-dev@lists.linuxfoundation.org=20
>>> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>>=20
>> _______________________________________________ bitcoin-dev mailing
>> list bitcoin-dev@lists.linuxfoundation.org=20
>> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.22 (GNU/Linux)
>=20
> iQEcBAEBAgAGBQJWFBLWAAoJEGwAhlQc8H1mRM8H/0p2sz0gtu62bB+NrllRgU20
> C4imzMr904X7JicqDsGhtySGdyk8DuHBSK4k1A3pOgPb+DoNQhcOUfZ2ZTNgR2tT
> yjJHrJP2X+g8YixyQiQNBf65bogTgeBGEizh/H33RSGzdHwoIfeVS5Qja/AMUnk1
> 4XO8d+t5OdtYdKANmR/uUZikrnOXd6KIt9rmJhYUjqmLWXbHzQkhES0mFvJ1BdVZ
> ZHNjnWzoE74NAEmPqhhhtU/GCFKQhBq7HHAnqkMoeWk0mgJoGCc+b/4/PwchmUJq
> CmVO2TJFrnHb4tYAFgw14tdbSe5ERYT0pHW4qM3gJlYL1ik03k0iQDZZ0eStaXM=3D
> =3Dbwvw
> -----END PGP SIGNATURE-----
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
|
