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
|
Return-Path: <dave@hashingit.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 5E4228EA
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 7 Aug 2015 20:33:21 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from heron.directrouter.co.uk (heron.directrouter.co.uk
[89.145.69.228])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 2ED20A8
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 7 Aug 2015 20:33:20 +0000 (UTC)
Received: from [104.129.194.86] (port=43837 helo=[172.26.10.200])
by heron.directrouter.co.uk with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256)
(Exim 4.85) (envelope-from <dave@hashingit.com>)
id 1ZNoKM-000uLp-2k; Fri, 07 Aug 2015 20:33:18 +0000
Content-Type: multipart/alternative;
boundary="Apple-Mail=_35E943FA-9B83-4432-8908-20E293D65D66"
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2102\))
From: Dave Hudson <dave@hashingit.com>
In-Reply-To: <CAF_2MyXumMsx2nzpoxkGZjXarj6tbAsm+37RwPs-nsi+zaUdGw@mail.gmail.com>
Date: Fri, 7 Aug 2015 16:33:16 -0400
Message-Id: <2A22EA31-4261-4C89-AECD-F3A3E0260930@hashingit.com>
References: <CABsx9T16fH+56isq95m4+QWsKwP==tf75ep8ghnEcBoV4OtZJA@mail.gmail.com>
<CAPg+sBgOt=qhQVZv5P-4mcD75=L4PKgOfRqhyB6FZdSYQajrwQ@mail.gmail.com>
<CABsx9T10y6-=c7Qg6jysnf38wRX3NA3wWozxGfE+mEYJvPeqWA@mail.gmail.com>
<CAPg+sBiaT-2sjedA1mLOQo+q7=DjJ2yRuy7E4Gb3Wn8R-DzRTQ@mail.gmail.com>
<CAF_2MyUtrBUnR6EN-mOOnDa+Xh9=2coo9GaUcaeHCREqfP7jxA@mail.gmail.com>
<CAOG=w-uOxD0qntS4zWibV-khUYfKkjbsf84DbFR9WGV=FqQYxQ@mail.gmail.com>
<CAF_2MyVoL7_7jPZX-aftfcjV59nCP1q5bOK-Xyn8JoqyqysXLg@mail.gmail.com>
<CAF_2MyUqf3Qf7aj6DXy81AycD7EoyZTMsHKih1yfvAmy1BS+wA@mail.gmail.com>
<CAOG=w-s6x57Ab6=Q47abD4aYaUb18OUnoNqGaX4s3Awb7tNQoA@mail.gmail.com>
<CAF_2MyXumMsx2nzpoxkGZjXarj6tbAsm+37RwPs-nsi+zaUdGw@mail.gmail.com>
To: Ryan Butler <rryananizer@gmail.com>
X-Mailer: Apple Mail (2.2102)
X-AntiAbuse: This header was added to track abuse,
please include it with any abuse report
X-AntiAbuse: Primary Hostname - heron.directrouter.co.uk
X-AntiAbuse: Original Domain - lists.linuxfoundation.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - hashingit.com
X-Get-Message-Sender-Via: heron.directrouter.co.uk: authenticated_id:
dave@hashingit.com
X-Source:
X-Source-Args:
X-Source-Dir:
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,HTML_MESSAGE
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: Fri, 07 Aug 2015 20:33:21 -0000
--Apple-Mail=_35E943FA-9B83-4432-8908-20E293D65D66
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset=us-ascii
> On 7 Aug 2015, at 16:17, Ryan Butler via bitcoin-dev =
<bitcoin-dev@lists.linuxfoundation.org> wrote:
>=20
> A raspberry pie 2 node on reasonable Internet connection with a =
reasonable hard drive can run a node with 8 or 20mb blocks easily.
>=20
I'm curious as I've not seen any data on this subject. How fast can a =
RP2 do the necessary cryptographic calculations to validate blocks of =
various sizes?
While everyone tends to talk in terms of 10 minutes per block that is, =
of course, only a typical time and doesn't account for situations in =
which 2 or more blocks are found in quick succession (which, of course, =
happens on a daily basis). At what point does, say, an RP2 node fail to =
be able to validate a second or third block because it's still not =
finished processing the first?
If someone were to be playing games with the system and mining =
transactions without first broadcasting them to the network then how =
long would that take? This would in essence define the ability to DoS =
lower-performance nodes (ignoring all of the other usual considerations =
such as bandwidth, etc).
--Apple-Mail=_35E943FA-9B83-4432-8908-20E293D65D66
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
charset=us-ascii
<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D""><br class=3D""><div><blockquote type=3D"cite" class=3D""><div =
class=3D"">On 7 Aug 2015, at 16:17, Ryan Butler via bitcoin-dev <<a =
href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" =
class=3D"">bitcoin-dev@lists.linuxfoundation.org</a>> wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><p dir=3D"ltr" =
class=3D"">A raspberry pie 2 node on reasonable Internet connection with =
a reasonable hard drive can run a node with 8 or 20mb blocks =
easily.</p></div></blockquote>I'm curious as I've not seen any data on =
this subject. How fast can a RP2 do the necessary cryptographic =
calculations to validate blocks of various sizes?</div><div><br =
class=3D""></div><div>While everyone tends to talk in terms of 10 =
minutes per block that is, of course, only a typical time and doesn't =
account for situations in which 2 or more blocks are found in quick =
succession (which, of course, happens on a daily basis). At what point =
does, say, an RP2 node fail to be able to validate a second or third =
block because it's still not finished processing the =
first?</div><div><br class=3D""></div><div>If someone were to be playing =
games with the system and mining transactions without first broadcasting =
them to the network then how long would that take? This would in essence =
define the ability to DoS lower-performance nodes (ignoring all of the =
other usual considerations such as bandwidth, etc).</div><div><br =
class=3D""></div></body></html>=
--Apple-Mail=_35E943FA-9B83-4432-8908-20E293D65D66--
|
