summaryrefslogtreecommitdiff
path: root/b7/7336df264ec2d7d5793e81b7bbc51b3dccad92
blob: b15816f07152d6e97286d7593c91010f34ce9a44 (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
Return-Path: <jgarzik@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
	[172.17.192.35])
	by mail.linuxfoundation.org (Postfix) with ESMTPS id A5D97F89
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Thu, 17 Dec 2015 02:58:36 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-ig0-f174.google.com (mail-ig0-f174.google.com
	[209.85.213.174])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 411DE16F
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Thu, 17 Dec 2015 02:58:36 +0000 (UTC)
Received: by mail-ig0-f174.google.com with SMTP id ph11so2221072igc.1
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Wed, 16 Dec 2015 18:58:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type;
	bh=M1qd+Ni4sdXYL/UM5+EFhyPy2zNZ/4n+t4WH5FkN2Og=;
	b=RViuStzflDQmEQCBz3hBkkdNfhQOvRvCR4tCbvAKLNeb/8n/cnDdt2NLfvD1zv4M5g
	O4lf3idhkEb2JcJ1L/rQ7iIrb5iVGILvHu+XeGqQZw7ulHFBUBvCdeiA8NU9oVL1h+Zx
	niSFkMYnbz1n+ikPLL0MmUpLRPyH2XonqYw1dIZHZUZregAtBWleJe9mMoLd1Ir4uzKx
	Y4WLz8i9chceBrccT46wY81AQZSrmPFeF3Ex7b1WJ3pcL0thZxCiyRCZjLj+RKunPTNM
	jAtfIhN46fIAIuAZFPTXe4Ne/NGlk74tqo/9YeKzOjUyMSjDFCZLW27mGRbMreZPtkLE
	sR4Q==
MIME-Version: 1.0
X-Received: by 10.50.111.193 with SMTP id ik1mr1133403igb.23.1450321115750;
	Wed, 16 Dec 2015 18:58:35 -0800 (PST)
Received: by 10.79.8.198 with HTTP; Wed, 16 Dec 2015 18:58:35 -0800 (PST)
In-Reply-To: <FC95D096-74AE-4B1C-B11B-1CB718538E7D@gmail.com>
References: <CADm_WcYWh5EnBCzQQVc04sf-0seh2zrmc+5dH8Z-Bo78jhPnfA@mail.gmail.com>
	<49257841-66C8-4EF7-980B-73DC604CA591@mattcorallo.com>
	<CADm_WcYdAHP95mrxH0CjvxKaV12rXEdBXf-L5QtKHuBL1ndFaQ@mail.gmail.com>
	<FC95D096-74AE-4B1C-B11B-1CB718538E7D@gmail.com>
Date: Wed, 16 Dec 2015 21:58:35 -0500
Message-ID: <CADm_WcYhPqZZ5KQ7DxyFgkk5td4ircrXwArg_guWDPWPtnCxhw@mail.gmail.com>
From: Jeff Garzik <jgarzik@gmail.com>
To: Eric Lombrozo <elombrozo@gmail.com>
Content-Type: multipart/alternative; boundary=047d7b3a9c14ea289505270f326c
X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,HTML_MESSAGE,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: Jeff Garzik via bitcoin-dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Segregated Witness in the context of Scaling
	Bitcoin
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: Thu, 17 Dec 2015 02:58:36 -0000

--047d7b3a9c14ea289505270f326c
Content-Type: text/plain; charset=UTF-8

On Wed, Dec 16, 2015 at 9:44 PM, Eric Lombrozo <elombrozo@gmail.com> wrote:

> At least SW *is* a scaling solution (albeit most of the important benefits
> are long term). The issue of fee events has nothing to do with scaling - it
> has to do with economics...specifically whether we should be subsidizing
> transactions, who should pay the bill for it, etc. My own personal opinion
> is that increasing validation costs works against adoption, not for
> it...even if it artificially keeps fees low - and we'll have to deal with a
> fee event sooner or later anyhow. You may disagree with my opinion, but
> please, let's stop confounding the economic issues with actual scaling.
>

At least on my part, the title of the 1st email was "It's economics & ..."
and focused on (a) economics and (b) transition issues.  There was no
confounding.  There was a list of real problems and risks taken when 1M is
not lifted in the short term.

Thus "SW is orthogonal" in these emails, because these problems remain
regardless of SW or no, as the 1st email outlined.

The 2nd email addresses the specific assertion of "no 1M hard fork needed,
because SW."

--047d7b3a9c14ea289505270f326c
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Wed, Dec 16, 2015 at 9:44 PM, Eric Lombrozo <span dir=
=3D"ltr">&lt;<a href=3D"mailto:elombrozo@gmail.com" target=3D"_blank">elomb=
rozo@gmail.com</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"><div cla=
ss=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex"><div>At least SW *is* a s=
caling solution (albeit most of the important benefits are long term). The =
issue of fee events has nothing to do with scaling - it has to do with econ=
omics...specifically whether we should be subsidizing transactions, who sho=
uld pay the bill for it, etc. My own personal opinion is that increasing va=
lidation costs works against adoption, not for it...even if it artificially=
 keeps fees low - and we&#39;ll have to deal with a fee event sooner or lat=
er anyhow. You may disagree with my opinion, but please, let&#39;s stop con=
founding the economic issues with actual scaling.<br></div></blockquote><di=
v><br></div><div>At least on my part, the title of the 1st email was &quot;=
It&#39;s economics &amp; ...&quot; and focused on (a) economics and (b) tra=
nsition issues.=C2=A0 There was no confounding.=C2=A0 There was a list of r=
eal problems and risks taken when 1M is not lifted in the short term.</div>=
<div><br></div><div>Thus &quot;SW is orthogonal&quot; in these emails, beca=
use these problems remain regardless of SW or no, as the 1st email outlined=
.</div><div><br></div><div>The 2nd email addresses the specific assertion o=
f &quot;no 1M hard fork needed, because SW.&quot;</div><div><br></div><div>=
<br></div></div></div></div>

--047d7b3a9c14ea289505270f326c--