From: Scott Morgan <scott@adligo.com>
To: bitcoin-dev@lists.linuxfoundation.org
Subject: [bitcoin-dev] Merkel Forrest Partitioning
Date: Tue, 21 Jun 2016 17:12:32 -0500 [thread overview]
Message-ID: <CANEdHmj92DirMaavmFpHPOmCgBobdsy=czSbY2pLOEGKjgTPBw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1137 bytes --]
Hi Akiva,
I have also given a little thought to partitioning, in a totally
different way a Merkel Tree Forrest. Generally the idea here would have be
to create new Merkel Trees every so often as currency supply was added. It
would partition the mining process and therefore improve the distribution
of the verification.
It would work as follows, and NO I haven't really thought this through it's
just an idea!
Imagine it was 2009 and there was a small number of 250 BTC in 'Batch 1',
once the number of BTC needed to go above 250 BTC two new Batches would be
created each one with it's own Merkel Tree until 750 BTC and so on.
Eventually there would be a large number of trees, allowing small scale
pool miners to dominate a single or small number of the trees and their
block chains.
This would also create a potential partial payment problem, where you send
3 BTC but only receive 2 BTC since 1 BTC ends up on a bad block and needs
to be resent.
Since most of the BTC currency supply is already available it's a bit late
for BitCoin, but could be used for new crypto currencies.
Any thoughts on this idea?
Cheers,
Scott
[-- Attachment #2: Type: text/html, Size: 2915 bytes --]
reply other threads:[~2016-06-21 22:12 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='CANEdHmj92DirMaavmFpHPOmCgBobdsy=czSbY2pLOEGKjgTPBw@mail.gmail.com' \
--to=scott@adligo.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