From: Akiva Lichtner <akiva.lichtner@gmail•com>
To: bitcoin-dev@lists•linuxfoundation.org
Subject: [bitcoin-dev] Scaling by Partitioning
Date: Tue, 8 Dec 2015 11:27:18 -0500 [thread overview]
Message-ID: <CABCnA7Wqz76m8qo5BYT41Z=hBH+fUfOc4xsFAGg=Niv7Jgkqsg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1602 bytes --]
Hello,
I am seeking some expert feedback on an idea for scaling Bitcoin. As a
brief introduction: I work in the payment industry and I have twenty years'
experience in development. I have some experience with process groups and
ordering protocols too. I think I understand Satoshi's paper but I admit I
have not read the source code.
The idea is to run more than one simultaneous chain, each chain defeating
double spending on only part of the coin. The coin would be partitioned by
radix (or modulus, not sure what to call it.) For example in order to
multiply throughput by a factor of ten you could run ten parallel chains,
one would work on coin that ends in "0", one on coin that ends in "1", and
so on up to "9".
The number of chains could increase automatically over time based on the
moving average of transaction volume.
Blocks would have to contain the number of the partition they belong to,
and miners would have to round-robin through partitions so that an attacker
would not have an unfair advantage working on just one partition.
I don't think there is much impact to miners, but clients would have to
send more than one message in order to spend money. Client messages will
need to enumerate coin using some sort of compression, to save space. This
seems okay to me since often in computing client software does have to
break things up in equal parts (e.g. memory pages, file system blocks,) and
the client software could hide the details.
Best wishes for continued success to the project.
Regards,
Akiva
P.S. I found a funny anagram for SATOSHI NAKAMOTO: "NSA IS OOOK AT MATH"
[-- Attachment #2: Type: text/html, Size: 1878 bytes --]
next reply other threads:[~2015-12-08 16:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-08 16:27 Akiva Lichtner [this message]
2015-12-08 16:45 ` Bryan Bishop
2015-12-08 18:30 ` Akiva Lichtner
2015-12-08 20:50 ` Patrick Strateman
2015-12-08 21:23 ` Akiva Lichtner
2015-12-08 21:29 ` Patrick Strateman
2015-12-08 21:41 ` Akiva Lichtner
2015-12-09 6:30 ` Loi Luu
2015-12-09 18:26 ` Akiva Lichtner
2015-12-09 21:16 ` Loi Luu
2015-12-10 4:04 ` Akiva Lichtner
2015-12-09 22:35 ` Andrew
2015-12-10 3:58 ` Akiva Lichtner
2015-12-10 4:31 ` Bryan Bishop
2015-12-10 4:08 ` Dave Scotese
2015-12-10 4:14 ` Dave Scotese
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='CABCnA7Wqz76m8qo5BYT41Z=hBH+fUfOc4xsFAGg=Niv7Jgkqsg@mail.gmail.com' \
--to=akiva.lichtner@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/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