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
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <sickpig@gmail.com>) id 1X6nEC-0003FO-9K
for bitcoin-development@lists.sourceforge.net;
Mon, 14 Jul 2014 20:52:04 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.217.178 as permitted sender)
client-ip=209.85.217.178; envelope-from=sickpig@gmail.com;
helo=mail-lb0-f178.google.com;
Received: from mail-lb0-f178.google.com ([209.85.217.178])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1X6nEA-0005RK-D8
for bitcoin-development@lists.sourceforge.net;
Mon, 14 Jul 2014 20:52:04 +0000
Received: by mail-lb0-f178.google.com with SMTP id 10so3233277lbg.37
for <bitcoin-development@lists.sourceforge.net>;
Mon, 14 Jul 2014 13:51:55 -0700 (PDT)
X-Received: by 10.112.133.70 with SMTP id pa6mr3282810lbb.69.1405371115637;
Mon, 14 Jul 2014 13:51:55 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.152.181.98 with HTTP; Mon, 14 Jul 2014 13:51:35 -0700 (PDT)
In-Reply-To: <CANEZrP1FZjqpoOgJuNa4=_bar61=PCTeT8MqG9FGnpdKS=SCbw@mail.gmail.com>
References: <53C3A8C0.5070608@googlemail.com>
<CANEZrP21sc9smev5tg07HnLpw-8WWS7EvzzTyEvD6qYEfHvpoA@mail.gmail.com>
<CA+c4Zoy-O_MkRZDVjHysDMhZnx8mo7XAAw7iJQYHrm9f4OsEUQ@mail.gmail.com>
<CANEZrP1FZjqpoOgJuNa4=_bar61=PCTeT8MqG9FGnpdKS=SCbw@mail.gmail.com>
From: "sickpig@gmail.com" <sickpig@gmail.com>
Date: Mon, 14 Jul 2014 22:51:35 +0200
Message-ID: <CA+c4ZoxQPwMsA7N+s0C9+snnPEoL-N_GsmfFfDHNMyahWpqyvg@mail.gmail.com>
To: Mike Hearn <mike@plan99.net>
Content-Type: multipart/alternative; boundary=047d7b3442ac20131c04fe2d76e7
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
(sickpig[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: 1X6nEA-0005RK-D8
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 20:52:04 -0000
--047d7b3442ac20131c04fe2d76e7
Content-Type: text/plain; charset=UTF-8
On Mon, Jul 14, 2014 at 2:37 PM, Mike Hearn <mike@plan99.net> wrote:
> 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.
>
thank for the frank reply
--047d7b3442ac20131c04fe2d76e7
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">=
On Mon, Jul 14, 2014 at 2:37 PM, Mike Hearn <span dir=3D"ltr"><<a href=
=3D"mailto:mike@plan99.net" target=3D"_blank">mike@plan99.net</a>></span=
> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div class=3D"gmail_extra">=
<div class=3D"gmail_quote"><div class=3D""><blockquote class=3D"gmail_quote=
" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>just out of curiosity, do you think 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><div>Well it's a finite code base s=
o yes, it should be possible.</div><div><br></div><div>The only problem is =
.... so far everyone who tried it, didn't succeed :) Heck even people w=
ho tried 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>
</blockquote></div><br></div><div class=3D"gmail_extra">thank for the frank=
reply=C2=A0</div></div>
--047d7b3442ac20131c04fe2d76e7--
|
