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
|
Return-Path: <jtimon@jtimon.cc>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id D01CC8A6
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 12 Aug 2015 09:00:33 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-wi0-f174.google.com (mail-wi0-f174.google.com
[209.85.212.174])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 1A2B089
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 12 Aug 2015 09:00:31 +0000 (UTC)
Received: by wicne3 with SMTP id ne3so91521148wic.0
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 12 Aug 2015 02:00:30 -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:date
:message-id:subject:from:to:cc:content-type;
bh=oUHHxrDErs9B3aMuA/N+9LqmKMFOi02wUvgopk4MA/g=;
b=F8myle9ivRd9OhVQltu8ukgZP0rIHXKc2zl8LO2MBOgEFuw1pt3V208iGUbiXZqVgF
UWbr867bbWBSE+woTVGxD9z+EnCCLSU1NksJsAi9CgvN5iC0I56WDDy+82uA+S3aPJgQ
l/LQLlRnYjNq9K+rvxCHUtjkdN9mAdqfDISqlWIr8BXSzI2JMAOlr4RSddTx0BSZPhq/
x7Lgu4RApDlqODtr0I1RDanNF4HxJ6sjXTCAsMB2BzSczH2X829VuE5n/X9dSN2m1za4
8Z4cNUbYfD9DNYTlxL63y1+OP2HPA3jRkBbnLLnPrOXHKx1QG3sV/OnuPN1I/3PZD+tX
XrnQ==
X-Gm-Message-State: ALoCoQnNVbktZVE4T1eMpHjDcU5TSdiCaR1hg3uRZcVAgpyB3EL/vEVOhgk9aHQBSYFc47Ai9/0W
MIME-Version: 1.0
X-Received: by 10.180.8.135 with SMTP id r7mr46042899wia.58.1439370030139;
Wed, 12 Aug 2015 02:00:30 -0700 (PDT)
Received: by 10.194.31.230 with HTTP; Wed, 12 Aug 2015 02:00:29 -0700 (PDT)
Received: by 10.194.31.230 with HTTP; Wed, 12 Aug 2015 02:00:29 -0700 (PDT)
In-Reply-To: <3295391.2gkoFVhbEs@pluto>
References: <CABsx9T16fH+56isq95m4+QWsKwP==tf75ep8ghnEcBoV4OtZJA@mail.gmail.com>
<CALgxB7sLsod9Kb-pwxGwCtPpWXsUusDE1nJ7p4nbFMG8mDWFtg@mail.gmail.com>
<CAPg+sBjGVk1jHraLZTroRneL6L1HxZ-bTGaLNwakcDSDDHqauA@mail.gmail.com>
<3295391.2gkoFVhbEs@pluto>
Date: Wed, 12 Aug 2015 11:00:29 +0200
Message-ID: <CABm2gDoEeeAt1NWCRc7Z6Dd6ft_fS82J=JbWBb-d=g5KYpJA6Q@mail.gmail.com>
From: =?UTF-8?B?Sm9yZ2UgVGltw7Nu?= <jtimon@jtimon.cc>
To: Thomas Zander <thomas@thomaszander.se>
Content-Type: multipart/alternative; boundary=f46d0418271e58dfaa051d1973b4
X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,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: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Fees and the block-finding process
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: Wed, 12 Aug 2015 09:00:34 -0000
--f46d0418271e58dfaa051d1973b4
Content-Type: text/plain; charset=UTF-8
On Aug 12, 2015 10:11 AM, "Thomas Zander via bitcoin-dev" <
bitcoin-dev@lists.linuxfoundation.org> wrote:
>
> On Tuesday 11. August 2015 21.51.59 Pieter Wuille via bitcoin-dev wrote:
> > If people are doing transactions despite being unreliable, there
> > must be a use for them.
>
> Thats one usage of the form unreliable.
> Yes, if people start getting their transactions thrown out because of full
> blocks or full memory pools, then its unreliable to send stuff.
>
> Much more importantly is the software is unreliable at such loads. Bitcoin
> core will continue to grow in memory consumption, and eventually crash.
Or,
> worse, crash the system its running on.
> We know of some issues in the software with regards to running at > 100%
> capacity, I'm sure we'll find more when it actually happens.
Don't fear this happening at 1 MB, fear this happening at any size. This
needs to be solved regardless of the block size.
Don't worry, the "doing nothing side" is already taking care of this. I
will give the link for the second time...
https://github.com/bitcoin/bitcoin/pull/6470
--f46d0418271e58dfaa051d1973b4
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<p dir=3D"ltr"><br>
On Aug 12, 2015 10:11 AM, "Thomas Zander via bitcoin-dev" <<a =
href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-dev@lists.lin=
uxfoundation.org</a>> wrote:<br>
><br>
> On Tuesday 11. August 2015 21.51.59 Pieter Wuille via bitcoin-dev wrot=
e:<br>
> >=C2=A0 If people are doing transactions despite being unreliable, =
there<br>
> > must be a use for them.<br>
><br>
> Thats one usage of the form unreliable.<br>
> Yes, if people start getting their transactions thrown out because of =
full<br>
> blocks or full memory pools, then its unreliable to send stuff.<br>
><br>
> Much more importantly is the software is unreliable at such loads. Bit=
coin<br>
> core will continue to grow in memory consumption, and eventually crash=
. Or,<br>
> worse, crash the system its running on.<br>
> We know of some issues in the software with regards to running at >=
100%<br>
> capacity, I'm sure we'll find more when it actually happens.</=
p>
<p dir=3D"ltr">Don't fear this happening at 1 MB, fear this happening a=
t any size. This needs to be solved regardless of the block size.<br>
Don't worry, the "doing nothing side" is already taking care =
of this. I will give the link for the second time...</p>
<p dir=3D"ltr"><a href=3D"https://github.com/bitcoin/bitcoin/pull/6470">htt=
ps://github.com/bitcoin/bitcoin/pull/6470</a></p>
--f46d0418271e58dfaa051d1973b4--
|
