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
|
Return-Path: <nbvfour@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 06D27DF2
for <bitcoin-dev@lists.linuxfoundation.org>;
Sat, 6 Feb 2016 20:22:32 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-io0-f174.google.com (mail-io0-f174.google.com
[209.85.223.174])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 74EAD166
for <bitcoin-dev@lists.linuxfoundation.org>;
Sat, 6 Feb 2016 20:22:31 +0000 (UTC)
Received: by mail-io0-f174.google.com with SMTP id d63so161581818ioj.2
for <bitcoin-dev@lists.linuxfoundation.org>;
Sat, 06 Feb 2016 12:22:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
h=mime-version:sender:in-reply-to:references:date:message-id:subject
:from:to:cc:content-type:content-transfer-encoding;
bh=CKCIXq7W7SEl8wv+V3qizA4BLixxmvzT/ExhmLXj5r4=;
b=D5RjCTefryM27/ALB9tKk/esERCqw1NITY+n0wBFSC8wWHJmvAsS/O5z8eMIdD6S8v
THOrPgCf2aVqmShdm910Wih3q4Fw46DYUQtWb0mdvFR6WYwt3Yek7fVkxuLAvmH0rnt5
yyqXCZhsohAkKA6GLmfsH5afj8em1ZqRqKzHiU9wgj35E5ekk62+fAaT7H1fvntSOmQV
7FNn6bUCFWP79qjaehGABcPALlSTNt3GoXQs+diUceW2aiUSMCY+37SgcBj+GMEjnXue
fxLhnwJHD3IulkUmTz8JM2TKzr3O9uNOaahiITEQM4+r/rjZnAckaiY+9vMyg1jX5Cre
b1+A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:mime-version:sender:in-reply-to:references:date
:message-id:subject:from:to:cc:content-type
:content-transfer-encoding;
bh=CKCIXq7W7SEl8wv+V3qizA4BLixxmvzT/ExhmLXj5r4=;
b=QMbATsVCa1898/JDiszALV2/X0kkgb7PoloIoE2BKKE2lTvTV29CRyY20y3erTIvVj
ESJ055yDFjLEUY7qVbflfWifr6g+TxvX3qSHRI2hE6cR7MSvvtYEWSBt63ZiLDk7u1jk
J8jA5sQ5eRm+UhuUujn7W21o8tW3+oI2Ltfhpr6uvu4fdrGocEmqV3LA0X6SWw3ASoLm
9fRELligjvuLo0fnZv7HtUSR1O/RHJCL0NT72dYQiNi+AAtlrtFDykxoOQGjFfLBh936
Ag9lQ/4j19GVgualWXvn1W10BUq1A21qBQuOdkrjVkru86wrTq3h9qV+Wn9OOPQ5zE5k
UerQ==
X-Gm-Message-State: AG10YOSzqBwF7b8cQwlV+NloPfQqgzrGbQLmc1RztcayXsUVpIe8vGctCM7YvmRGSIajea5cxS+7O7ooYCWBUQ==
MIME-Version: 1.0
X-Received: by 10.107.40.76 with SMTP id o73mr19655210ioo.157.1454790150987;
Sat, 06 Feb 2016 12:22:30 -0800 (PST)
Sender: nbvfour@gmail.com
Received: by 10.36.20.142 with HTTP; Sat, 6 Feb 2016 12:22:30 -0800 (PST)
In-Reply-To: <1804222.7gVHPiWqto@kiwi>
References: <CABsx9T1Bd0-aQg-9uRa4u3dGA5fKxaj8-mEkxVzX8mhdj4Gt2g@mail.gmail.com>
<CABsx9T2LuMZciXpMiY24+rPzhj1VT6j=HJ5STtnQmnfnA_XFUw@mail.gmail.com>
<CABm2gDoungCbB22_SKHcedBKegWEPpjeM2woxLGchC4=om8BrA@mail.gmail.com>
<1804222.7gVHPiWqto@kiwi>
Date: Sat, 6 Feb 2016 12:22:30 -0800
X-Google-Sender-Auth: uqOPIrwipS_QlO3Nuw67Pxg0EyU
Message-ID: <CAAcC9yvJw2t1vOFaxbiTREUwJNJeY8OjJf1TZ4LrOGBa4ZXRXA@mail.gmail.com>
From: Chris Priest <cp368202@ohiou.edu>
To: Tom Zander <tomz@freedommail.ch>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID, FREEMAIL_FROM, 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
X-Mailman-Approved-At: Sat, 06 Feb 2016 21:15:11 +0000
Cc: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] BIP proposal: Increase block size limit to 2
megabytes
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: Sat, 06 Feb 2016 20:22:32 -0000
Its mostly a problem for exchanges and miners. Those entities need to
be on the network 100% of the time because they are using the network
100% of the time. A normal wallet user isn't taking payments every few
minutes like the exchanges are. "Getting booted off the network" is
not something to worry about for normal wallet users.
If miners aren't up to date, that is the biggest problem. A sudden
drop in hashpower will effect the network for all users, including
normal wallet users (by them having to wait longer for confirmations).
Miners must not be booted off the network ever. Hashpower voting is
the best way to make sure this never happens.
On 2/6/16, Tom Zander via bitcoin-dev
<bitcoin-dev@lists.linuxfoundation.org> wrote:
> On Saturday, February 06, 2016 06:09:21 PM Jorge Tim=C3=B3n via bitcoin-d=
ev
> wrote:
>> None of the reasons you list say anything about the fact that "being
>> lost"
>> (kicked out of the network) is a problem for those node's users.
>
> That's because its not.
>
> If you have a node that is "old" your node will stop getting new blocks.
> The node will essentially just say "x-hours behind" with "x" getting larg=
er
>
> every hour. Funds don't get confirmed. etc.
>
> After upgrading the software they will see the new reality of the network=
.
>
> Nobody said its a problem, because its not.
>
> --
> Tom Zander
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
|
