From: Sergio Demian Lerner <sergio.d.lerner@gmail.com>
To: bitcoin-dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: [bitcoin-dev] Proof of unique blockchain storage revised
Date: Wed, 16 Sep 2015 01:37:42 -0300 [thread overview]
Message-ID: <CAKzdR-rsgtAhiRwZtj8H8sCZaxz30Srki6SmcR7k-67ff1NyqA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 623 bytes --]
One possible way to incentivize the existence of more Bitcoin network nodes
is by paying peers when they provide data in the blokcchain. One of the
problems is that it is not easy to tell if the peer is really providing a
useful service by storing the blockchain or it is just relying the request
to some other peers as a proxy.
In this post I review the use of asymmetric-time functions to be able to
prove unique (IP-tied) blockchain storage and propose improvements to make
it fully practical.
Full post here:
https://bitslog.wordpress.com/2015/09/16/proof-of-unique-blockchain-storage-revised/
Best regards, Sergio.
[-- Attachment #2: Type: text/html, Size: 791 bytes --]
reply other threads:[~2015-09-16 4:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAKzdR-rsgtAhiRwZtj8H8sCZaxz30Srki6SmcR7k-67ff1NyqA@mail.gmail.com \
--to=sergio.d.lerner@gmail.com \
--cc=bitcoin-dev@lists.linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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