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
|
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 <boydb@midnightdesign.ws>) id 1Z5vCN-0001Ez-VY
for bitcoin-development@lists.sourceforge.net;
Fri, 19 Jun 2015 12:15:07 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of
midnightdesign.ws designates 50.87.144.70 as permitted sender)
client-ip=50.87.144.70; envelope-from=boydb@midnightdesign.ws;
helo=gator3054.hostgator.com;
Received: from gator3054.hostgator.com ([50.87.144.70])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256)
(Exim 4.76) id 1Z5vCM-00018k-7H
for bitcoin-development@lists.sourceforge.net;
Fri, 19 Jun 2015 12:15:07 +0000
Received: from [209.85.160.181] (port=35587 helo=mail-yk0-f181.google.com)
by gator3054.hostgator.com with esmtpsa (UNKNOWN:AES128-GCM-SHA256:128)
(Exim 4.82) (envelope-from <boydb@midnightdesign.ws>)
id 1Z5un2-000145-Nq for bitcoin-development@lists.sourceforge.net;
Fri, 19 Jun 2015 06:48:56 -0500
Received: by ykar6 with SMTP id r6so89534131yka.2
for <bitcoin-development@lists.sourceforge.net>;
Fri, 19 Jun 2015 04:48:54 -0700 (PDT)
X-Gm-Message-State: ALoCoQnIGrTWPzmfOd255EUUzh7vMHgkzNCNnL5ycq4UbKec1R8LRtIB4rGegLWQmtyDBFNJekVg
MIME-Version: 1.0
X-Received: by 10.52.181.196 with SMTP id dy4mr12318388vdc.67.1434714534723;
Fri, 19 Jun 2015 04:48:54 -0700 (PDT)
Received: by 10.31.232.65 with HTTP; Fri, 19 Jun 2015 04:48:54 -0700 (PDT)
In-Reply-To: <CANEZrP33GCiZHK1GV2Qt_R_AHK6SEjybGPtmORjqgvQ9MiYVZQ@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>
<CAOG=w-tf7qz9XSkDg5POKtFLkHWDA==jf2iVxVL8wz1hqcAVOg@mail.gmail.com>
<CANEZrP33GCiZHK1GV2Qt_R_AHK6SEjybGPtmORjqgvQ9MiYVZQ@mail.gmail.com>
Date: Fri, 19 Jun 2015 06:48:54 -0500
Message-ID: <CANg-TZBL-d4L6+kP7CGi89QkYtFEk4kGZZqB-5jp5K5Cm8nEZQ@mail.gmail.com>
From: Brooks Boyd <boydb@midnightdesign.ws>
To: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Content-Type: multipart/alternative; boundary=bcaec5485aba325bc60518dd82c6
X-AntiAbuse: This header was added to track abuse,
please include it with any abuse report
X-AntiAbuse: Primary Hostname - gator3054.hostgator.com
X-AntiAbuse: Original Domain - lists.sourceforge.net
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - midnightdesign.ws
X-BWhitelist: no
X-Source-IP: 209.85.160.181
X-Exim-ID: 1Z5un2-000145-Nq
X-Source:
X-Source-Args:
X-Source-Dir:
X-Source-Sender: (mail-yk0-f181.google.com) [209.85.160.181]:35587
X-Source-Auth: midnight
X-Email-Count: 0
X-Source-Cap: bWlkbmlnaHQ7bWlkbmlnaHQ7Z2F0b3IzMDU0Lmhvc3RnYXRvci5jb20=
X-Spam-Score: -0.5 (/)
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 SPF_HELO_PASS SPF: HELO matches SPF record
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
X-Headers-End: 1Z5vCM-00018k-7H
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: Fri, 19 Jun 2015 12:15:08 -0000
--bcaec5485aba325bc60518dd82c6
Content-Type: text/plain; charset=UTF-8
On Fri, Jun 19, 2015 at 4:37 AM, Mike Hearn <mike@plan99.net> wrote:
> Or alternatively, fix the reasons why users would have negative
>> experiences with full blocks
>>
>
> It's impossible, Mark. *By definition* if Bitcoin does not have
> sufficient capacity for everyone's transactions, some users who were using
> it will be kicked out to make way for the others. Whether that happens in
> some kind of stable organised way or (as with the current code) a fairly
> chaotic way doesn't change the fundamental truth: *some users will find
> their bitcoin savings have become uneconomic to spend*.
>
> Here's a recent user complaint that provides a preview of coming
> attractions:
>
>
> https://www.reddit.com/r/Bitcoin/comments/39r3bi/breadwallet_asking_me_to_pay_over_10_network_fee/
>
> Hello, I'm just trying to send my small Sarutobi-tips stash (12,159 bits)
>> onto a paper wallet. When I try to send it, a window pops up stating
>> "insufficient funds for bitcoin network fee, reduce payment amount by 1,389
>> bits?" This would be a fee of $0.32 to send my $2.82, leaving me with $2.50.
>
>
>
Has there been any talk about reducing the time between blocks? If blocks
were allowed to come twice as fast, they would be able to clear pending
transactions in the mempool the same as if the block size doubled, but
would allow mining to stay more decentralized since miners wouldn't be
working on such large-scale blocks? It would still take more storage space
to store the blockchain, though.
Brooks
--bcaec5485aba325bc60518dd82c6
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On F=
ri, Jun 19, 2015 at 4:37 AM, Mike Hearn <span dir=3D"ltr"><<a href=3D"ma=
ilto:mike@plan99.net" target=3D"_blank">mike@plan99.net</a>></span> wrot=
e:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-l=
eft:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div class=3D"gmail_e=
xtra"><div class=3D"gmail_quote"><span class=3D""><blockquote class=3D"gmai=
l_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-lef=
t-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir=
=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><div>Or alte=
rnatively, fix the reasons why users would have negative experiences with f=
ull blocks</div></div></div></div></blockquote><div><br></div></span><div>I=
t's impossible, Mark. <i>By definition</i>=C2=A0if Bitcoin does not hav=
e sufficient capacity for everyone's transactions, some users who were =
using it will be kicked out to make way for the others. Whether that happen=
s in some kind of stable organised way or (as with the current code) a fair=
ly chaotic way doesn't change the fundamental truth: <b>some users will=
find their bitcoin savings have become uneconomic to spend</b>.</div><div>=
<b><br></b></div><div>Here's a recent user complaint that provides a pr=
eview of coming attractions:</div><div><br></div><div><a href=3D"https://ww=
w.reddit.com/r/Bitcoin/comments/39r3bi/breadwallet_asking_me_to_pay_over_10=
_network_fee/" target=3D"_blank">https://www.reddit.com/r/Bitcoin/comments/=
39r3bi/breadwallet_asking_me_to_pay_over_10_network_fee/</a><br></div><div>=
<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8=
ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-sty=
le:solid;padding-left:1ex"><span style=3D"font-family:Verdana,arial,sans-se=
rif;font-size:14px;line-height:18.2000007629395px">Hello, I'm just tryi=
ng to send my small Sarutobi-tips stash (12,159 bits) onto a paper wallet. =
When I try to send it, a window pops up stating "insufficient funds fo=
r bitcoin network fee, reduce payment amount by 1,389 bits?" This woul=
d be a fee of $0.32 to send my $2.82, leaving me with $2.50.</span></blockq=
uote><div><br></div></div></div></div></blockquote><div><br></div><div>Has =
there been any talk about reducing the time between blocks? If blocks were =
allowed to come twice as fast, they would be able to clear pending transact=
ions in the mempool the same as if the block size doubled, but would allow =
mining to stay more decentralized since miners wouldn't be working on s=
uch large-scale blocks? It would still take more storage space to store the=
blockchain, though.</div><div><br></div><div>Brooks</div></div></div></div=
>
--bcaec5485aba325bc60518dd82c6--
|
