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
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <gmaxwell@gmail.com>) id 1U5nDr-0000l5-CB
for bitcoin-development@lists.sourceforge.net;
Thu, 14 Feb 2013 01:02:47 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.215.51 as permitted sender)
client-ip=209.85.215.51; envelope-from=gmaxwell@gmail.com;
helo=mail-la0-f51.google.com;
Received: from mail-la0-f51.google.com ([209.85.215.51])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1U5nDq-0000ky-AK
for bitcoin-development@lists.sourceforge.net;
Thu, 14 Feb 2013 01:02:47 +0000
Received: by mail-la0-f51.google.com with SMTP id fo13so1802535lab.38
for <bitcoin-development@lists.sourceforge.net>;
Wed, 13 Feb 2013 17:02:39 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.112.45.201 with SMTP id p9mr9553528lbm.13.1360803759625;
Wed, 13 Feb 2013 17:02:39 -0800 (PST)
Received: by 10.112.96.164 with HTTP; Wed, 13 Feb 2013 17:02:39 -0800 (PST)
In-Reply-To: <CAAS2fgR5=nLTBQUBzjZQs91AVw5XSTiqe-KB_T9R9wKfBrOq6Q@mail.gmail.com>
References: <CAN1xFdrX61HsRxsXxXW+i0FzjQkoNVRaDG-2yJNOfYUi5FnsPA@mail.gmail.com>
<CAAS2fgTwjXCGFS-N8a8Ro80ahxXT01dCfqWYOqmwCkdRramaMg@mail.gmail.com>
<CAN1xFdrGiWmn_EaBNMXXZAV38oeqP14YiMzMZQrkA+WL9QEMfA@mail.gmail.com>
<CAAS2fgR5=nLTBQUBzjZQs91AVw5XSTiqe-KB_T9R9wKfBrOq6Q@mail.gmail.com>
Date: Wed, 13 Feb 2013 17:02:39 -0800
Message-ID: <CAAS2fgQGb1Tb=cma8_20_gWUQ+60v9v=UTt52RMGnztOx5-E3w@mail.gmail.com>
From: Gregory Maxwell <gmaxwell@gmail.com>
To: Raph Frank <raphfrk@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: -1.6 (-)
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 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(gmaxwell[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
author's domain
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1U5nDq-0000ky-AK
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Incorporating block validation rule
modifications into the block chain
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, 14 Feb 2013 01:02:47 -0000
On Wed, Feb 13, 2013 at 7:42 AM, Gregory Maxwell <gmaxwell@gmail.com> wrote=
:
> I hope that should it become necessary to do so that correct path will
> be obvious to everyone, otherwise there is a grave risk of undermining
> the justification for the confidence in the immutability of any of the
> rules of the system.
With all I wrote on the gloom side=E2=80=94 I thought I should elaborate ho=
w I
think that would work, assuming that my gloom isn't convincingly
disproven.
It's the year 2043=E2=80=94 the Y2038 problem is behind us and everyone is
beginning to forget how terrible it turned out to be=E2=80=94 By some amaz=
ing
chance Bitcoin still exists and is widely used. Off-chain system like
fidelity bonded banks are vibrant and widely used providing scalable
instant and completely private transactions to millions of people.
Someone posts to the infrequently used IETF Bitcoin working group with
a new draft=E2=80=94 It points out that the transaction load is high enough
that even with a 100x increase in block size completion for fees would
hardly be impacted and that=E2=80=94 because computers are 2^20 times faste=
r
per unit cost than they were in 2013=E2=80=94 and networks had made similar
gains, so even a common wristwatch (the personal computer embedded in
everyone's wrist at birth) could easily keep up with 100 megabyte
blocks.... so the size should be increased as of block 2,047,500.
The only objections are filed by some bearded hippy at the museum of
internet trolling (their authentic reconstruction of Diablo-D3's
desktop exhibit couldn't keep up), and by some dictatorship who again
insists that their communist PeoplesCoin should be used instead=E2=80=94 th=
e
usual suspects. And so, after a couple years of upgrades, it is so.
Or perhaps more likely=E2=80=94 it would get revised along side a hardforki=
ng
cryptosystem upgrade (e.g. replacing sha256 in the hash trees with
SHA-4-512), thus amortizing out all the migration costs...
The trickiness and risk of changing it=E2=80=94 of economic problems, of th=
e
risk of undermining trust in the immutability of the system's rules=E2=80=
=94
only exists if there is genuine, considered, and honest controversy
about the parameters. At the moment any increase would be sure to be
controversial: common hardware and networks would not obviously keep
up with our current maximum size, and our current transaction load
doesn't produce a usable fees market. This cannot remain true
forever.
|
