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
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <mh.in.england@gmail.com>) id 1X6fVQ-0007Yp-6O
for bitcoin-development@lists.sourceforge.net;
Mon, 14 Jul 2014 12:37:20 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.219.43 as permitted sender)
client-ip=209.85.219.43; envelope-from=mh.in.england@gmail.com;
helo=mail-oa0-f43.google.com;
Received: from mail-oa0-f43.google.com ([209.85.219.43])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1X6fVP-0000pb-8q
for bitcoin-development@lists.sourceforge.net;
Mon, 14 Jul 2014 12:37:20 +0000
Received: by mail-oa0-f43.google.com with SMTP id i7so3155050oag.30
for <bitcoin-development@lists.sourceforge.net>;
Mon, 14 Jul 2014 05:37:13 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.60.97.230 with SMTP id ed6mr2438128oeb.81.1405341433793;
Mon, 14 Jul 2014 05:37:13 -0700 (PDT)
Sender: mh.in.england@gmail.com
Received: by 10.76.35.234 with HTTP; Mon, 14 Jul 2014 05:37:13 -0700 (PDT)
In-Reply-To: <CA+c4Zoy-O_MkRZDVjHysDMhZnx8mo7XAAw7iJQYHrm9f4OsEUQ@mail.gmail.com>
References: <53C3A8C0.5070608@googlemail.com>
<CANEZrP21sc9smev5tg07HnLpw-8WWS7EvzzTyEvD6qYEfHvpoA@mail.gmail.com>
<CA+c4Zoy-O_MkRZDVjHysDMhZnx8mo7XAAw7iJQYHrm9f4OsEUQ@mail.gmail.com>
Date: Mon, 14 Jul 2014 14:37:13 +0200
X-Google-Sender-Auth: bniKREqSOysdq8G1uM7QAc-7wnk
Message-ID: <CANEZrP1FZjqpoOgJuNa4=_bar61=PCTeT8MqG9FGnpdKS=SCbw@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: "sickpig@gmail.com" <sickpig@gmail.com>
Content-Type: multipart/alternative; boundary=089e0115f46ef3140a04fe268c97
X-Spam-Score: -0.5 (/)
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
(mh.in.england[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
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: 1X6fVP-0000pb-8q
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>,
Krzysztof Okupski <k.okupski@googlemail.com>
Subject: Re: [Bitcoin-development] Bitcoin Protocol Specification
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: Mon, 14 Jul 2014 12:37:20 -0000
--089e0115f46ef3140a04fe268c97
Content-Type: text/plain; charset=UTF-8
>
> just out of curiosity, do you think it will be possible to create any
> other proper protocol specifications rather than the C++ original?
Well it's a finite code base so yes, it should be possible.
The only problem is .... so far everyone who tried it, didn't succeed :)
Heck even people who tried to reimplement it by reading the code keep
getting subtle details wrong.
So it should definitely be possible one day, assuming Bitcoin doesn't
become radically more complex, but it's a minefield.
--089e0115f46ef3140a04fe268c97
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"><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #c=
cc solid;padding-left:1ex"><div class=3D"">just out of curiosity, do you th=
ink it will be possible to create any<br>
</div>
other proper=C2=A0protocol specifications rather than the C++ =C2=A0origina=
l?</blockquote><div><br></div><div>Well it's a finite code base so yes,=
it should be possible.</div><div><br></div><div>The only problem is .... s=
o far everyone who tried it, didn't succeed :) Heck even people who tri=
ed to reimplement it by reading the code keep getting subtle details wrong.=
</div>
<div><br></div><div>So it should definitely be possible one day, assuming B=
itcoin doesn't become radically more complex, but it's a minefield.=
</div></div></div></div>
--089e0115f46ef3140a04fe268c97--
|
