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
|
Return-Path: <Peter_R@gmx.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id B9C968FE
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 15 Nov 2015 01:45:14 +0000 (UTC)
X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6
Received: from mout.gmx.net (mout.gmx.net [212.227.15.15])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id F312AF5
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 15 Nov 2015 01:45:12 +0000 (UTC)
Received: from [192.168.50.29] ([69.50.179.106]) by mail.gmx.com (mrgmx001)
with ESMTPSA (Nemesis) id 0Lb5nF-1ahXJb0Hgv-00kce5;
Sun, 15 Nov 2015 02:45:06 +0100
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
From: Peter R <peter_r@gmx.com>
In-Reply-To: <CAAS2fgTLE1cpDqKTiy0r1VMex7zTAB8tgUC=Y0WXmbNBJL42xQ@mail.gmail.com>
Date: Sat, 14 Nov 2015 17:45:03 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <6DAD1D38-A156-4507-B506-BF66F26E6594@gmx.com>
References: <5631C363.5060705@neomailbox.net>
<201510290803.52734.luke@dashjr.org>
<5632DE33.7030600@bitcartel.com>
<CAAS2fgTga_vTfOKrFu_hEzXSfTfg9FRfJ6aL6ginuGFqnbm7=w@mail.gmail.com>
<3CB90C47-293E-4C18-A381-E5203483D68F@gmx.com>
<CAAS2fgRdK4bDr3x_y9UpdH234PQSfD7U539HBLA==+hLQJ_7Fw@mail.gmail.com>
<571D9B7F-077D-4B80-B577-1C18FF2ECF31@gmx.com>
<CAAS2fgTLE1cpDqKTiy0r1VMex7zTAB8tgUC=Y0WXmbNBJL42xQ@mail.gmail.com>
To: Gregory Maxwell <gmaxwell@gmail.com>
X-Mailer: Apple Mail (2.2104)
Sender: Peter_R@gmx.com
X-Provags-ID: V03:K0:OK7BbcnKkct5SXvG7/nvqFVg/+Ix4JdECyfYebh2NQH3phohCHR
mvLgDbw+YiiPwLZKhTgbuC7+mX+F87fa5LKtWKj1kkiIi0EeZNQ4ezMNinxygWhSt1HZBba
hlhBXDBfsguUpibNyIPompHf3yOmFqOWO7XJ9CTUjPdLG9dIn4Lil4MUmU8bUikLGaNgu4v
tZdAbG5DfB3DMUsy6Ml6w==
X-UI-Out-Filterresults: notjunk:1;V01:K0:eqsFxPntEZI=:5PQbrCPjPGcYg1pFSIfA+2
xLI7U33lgLU2ZeZIdy6lCfwk0pdEA6BhLgYTBne+Z/N+U8Ohv8DMY6PeAUSaRYjis8IXcnSEb
1kR4kZR4gEa0rDgsSr2AtF5kLD6cjYNQRUejPfdIZjpFlrwg6CJiDySvbbTrFY5TiliIvZ9ub
TiXZOulLd7xB4xX4l4TySQur7JtoKYxAoFn5Dsgh4uA+SHM2jYyBkJFHdPQBkJd7XEhG1QmvJ
HPepZiIPffFEurCL9eUA6mUwNRZj7Y4dwLQhNZD3T1kckjt1MDjl99LfGmanZD97HG9aej95Q
7X8PjJum3gTGuzIy6KpzDK9z2LIU5GuHeKsAVQZaRwuWLTAbGP23dlqRWjManBVkipB16wU3v
rCnSCP0CGbqOC72d0voE4Emep7TRtsTA8FVQm93e2CekosAq5cGXF12g/9EojRMzCsEh2kf3b
Rbf/AjaNrbO8hDimTjAUTv5xLLfYKpCdFouN4mTgbUY9jxs1wJa2kMo1kzo5h9gWhw7osHHyf
LoX7slhpvccPaL24/WC+wSs4l9mQBP1UvUmDHKtc74aaJ6i4c0Ji+UvvOmy/u3kP/06IMw4J6
K9uJLAksRWuhLNyzmO5LEj7RR/UUhtfLGG2Otyr4mjbVDSt8HJ0Gx/bGN/UPMvlxOUriK1Tz7
SZMsnnqkNnPLhCPyOWgCZyH1a/Pp1VRlYigP2QHf6tfMNgvdgVaguQiQm3hhJ4sQ6itmcxglW
c0lY1ck3QvyK0Gls/tpXmwMRK4NT7/gK3k5pduJuptpMmNkBQB/uUxN/UjHOKD7XG3+PIQdcs
HNanwOc
X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,FREEMAIL_FROM,
MIME_QP_LONG_LINE,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>,
telemaco <telemaco@neomailbox.net>
Subject: Re: [bitcoin-dev] [patch] Switching Bitcoin Core to sqlite db
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: Sun, 15 Nov 2015 01:45:14 -0000
> On Nov 14, 2015, at 5:08 PM, Gregory Maxwell <gmaxwell@gmail.com> =
wrote:
>=20
> On Sun, Nov 15, 2015 at 1:02 AM, Peter R <peter_r@gmx.com> wrote:
>> Hi Greg,
>>=20
>> Like you said, the issue with using more than one database technology =
is not that one node would prove that Block X is valid while the another =
node proves that Block X is NOT valid. Instead, the problem is that one =
node might say =E2=80=9Cvalid=E2=80=9D while the other node says =E2=80=9C=
I don=E2=80=99t know.=E2=80=9D
>=20
> Sometimes errors are such that you can catch them (if you're super
> vigilant and know an error is even possible in that case)-- and
> indeed, in that case you can get a "I don't know, something is
> wrong.", other times errors are undetectable.
Agreed. There are two cases to consider:
Type 1. One implementation says =E2=80=9Cyes=E2=80=9D or =E2=80=9Cno,=E2=80=
=9D while the other says =E2=80=9CI don=E2=80=99t know=E2=80=9D, and
Type 2. One implementation says =E2=80=9Cyes=E2=80=9D and the other =
says =E2=80=9Cno,=E2=80=9D because of a bug. =20
My previous email described how Type 1 consensus failures can be safely =
dealt with. These include many kinds of database exceptions (e.g., the =
LevelDB fork at block #225,430), or consensus mismatches regarding the =
max size of a block. =20
Type 2 consensus failures are more severe but also less likely (I=E2=80=99=
m not aware of a Type 2 consensus failure besides the 92 million bitcoin =
bug from August 2010). If Core was to accept a rogue TX that created =
another 92 million bitcoins, I think it would be a good thing if the =
other implementations forked away from it (we don=E2=80=99t want =
bug-for-bug compatibility here). =20
This once again reveals the benefits of multiple competing =
implementations. =20
Sincerely,
Peter=20
|
