From: "Clément Elbaz" <clem.ds@gmail•com>
To: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Getting trusted metrics from the block chain in an untrusted environment ?
Date: Thu, 9 Jan 2014 18:46:05 +0100 [thread overview]
Message-ID: <CAP63atYX1rKCNaDHr5WwAO_kORibCDaBcecWoanpRDR0WMw6aA@mail.gmail.com> (raw)
In-Reply-To: <CAP63atZ=-Wd++nuL_Gf-wnT768w3wHhxsA+KgVY-S_C2+1QRLw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2936 bytes --]
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ément
On Wed, Jan 8, 2014 at 8:44 PM, Clément 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] instead
> of financial transactions.
>
> These structures are verifiable so it could work the same way as a regular
> 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ément
>
--
Clément ELBAZ
06. 09. 55. 78. 41
clem.ds@gmail•com
[-- Attachment #2: Type: text/html, Size: 3535 bytes --]
next prev parent reply other threads:[~2014-01-09 17:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-08 19:38 Clément Elbaz
2014-01-08 19:44 ` Clément Elbaz
2014-01-08 22:29 ` Clément Elbaz
2014-01-09 17:46 ` Clément Elbaz [this message]
2014-01-09 14:03 ` Rob Golding
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAP63atYX1rKCNaDHr5WwAO_kORibCDaBcecWoanpRDR0WMw6aA@mail.gmail.com \
--to=clem.ds@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox