From: joe2015@openmailbox•org
To: Bryan Bishop <kanzure@gmail•com>
Cc: Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Increasing the blocksize as a (generalized) softfork.
Date: Mon, 21 Dec 2015 11:04:31 +0800 [thread overview]
Message-ID: <8088b376ed29f3ea0af67b7567189e31@openmailbox.org> (raw)
In-Reply-To: <CABaSBazMYw6ou1=GDvi5XxNRgWxsQxTu9jU+PaqW9u9rAe=D-w@mail.gmail.com>
On 2015-12-21 02:17, Bryan Bishop wrote:
> On Sun, Dec 20, 2015 at 4:56 AM, joe2015--- via bitcoin-dev
> <bitcoin-dev@lists•linuxfoundation.org> wrote:
>
>> An Arbitrary Block-size Increase Via a Generalized Softfork
>
> This seems conceptually similar to "extension blocks":
> https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2015-May/008356.html
> [1]
> https://bitcointalk.org/index.php?topic=283746.0 [2]
> http://gnusha.org/bitcoin-wizards/2015-12-20.log [3]
>
> "Extended blocks" are also mentioned over here too:
> https://bitcointalk.org/index.php?topic=1296628.msg13307275#msg13307275
> [4]
The main difference is that my proposal does not introduce different
"tiers" of blocks, and does not require uses to move coins to manually
move coins between these tiers.
Instead, my proposal uses a single flat block format that is essentially
the same as the current block format; only bigger.
The main point is that such a change does not require a hardfork with
global consensus, as is commonly assumed, but rather can be deployed
like a softfork using the method described in my original post.
--joe.
next prev parent reply other threads:[~2015-12-21 3:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-20 10:56 joe2015
2015-12-20 15:22 ` joe2015
2015-12-20 15:50 ` Tier Nolan
2015-12-20 18:17 ` Bryan Bishop
2015-12-21 3:04 ` joe2015 [this message]
2015-12-21 4:23 ` jl2012
2015-12-21 4:41 ` joe2015
2015-12-30 19:00 ` Bob McElrath
2015-12-30 23:49 ` Jonathan Toomim
2015-12-30 23:56 ` Jonathan Toomim
2015-12-31 0:04 ` Bob McElrath
2015-12-31 4:39 ` joe2015
2015-12-31 10:39 ` David Chan
2015-12-31 11:32 ` joe2015
2016-01-04 21:53 ` Luke Dashjr
2015-12-20 17:21 joe2015
2015-12-21 3:39 ` Jeff Garzik
2015-12-21 3:58 ` joe2015
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=8088b376ed29f3ea0af67b7567189e31@openmailbox.org \
--to=joe2015@openmailbox$(echo .)org \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=kanzure@gmail$(echo .)com \
/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