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
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <mh.in.england@gmail.com>) id 1XFj1A-0001fl-BI
for bitcoin-development@lists.sourceforge.net;
Fri, 08 Aug 2014 12:11:32 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.219.47 as permitted sender)
client-ip=209.85.219.47; envelope-from=mh.in.england@gmail.com;
helo=mail-oa0-f47.google.com;
Received: from mail-oa0-f47.google.com ([209.85.219.47])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1XFj19-0002go-D3
for bitcoin-development@lists.sourceforge.net;
Fri, 08 Aug 2014 12:11:32 +0000
Received: by mail-oa0-f47.google.com with SMTP id g18so3950223oah.34
for <bitcoin-development@lists.sourceforge.net>;
Fri, 08 Aug 2014 05:11:26 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.60.159.232 with SMTP id xf8mr29916451oeb.16.1407499885970;
Fri, 08 Aug 2014 05:11:25 -0700 (PDT)
Sender: mh.in.england@gmail.com
Received: by 10.76.35.234 with HTTP; Fri, 8 Aug 2014 05:11:25 -0700 (PDT)
In-Reply-To: <CA+s+GJCbCRQP_w3g-0qtA6K8qrf6ywNfJ9d1367gSTfgCwgU2Q@mail.gmail.com>
References: <CAJHLa0Ok6s5xQcMSeLa69adLBXEaicuXqcg45eZrwYtVFbx-dA@mail.gmail.com>
<CANEZrP2wYcxJhxRRa86Nm9ENtK2SA5VNG-L7f5pHb_W=Ajcj5Q@mail.gmail.com>
<CA+s+GJD+9qpwFcVfHOCCsFYjmk7A0V=65vG-7jJ6D7jj4Pi_7g@mail.gmail.com>
<CANEZrP245242JYDBBo72XVmKgEBO96QPjcJi8Jy2Dm_r90n1Bw@mail.gmail.com>
<CAJHLa0N3xx1QZ==iSLYNsdgkBGoqN34+4eVtukkjn+3SrDhC7A@mail.gmail.com>
<CANEZrP1mhSodC-ZvkuVKAgHO44bM7QX=RivRDhnDeHOKr8PXqQ@mail.gmail.com>
<CA+s+GJCbCRQP_w3g-0qtA6K8qrf6ywNfJ9d1367gSTfgCwgU2Q@mail.gmail.com>
Date: Fri, 8 Aug 2014 14:11:25 +0200
X-Google-Sender-Auth: ioFRv-5n_Q579rhKqpJtisCOX7A
Message-ID: <CANEZrP2UFMDJ+88MU=RTyU4FV_HCHwuHLmd5S9aK2AZ7DJ+j7g@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Wladimir <laanwj@gmail.com>
Content-Type: multipart/alternative; boundary=047d7bd6c4e4b9930f05001d1a96
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: 1XFj19-0002go-D3
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] NODE_EXT_SERVICES and advertising related
services
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, 08 Aug 2014 12:11:32 -0000
--047d7bd6c4e4b9930f05001d1a96
Content-Type: text/plain; charset=UTF-8
>
> Something like `getutxos` or this proposal could be implemented as an
> external application or script, instead of having to integrate
> everything into bitcoind.
>
Right, although getutxos needs access to the UTXO set which bitcoind
already has. An external plugin would have to recalculate it from scratch
which seems redundant.
However there are many other useful services that could be added in such a
way, like -txindex or the nLockTime storage facility we talked about the
other day.
> Bitcoind would need a local interprocess message bus for that
Maybe, that feels like it could be overkill though. Probably just something
like
./bitcoind -servicecookie=<long random string> -allowextservices=127.0.0.1/8
and then any program can connect to bitcoind as normal, send "registersrv"
with the cookie and a list of command ids it's interested in, maybe a
service bit to set, and start receiving those messages wrapped in a new
structure that gives some kind of client ID (like IP address). So any
library that can do the basic P2P protocol could then be extended with not
much code to get a multiplexed stream of messages from different clients.
An additional standalone program can then bridge this mechanism to running
a shell command for particular messages, though given the history of shell
based exploits I'd feel safer with something that doesn't do that ....
--047d7bd6c4e4b9930f05001d1a96
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">Something like `getutxos` or this proposal could=
be implemented as an<br>
external application or script, instead of having to integrate<br>
everything into bitcoind.<br></blockquote><div><br></div><div>Right, althou=
gh getutxos needs access to the UTXO set which bitcoind already has. An ext=
ernal plugin would have to recalculate it from scratch which seems redundan=
t.</div>
<div><br></div><div>However there are many other useful services that could=
be added in such a way, like -txindex or the nLockTime storage facility we=
talked about the other day.</div><div>=C2=A0</div><blockquote class=3D"gma=
il_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-lef=
t:1ex">
Bitcoind would need a local interprocess message bus for that</blockquote><=
div><br></div><div>Maybe, that feels like it could be overkill though. Prob=
ably just something like</div><div><br></div><div>./bitcoind -servicecookie=
=3D<long random string> -allowextservices=3D<a href=3D"http://127.0.0=
.1/8">127.0.0.1/8</a></div>
<div><br></div><div>and then any program can connect to bitcoind as normal,=
send "registersrv" with the cookie and a list of command ids it&=
#39;s interested in, maybe a service bit to set, and start receiving those =
messages wrapped in a new structure that gives some kind of client ID (like=
IP address). So any library that can do the basic P2P protocol could then =
be extended with not much code to get a multiplexed stream of messages from=
different clients.</div>
<div><br></div><div>An additional standalone program can then bridge this m=
echanism to running a shell command for particular messages, though given t=
he history of shell based exploits I'd feel safer with something that d=
oesn't do that ....</div>
</div></div></div>
--047d7bd6c4e4b9930f05001d1a96--
|
