From: joe2015@openmailbox•org
To: bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] Increasing the blocksize as a (generalized) softfork.
Date: Mon, 21 Dec 2015 01:21:22 +0800 [thread overview]
Message-ID: <dcf6dfa0f7fdcf96e9970e815e4c9b78@openmailbox.org> (raw)
On 2015-12-20 23:50, Tier Nolan via bitcoin-dev wrote:
> This is essentially the "nuclear option".
Remember this is proposed as an alternative to hardforks, which is also
a "nuclear option". Hardforks carry significant risks such as
permanently splitting Bitcoin into two chains if global consensus is
never reached. A (generalized) softfork avoids this problem.
> This could be achieved by adding the hash of an extended block into
> the coinbase but not requiring the coinbase to be the only
> transaction.
I think this can also be viewed as a generalized softfork if one so
chooses, e.g.
NewBlock := OldBlock ++ ExtendedBlock
f(NewBlock) = OldBlock
I do not think this is a bad idea but is more complex than my proposal,
e.g. users having to move coins between different tiers of blocks.
Under my proposal the Bitcoin works more or less the same except with a
larger limit.
--joe
next reply other threads:[~2015-12-20 17:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-20 17:21 joe2015 [this message]
2015-12-21 3:39 ` Jeff Garzik
2015-12-21 3:58 ` joe2015
-- strict thread matches above, loose matches on Subject: below --
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
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
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=dcf6dfa0f7fdcf96e9970e815e4c9b78@openmailbox.org \
--to=joe2015@openmailbox$(echo .)org \
--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