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
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <mark@friedenbach.org>) id 1Z5iNF-0004oR-F2
for bitcoin-development@lists.sourceforge.net;
Thu, 18 Jun 2015 22:33:29 +0000
X-ACL-Warn:
Received: from mail-ig0-f178.google.com ([209.85.213.178])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Z5iNC-0004Oz-Q2
for bitcoin-development@lists.sourceforge.net;
Thu, 18 Jun 2015 22:33:29 +0000
Received: by igblz2 with SMTP id lz2so1940738igb.1
for <bitcoin-development@lists.sourceforge.net>;
Thu, 18 Jun 2015 15:33:21 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:mime-version:in-reply-to:references:from:date
:message-id:subject:to:cc:content-type;
bh=4ybQTEN7Nei36eZrOtrf3SE8nfGsfB5YeD+TXB6ETzA=;
b=l6FHnqoFp50HHpEzjjYLr3q73e0+otq/9Scv3rN5xn+6eOvsP5hYLJqeT6idOgokxL
lvqlr6ZjfGEeEBg62WnVP/C/tSslxQ5Sug9P7DsL5Uutg/KBKcF6O29lq5qCXSnx9eFM
rA8k4jVUF6WQWJpMOK39DmDYM/JqlaJ1nv0y/GuxQF3LsnD8EeCyccIbjW7WULsqCiN6
wC2xZiPzPeI8xaI/f2K3dIcSCGAf8Pu0pXFV9c6s8EAy9zEe4R4ySqlAN7elCOITUHJN
gUTFQOmQg2ki6QPKwju8Ub0N3jNG+dgyDpI/dG9jqm8gLm6/QPnZ4AUqdsnJgvdyA7xU
9X9A==
X-Gm-Message-State: ALoCoQk3RqU4apPvwNQwN3xi8IFR4hM1S8JiXmbDcBAr5OGG844cE0RIR/uWWCE4pm4iUBGTYoRC
X-Received: by 10.107.37.69 with SMTP id l66mr18264011iol.76.1434666801410;
Thu, 18 Jun 2015 15:33:21 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.107.149.20 with HTTP; Thu, 18 Jun 2015 15:33:00 -0700 (PDT)
X-Originating-IP: [24.4.96.213]
In-Reply-To: <CAJHLa0Mhnma8_ys2ckEA+dLT-EWnqO4j8YKMSaf3Tvv_K14czQ@mail.gmail.com>
References: <55828737.6000007@riseup.net>
<CABm2gDoa7KxsgvREo3yiNjfd6AeayqAqkjMe2rvX8yyxR_ddcA@mail.gmail.com>
<55831CAB.2080303@jrn.me.uk> <1867667.WXWC1C9quc@crushinator>
<CAOG=w-scXm-46sp2NgR2UUp20R5ujuaAzW-jU_Owh20C4Xc=9A@mail.gmail.com>
<CAJHLa0Mhnma8_ys2ckEA+dLT-EWnqO4j8YKMSaf3Tvv_K14czQ@mail.gmail.com>
From: Mark Friedenbach <mark@friedenbach.org>
Date: Thu, 18 Jun 2015 15:33:00 -0700
Message-ID: <CAOG=w-tf7qz9XSkDg5POKtFLkHWDA==jf2iVxVL8wz1hqcAVOg@mail.gmail.com>
To: Jeff Garzik <jgarzik@bitpay.com>
Content-Type: multipart/alternative; boundary=001a1140ea0211caa10518d265d1
X-Spam-Score: 1.0 (+)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
1.0 HTML_MESSAGE BODY: HTML included in message
X-Headers-End: 1Z5iNC-0004Oz-Q2
Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>,
Gavin Andresen <gavin@bitcoinfoundation.org>
Subject: Re: [Bitcoin-development] Concerns Regarding Threats by a Developer
to Remove Commit Access from Other Developers
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: Thu, 18 Jun 2015 22:33:29 -0000
--001a1140ea0211caa10518d265d1
Content-Type: text/plain; charset=UTF-8
On Thu, Jun 18, 2015 at 2:58 PM, Jeff Garzik <jgarzik@bitpay.com> wrote:
>
> The whole point is getting out in front of the need, to prevent
> significant negative impact to users when blocks are consistently full.
>
> To do that, you need to (a) plan forward, in order to (b) set a hard fork
> date in the future.
>
Or alternatively, fix the reasons why users would have negative experiences
with full blocks, chiefly:
* Get safe forms of replace-by-fee and child-pays-for-parent finished and
in 0.12.
* Develop cross-platform libraries for managing micropayment channels,
and get wallet authors to adopt
* Use fidelity bonds, solvency proofs, and other tricks to minimize the
risk of already deployed off-chain solutions as an interim measure until:
* Deploy soft-fork changes for truly scalable solutions like Lightning
Network.
Not raising the block size limit does not mean doing nothing to solve the
problem.
--001a1140ea0211caa10518d265d1
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">On Thu, Jun 18, 2015 at 2:58 PM, Jeff Garzik <span dir=3D"=
ltr"><<a href=3D"mailto:jgarzik@bitpay.com" target=3D"_blank">jgarzik@bi=
tpay.com</a>></span> wrote:<br><div class=3D"gmail_extra"><div class=3D"=
gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;b=
order-left:1px #ccc solid;padding-left:1ex"><br><div dir=3D"ltr">The whole =
point is getting out in front of the need, to prevent significant negative =
impact to users when blocks are consistently full.<div><br></div><div>To do=
that, you need to (a) plan forward, in order to (b) set a hard fork date i=
n the future.</div></div></blockquote><div><br></div><div>Or alternatively,=
fix the reasons why users would have negative experiences with full blocks=
, chiefly:<br><br></div><div>=C2=A0 * Get safe forms of replace-by-fee and =
child-pays-for-parent finished and in 0.12.<br></div><div>=C2=A0 * Develop =
cross-platform libraries for managing micropayment channels, and get wallet=
authors to adopt <br></div><div>=C2=A0 * Use fidelity bonds, solvency proo=
fs, and other tricks to minimize the risk of already deployed off-chain sol=
utions as an interim measure until:<br></div><div>=C2=A0 * Deploy soft-fork=
changes for truly scalable solutions like Lightning Network.<br><br></div>=
<div>Not raising the block size limit does not mean doing nothing to solve =
the problem.<br></div></div><br></div></div>
--001a1140ea0211caa10518d265d1--
|
