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 ) id 1W1JgJ-000093-Ll for bitcoin-development@lists.sourceforge.net; Thu, 09 Jan 2014 17:46:11 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.128.54 as permitted sender) client-ip=209.85.128.54; envelope-from=clem.ds@gmail.com; helo=mail-qe0-f54.google.com; Received: from mail-qe0-f54.google.com ([209.85.128.54]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1W1JgI-0001ia-QX for bitcoin-development@lists.sourceforge.net; Thu, 09 Jan 2014 17:46:11 +0000 Received: by mail-qe0-f54.google.com with SMTP id cy11so3498932qeb.27 for ; Thu, 09 Jan 2014 09:46:05 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.49.17.232 with SMTP id r8mr9925343qed.74.1389289565406; Thu, 09 Jan 2014 09:46:05 -0800 (PST) Received: by 10.229.177.195 with HTTP; Thu, 9 Jan 2014 09:46:05 -0800 (PST) In-Reply-To: References: Date: Thu, 9 Jan 2014 18:46:05 +0100 Message-ID: From: =?ISO-8859-1?Q?Cl=E9ment_Elbaz?= To: bitcoin-development@lists.sourceforge.net Content-Type: multipart/alternative; boundary=047d7bea3be4096f5d04ef8d2f1a 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: 1W1JgI-0001ia-QX 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: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Jan 2014 17:46:11 -0000 --047d7bea3be4096f5d04ef8d2f1a Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi Rob, Thank you for answering. > So you want to 'benefit' from the network without contributing to it ? > Not going to happen - why would anyone be interested in providing you 'free compute resources' ? Not free. As I stated in my second email ("some more thoughts" etc.), it seems really fitting to pay a fee to the network for every metric request you send. 'I want to execute this request on your blockchain, and I want the response to be approved by the Bitcoin network, and here is a fee for all the computing trouble". You either have the blockchain and the hardware resources to compute things based on it, or you have addresses that takes a few bytes of data in your environement but contains money, potentially a lot. The situation seems plausible to me. The thing is, as soon as there is an exchange of value (hardware computing resources vs bitcoins) between parties that do not trust each other, there is a need for proof of work, and thus my idea (in my second email) of a specifc block chain that would store metric requests, current block number when they were asked, and hash of theirs responses. This can be validated by others nodes and as such can be published in a ledger just like bitcoin transaction. > Setup a node, create an API interface and have your 'app' use your API on yoru node :p The idea would have been actually to be able to get these computations in a trusted way without having access to a specific trusted node. Compensating absence of trust by providing actual money. Anyways. I got quite a few answer privately, and after study it seems SPV mode of bitcoinj will be just fine for my specific needs. I would have liked the solution to be network-centric ideally (By committing to an SPV-ready API like bitcoinj, I'm committing to languages that provide a stable SPV API), but I'll be just fine with bitcoinj for now. Thank you Rob and everyone for your time. Cl=E9ment On Wed, Jan 8, 2014 at 8:44 PM, Cl=E9ment Elbaz 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 --047d7bea3be4096f5d04ef8d2f1a Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi Rob,

Thank y= ou for answering.

> So you want to 'benefit' from the net= work without contributing to it ?

> Not going to happen - why wou= ld anyone be interested in providing you 'free compute resources' ?=

Not free. As I stated in my second email ("some more thought= s" etc.), it seems really fitting to pay a fee to the network for ever= y metric request you send. 'I want to execute this request on your bloc= kchain, and I want the response to be approved by the Bitcoin network, and = here is a fee for all the computing trouble".

You either have the blockchain and the hardware resources to comp= ute things based on it, or you have addresses that takes a few bytes of dat= a in your environement but contains money, potentially a lot. The situation= seems plausible to me.

The thing is, as soon as there is an exchange of value (hardware = computing resources vs bitcoins) between parties that do not trust each oth= er, there is a need for proof of work, and thus my idea (in my second email= ) of a specifc block chain that would store metric requests, current block = number when they were asked, and hash of theirs responses. This can be vali= dated by others nodes and as such can be published in a ledger just like bi= tcoin transaction.

> Setup a node, create an API interface and have your 'app' = use your API on yoru node :p

The idea would have been actually= to be able to get these computations in a trusted way without having acces= s to a specific trusted node. Compensating absence of trust by providing ac= tual money.

Anyways. I got quite a few answer privately, and after study it s= eems SPV mode of bitcoinj will be just fine for my specific needs. I would = have liked the solution to be network-centric ideally (By committing to an = SPV-ready API like bitcoinj, I'm committing to languages that provide a= stable SPV API), but I'll be just fine with bitcoinj for now.

Thank you Rob and everyone for your time.

Cl=E9ment




On Wed, Jan 8, 2014 at 8:44 PM, Cl=E9ment Elba= z <clem.ds@gmail.com> wrote:
Some more thoughts :
If no such project exist yet, I thought it could work with an alternate, s= mall and fixed-length 'metric request block chain' of some sort.
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.

These structures are verifiable so it could work the same way as a regu= lar financial blochchain.

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.

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 thi= s makes any sense to you ?

Thanks,

Cl=E9ment



--
Cl=E9ment ELBAZ
06. = 09. 55. 78. 41
cl= em.ds@gmail.com
--047d7bea3be4096f5d04ef8d2f1a--