From: Alan Reiner <etotheipi@gmail•com>
To: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: [Bitcoin-development] Ultimate Blockchain Compression w/ trust-free lite nodes
Date: Sun, 17 Jun 2012 14:39:28 -0400 [thread overview]
Message-ID: <4FDE2460.5080301@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1483 bytes --]
All,
With the flurry of discussion about blockchain compression, I thought it
was time to put forward my final, most-advanced idea, into a single,
well-thought-out, *illustrated*, forum post. Please check it out:
https://bitcointalk.org/index.php?topic=88208.0
This is a huge undertaking, but it has some pretty huge benefits. And
it's actually feasible because it can be implemented without disrupting
the main network. I'm sure there's lots of issues with it, but I'm
putting it out there to see how it might be improved and actually executed.
----
*Summary:
*/Use a special tree data structure to organize all unspent-TxOuts on
the network, and use the root of this tree to communicate its
"signature" between nodes. The leaves of this tree actually correspond
to addresses/scripts, and the data at the leaf is actually a root of the
unspent-TxOut list for that address/script. To maintain security of the
tree signatures, it will be included in the header of an alternate
blockchain, which will be secured by merged mining.
This provides the same compression as the simpler unspent-TxOut merkle
tree, but also gives nodes a way to download just the unspent-TxOut list
for each address in their wallet, and verify that list directly against
the blockheaders. Therefore, even lightweight nodes can get full
address information, from any untrusted peer, and with only a tiny
amount of downloaded data (a few kB). /*
*----
Alright, tear it up!
-Alan
[-- Attachment #2: Type: text/html, Size: 2206 bytes --]
next reply other threads:[~2012-06-17 18:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-17 18:39 Alan Reiner [this message]
2012-06-17 19:05 ` Peter Todd
2012-06-17 22:46 ` Alberto Torres
2012-06-17 23:17 ` Alan Reiner
2012-06-18 10:14 ` Peter Todd
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=4FDE2460.5080301@gmail.com \
--to=etotheipi@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