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
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <kanzure@gmail.com>) id 1YMiP7-0004cv-BM
for bitcoin-development@lists.sourceforge.net;
Sat, 14 Feb 2015 19:29:25 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.214.179 as permitted sender)
client-ip=209.85.214.179; envelope-from=kanzure@gmail.com;
helo=mail-ob0-f179.google.com;
Received: from mail-ob0-f179.google.com ([209.85.214.179])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1YMiP3-00048a-Re
for bitcoin-development@lists.sourceforge.net;
Sat, 14 Feb 2015 19:29:25 +0000
Received: by mail-ob0-f179.google.com with SMTP id wp4so30779917obc.10
for <bitcoin-development@lists.sourceforge.net>;
Sat, 14 Feb 2015 11:29:16 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.182.233.226 with SMTP id tz2mr2787630obc.33.1423942156421;
Sat, 14 Feb 2015 11:29:16 -0800 (PST)
Received: by 10.60.22.7 with HTTP; Sat, 14 Feb 2015 11:29:16 -0800 (PST)
In-Reply-To: <CALqxMTFDVfOai0Y=O7UWrk5pk5pWSMz+FGedJngEZ-V=bDjGTg@mail.gmail.com>
References: <CABm2gDpReRty6TdfMDssjF27XgC_SYs_U__SFBNdsYW24Mzh8w@mail.gmail.com>
<54CC0E1D.7030409@voskuil.org>
<CABm2gDqM6q24tPEBKSHbbVQu-mvfV37PNc4hD=VjyRHk2jujZw@mail.gmail.com>
<54D0414F.6030806@voskuil.org>
<CABm2gDo_sYjNWU6EEsKmOXt5uUu87Lj1oFzqio79MxSx2SYrNg@mail.gmail.com>
<54DE7601.4070509@voskuil.org>
<CABm2gDpt60B=Sf_2X9xt4fPH7x4fff7K4h36XfosHigV5tP+4Q@mail.gmail.com>
<54DF07A5.1060004@voskuil.org>
<CABm2gDoS+XOR7Ugt91kNWNdvwsb1_Zb-aO0sma_Xps2Sx-0N5g@mail.gmail.com>
<54DF2E80.5060506@voskuil.org>
<20150214131320.GA26731@savin.petertodd.org>
<3D4F2E23-CADE-4FE7-B960-3F79815E868C@bitsofproof.com>
<CALqxMTFDVfOai0Y=O7UWrk5pk5pWSMz+FGedJngEZ-V=bDjGTg@mail.gmail.com>
Date: Sat, 14 Feb 2015 13:29:16 -0600
Message-ID: <CABaSBay6DZdvbfXG=jwxNkWtcZVjhw7Bi6Ro1e3mLTmCWdn8zQ@mail.gmail.com>
From: Bryan Bishop <kanzure@gmail.com>
To: Adam Back <adam@cypherspace.org>, Bryan Bishop <kanzure@gmail.com>,
Bryan Bishop <bryan@ledgerx.com>
Content-Type: multipart/alternative; boundary=001a11c2e62e6a134f050f115e7e
X-Spam-Score: -0.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
(kanzure[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
-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: 1YMiP3-00048a-Re
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>,
libbitcoin@lists.dyne.org
Subject: Re: [Bitcoin-development] On Rewriting Bitcoin (was Re:
[Libbitcoin] Satoshi client: is a fork past 0.10 possible?)
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: Sat, 14 Feb 2015 19:29:25 -0000
--001a11c2e62e6a134f050f115e7e
Content-Type: text/plain; charset=UTF-8
On Sat, Feb 14, 2015 at 1:04 PM, Adam Back <adam@cypherspace.org> wrote:
> That its highly complex to maintain strict consensus between bitcoin
> versions, does not justify consensus rewrite experiments
Correct. However, those maintenance costs absolutely do justify working
towards formal proofs of correctness for the existing implementation. These
plans are no secret and are publicly discussed, but I think it would be
instrumental to outsiders if the correctness plans and ongoing progress
could be mentioned whenever a warning is made about unjustified and
dangerous Bitcoin consensus rewrite attempts.
- Bryan
http://heybryan.org/
1 512 203 0507
--001a11c2e62e6a134f050f115e7e
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On S=
at, Feb 14, 2015 at 1:04 PM, Adam Back <span dir=3D"ltr"><<a href=3D"mai=
lto:adam@cypherspace.org" target=3D"_blank">adam@cypherspace.org</a>></s=
pan> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex=
;border-left:1px #ccc solid;padding-left:1ex">That its highly complex to ma=
intain strict consensus between bitcoin versions, does not justify consensu=
s rewrite experiments</blockquote></div><br>Correct. However, those mainten=
ance costs absolutely do justify working towards formal proofs of correctne=
ss for the existing implementation. These plans are no secret and are publi=
cly discussed, but I think it would be instrumental to outsiders if the cor=
rectness plans and ongoing progress could be mentioned whenever a warning i=
s made about unjustified and dangerous Bitcoin consensus rewrite attempts.<=
br><br><div class=3D"gmail_signature">- Bryan<br><a href=3D"http://heybryan=
.org/">http://heybryan.org/</a><br>1 512 203 0507</div>
</div></div>
--001a11c2e62e6a134f050f115e7e--
|
