summaryrefslogtreecommitdiff
path: root/71/ab2c244b7ba4d5db965187d3f93b95d59330c0
blob: be1642dfda95a3d0c43a06c5f428fa0ef02bfbd1 (plain)
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
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
	helo=mx.sourceforge.net)
	by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <clem.ds@gmail.com>) id 1W11cn-0000U9-Sf
	for bitcoin-development@lists.sourceforge.net;
	Wed, 08 Jan 2014 22:29:21 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.216.170 as permitted sender)
	client-ip=209.85.216.170; envelope-from=clem.ds@gmail.com;
	helo=mail-qc0-f170.google.com; 
Received: from mail-qc0-f170.google.com ([209.85.216.170])
	by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1W11cm-0003fB-Nx
	for bitcoin-development@lists.sourceforge.net;
	Wed, 08 Jan 2014 22:29:21 +0000
Received: by mail-qc0-f170.google.com with SMTP id e9so1816874qcy.15
	for <bitcoin-development@lists.sourceforge.net>;
	Wed, 08 Jan 2014 14:29:15 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.49.72.66 with SMTP id b2mr215348436qev.11.1389220155185;
	Wed, 08 Jan 2014 14:29:15 -0800 (PST)
Received: by 10.229.177.195 with HTTP; Wed, 8 Jan 2014 14:29:15 -0800 (PST)
In-Reply-To: <CAP63atZ=-Wd++nuL_Gf-wnT768w3wHhxsA+KgVY-S_C2+1QRLw@mail.gmail.com>
References: <CAP63atZBJqi6oN9EbPxzEo4qk5ZMgEKQ11NSPWmU65FypDdbzw@mail.gmail.com>
	<CAP63atZ=-Wd++nuL_Gf-wnT768w3wHhxsA+KgVY-S_C2+1QRLw@mail.gmail.com>
Date: Wed, 8 Jan 2014 23:29:15 +0100
Message-ID: <CAP63atasCa50ts4EWyh8j+ZL4CgCci-9r5WS5CEDqM51iu5E9w@mail.gmail.com>
From: =?ISO-8859-1?Q?Cl=E9ment_Elbaz?= <clem.ds@gmail.com>
To: bitcoin-development@lists.sourceforge.net
Content-Type: multipart/alternative; boundary=047d7b5db124dd90d504ef7d0548
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: 1W11cm-0003fB-Nx
Subject: Re: [Bitcoin-development] Getting trusted metrics from the block
 chain in an untrusted environment ?
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: Wed, 08 Jan 2014 22:29:22 -0000

--047d7b5db124dd90d504ef7d0548
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hello all,

It seems there was a problem with my first email (thank you Mark for the
heads up), so I'll copy paste it there :

-----------------------
Hello all,

I'm designing a program that needs some metrics computed from the Bitcoin
block chain (some address balances, or the occurrence or not of a specific
transaction). The kind of infos you get from http://blockchain.info/,
provided you trust this website (my program do not).

My program should run on lightweight/embedded hardware. The execution
environment provides access to the Bitcoin network but not enough resources
to set up a trusted node along with my program. Also, my program trusts the
global Bitcoin network but no individual node.

I would need a way to ask an untrusted Bitcoin node to compute some 'metric
request' on my behalf and having the result of that metric request
validated by the network.

Is there any available or work-in-progress projects that would come close
to this need ? Or should I do it myself ? :-)

Thank you all,

Cl=E9ment Elbaz

-----------------------


On Wed, Jan 8, 2014 at 8:44 PM, Cl=E9ment Elbaz <clem.ds@gmail.com> wrote:

> Some more thoughts :
>
> If no such project exist yet, I thought it could work with an alternate,
> small and fixed-length 'metric request block chain' of some sort.
>
> It would temporarily stores structures defined as [metric request |
> current block number when request was made | hash of the response] instea=
d
> of financial transactions.
>
> These structures are verifiable so it could work the same way as a regula=
r
> financial blochchain.
>
> It should not be part of the main Bitcoin protocol but could be a plugin
> interacting with the data managed by the fullnode bitcoin software.
>
> Also, metrics requests can be expensive to compute and validate, so it
> would make sense to pay a fee everytime you ask one.
>
> Does any of this makes any sense to you ?
>
> Thanks,
>
> Cl=E9ment
>



--=20
Cl=E9ment ELBAZ
06. 09. 55. 78. 41
clem.ds@gmail.com

--047d7b5db124dd90d504ef7d0548
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Hello all,<br><br></div>It seems there was a problem =
with my first email (thank you Mark for the heads up), so I&#39;ll copy pas=
te it there :<br><br>-----------------------<br>Hello all,<br><br>I&#39;m d=
esigning a program that needs some metrics=20
computed from the Bitcoin block chain (some address balances, or the=20
occurrence or not of a specific transaction). The kind of infos you get=20
from <a href=3D"http://blockchain.info/" target=3D"_blank">http://blockchai=
n.info/</a>, provided you trust this website (my program do not).<br>
<br>My program should run on lightweight/embedded hardware. The=20
execution environment provides access to the Bitcoin network but not=20
enough resources to set up a trusted node along with my program. Also,=20
my program trusts the global Bitcoin network but no individual node.<br>
<br>I would need a way to ask an untrusted Bitcoin node to compute some=20
&#39;metric request&#39; on my behalf and having the result of that metric=
=20
request validated by the network.<br><br>Is there any available or work-in-=
progress projects that would come close to this need ? Or should I do it my=
self ? :-)<br>
<br>Thank you all,<br><br>Cl=E9ment Elbaz<br><br>-----------------------<br=
></div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Wed=
, Jan 8, 2014 at 8:44 PM, Cl=E9ment Elbaz <span dir=3D"ltr">&lt;<a href=3D"=
mailto:clem.ds@gmail.com" target=3D"_blank">clem.ds@gmail.com</a>&gt;</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">Some more thoughts :<br><br=
>If no such project exist yet, I thought it could work with an alternate, s=
mall and fixed-length &#39;metric request block chain&#39; of some sort. <b=
r>
<br>It would temporarily stores structures defined as [metric request | cur=
rent block number when request was made | hash of the response] instead of =
financial transactions. <br>
<br>These structures are verifiable so it could work the same way as a regu=
lar financial blochchain.<br><br>It should not be part of the main Bitcoin =
protocol but could be a plugin interacting with the data managed by the ful=
lnode bitcoin software.<br>

<br>Also, metrics requests can be expensive to compute and validate, so it =
would make sense to pay a fee everytime you ask one.<br><br>Does any of thi=
s makes any sense to you ?<br><br>Thanks,<br><br>Cl=E9ment</div>
</blockquote></div><br><br clear=3D"all"><br>-- <br>Cl=E9ment ELBAZ<br>06. =
09. 55. 78. 41<br><a href=3D"mailto:clem.ds@gmail.com" target=3D"_blank">cl=
em.ds@gmail.com</a><br>
</div>

--047d7b5db124dd90d504ef7d0548--