From: joe2015@openmailbox•org
To: jl2012 <jl2012@xbt•hk>
Cc: bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] Increasing the blocksize as a (generalized) softfork.
Date: Mon, 21 Dec 2015 12:41:54 +0800 [thread overview]
Message-ID: <f9ad1348fb7dedca35b594782fee7e0f@openmailbox.org> (raw)
In-Reply-To: <e170f3a10164019824edaafe5a04f067@xbt.hk>
On 2015-12-21 12:23, jl2012 wrote:
> I proposed something very similar 2 years ago:
> https://bitcointalk.org/index.php?topic=283746.0
Yes there are similarities but also some important differences. See my
response here:
http://lists.linuxfoundation.org/pipermail/bitcoin-dev/2015-December/012085.html
In short my proposal is compatible with conventional blocksize limit
hardfork ideas, like BIP101, BIP202, 2-4-8 etc. etc.
> This is an interesting academic idea. But the way you implement it
> will immediately kill all existing full and SPV nodes (not really
> dead, rather like zombie as they can't send and receive any tx).
That's the whole point. After a conventional hardfork everyone needs to
upgrade, but there is no way to force users to upgrade. A user who is
simply unaware of the fork, or disagrees with the fork, uses the old
client and the currency splits.
Under this proposal old clients effectively enter "zombie" mode, forcing
users to upgrade.
--joe
next prev parent reply other threads:[~2015-12-21 4:42 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
2015-12-21 4:23 ` jl2012
2015-12-21 4:41 ` joe2015 [this message]
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=f9ad1348fb7dedca35b594782fee7e0f@openmailbox.org \
--to=joe2015@openmailbox$(echo .)org \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=jl2012@xbt$(echo .)hk \
/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