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
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <clem.ds@gmail.com>) id 1XmhkR-00025X-Nk
for bitcoin-development@lists.sourceforge.net;
Fri, 07 Nov 2014 11:30:35 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
designates 74.125.82.54 as permitted sender)
client-ip=74.125.82.54; envelope-from=clem.ds@gmail.com;
helo=mail-wg0-f54.google.com;
Received: from mail-wg0-f54.google.com ([74.125.82.54])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1XmhkP-0003XJ-RH
for bitcoin-development@lists.sourceforge.net;
Fri, 07 Nov 2014 11:30:35 +0000
Received: by mail-wg0-f54.google.com with SMTP id n12so3462657wgh.27
for <bitcoin-development@lists.sourceforge.net>;
Fri, 07 Nov 2014 03:30:23 -0800 (PST)
X-Received: by 10.194.87.131 with SMTP id ay3mr15674622wjb.66.1415359823190;
Fri, 07 Nov 2014 03:30:23 -0800 (PST)
MIME-Version: 1.0
References: <20141106213215.GA12918@savin.petertodd.org>
<A53D2C60-1D6A-4796-9776-3AF396BEC9F1@bitsofproof.com>
<545BF0C2.3030201@bluematt.me>
<CAJHLa0NTj6m4JpHx3+nWtYVV1Zpwf-FaxiyFX9DR821cQYVqsg@mail.gmail.com>
<545BFAD6.1000504@riseup.net>
<20141106232649.GD26859@savin.petertodd.org>
<545C0617.7020300@riseup.net>
<20141107000310.GA6532@savin.petertodd.org>
<B29D4E11-E69E-49DE-9E4C-741DDA01B352@bitsofproof.com>
<20141107084810.GA7878@savin.petertodd.org>
From: =?UTF-8?Q?Cl=C3=A9ment_Elbaz?= <clem.ds@gmail.com>
Date: Fri, 07 Nov 2014 11:30:22 +0000
Message-ID: <CAP63atZv_WJX3Ev6HirVVbZdjn6oayqMfjFDj657TG4VKdL9Nw@mail.gmail.com>
To: Peter Todd <pete@petertodd.org>, Tamas Blummer <tamas@bitsofproof.com>
Content-Type: multipart/alternative; boundary=089e0102edfe7da49e050743233c
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
(clem.ds[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: 1XmhkP-0003XJ-RH
Cc: bitcoin-development@lists.sourceforge.net,
Justus Ranvier <justusranvier@riseup.net>
Subject: Re: [Bitcoin-development] The difficulty of writing consensus
critical code: the SIGHASH_SINGLE bug
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: Fri, 07 Nov 2014 11:30:35 -0000
--089e0102edfe7da49e050743233c
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Thinking out loud here : would it make sense to separate the consensus code
into some kind of "Bitcoin Kernel" (similar to the Linux Kernel) project
that could be used by anyone ?
Bitcoin Core (and any other application wishing to do so) could be based on
it.
The kernel would just contain the absolute minimum code for reaching
consensus, leaving every other aspects of the implementation to the
applications built with it.
It would be stateless : it would provide an interface to submit a
block/transaction to be validated, including the context needed to validate
it (the previously validated blocks referenced by this block/transaction).
What do you think ?
Cl=C3=A9ment
Le Fri Nov 07 2014 at 9:49:05 AM, Peter Todd <pete@petertodd.org> a =C3=A9c=
rit :
On Fri, Nov 07, 2014 at 09:07:47AM +0100, Tamas Blummer wrote:
> > Peter,
> >
> > forking would work best with a freeze of the consensus code. Do you see
> any chance for that?
>
> To a first approximation the consensus code *is* frozen; if we introduce
> any consensus changes into it at this point it's due to a mistake, not
> intentionally.
>
> Of course, that's not including the two serious soft-fork proposals in
> the air right now, Pieter Wuille's BIP62 and my CHECKLOCKTIMEVERIFY.
> However dealing with proposed changes like those in an environment where
> the competing implementations all use essentially the same
> consensus-critical code is much easier than in an environment where they
> don't; I say this on both a technical and political level.
>
> --
> 'peter'[:-1]@petertodd.org
> 00000000000000000c901eb1b6b765519b99c3afd7a9062ff4cfa29666ce140d
> ------------------------------------------------------------
> ------------------
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
--089e0102edfe7da49e050743233c
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Thinking out loud here : would it make sense to separate the consensus code=
into some kind of "Bitcoin Kernel" (similar to the Linux Kernel)=
project that could be used by anyone ?<div><br></div><div>Bitcoin Core (an=
d any other application wishing to do so) could be based on it.=C2=A0</div>=
<div><br></div><div>The kernel would just contain the absolute minimum code=
for reaching consensus, leaving every other aspects of the implementation =
to the applications built with it.</div><div><br></div><div>It would be sta=
teless : it would provide an interface to submit a block/transaction to be =
validated, including the context needed to validate it (the previously vali=
dated blocks referenced by this block/transaction).</div><div><br></div><di=
v>What do you think ?</div><div><br></div><div>Cl=C3=A9ment</div><div><br><=
div class=3D"gmail_quote">Le=C2=A0Fri Nov 07 2014 at 9:49:05 AM, Peter Todd=
<<a href=3D"mailto:pete@petertodd.org" target=3D"_blank">pete@petertodd=
.org</a>> a =C3=A9crit=C2=A0:</div><div class=3D"gmail_quote"><br><block=
quote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc=
solid;padding-left:1ex">On Fri, Nov 07, 2014 at 09:07:47AM +0100, Tamas Bl=
ummer wrote:<br>
> Peter,<br>
><br>
> forking would work best with a freeze of the consensus code. Do you se=
e any chance for that?<br>
<br>
To a first approximation the consensus code *is* frozen; if we introduce<br=
>
any consensus changes into it at this point it's due to a mistake, not<=
br>
intentionally.<br>
<br>
Of course, that's not including the two serious soft-fork proposals in<=
br>
the air right now, Pieter Wuille's BIP62 and my CHECKLOCKTIMEVERIFY.<br=
>
However dealing with proposed changes like those in an environment where<br=
>
the competing implementations all use essentially the same<br>
consensus-critical code is much easier than in an environment where they<br=
>
don't; I say this on both a technical and political level.<br>
<br>
--<br>
'peter'[:-1]@<a href=3D"http://petertodd.org" target=3D"_blank">pet=
ertodd.org</a><br>
00000000000000000c901eb1b6b765<u></u><u></u>519b99c3afd7a9062ff4cfa29666ce<=
u></u><u></u>140d<br>
------------------------------<u></u><u></u>------------------------------<=
u></u><u></u>------------------<br>
______________________________<u></u><u></u>_________________<br>
Bitcoin-development mailing list<br>
<a href=3D"mailto:Bitcoin-development@lists.sourceforge.net" target=3D"_bla=
nk">Bitcoin-development@lists.<u></u>sour<u></u>ceforge.net</a><br>
<a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-development=
" target=3D"_blank">https://lists.sourceforge.net/<u></u><u></u>lists/listi=
nfo/bitcoin-<u></u>develop<u></u>ment</a><br>
</blockquote></div></div>
--089e0102edfe7da49e050743233c--
|
