public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: joe2015@openmailbox•org
To: Bob McElrath <bob_bitcoin@mcelrath•org>
Cc: Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Increasing the blocksize as a (generalized) softfork.
Date: Thu, 31 Dec 2015 12:39:25 +0800	[thread overview]
Message-ID: <5a479e307f84c6e8547287489cd134d1@openmailbox.org> (raw)
In-Reply-To: <20151231000442.GK18200@mcelrath.org>

> So I'm very strongly against this "generalized softfork" idea -- I also 
> don't
> see how upgraded nodes and non-upgraded nodes can possibly end up with 
> the same
> UTXO set.

The only way for non-upgraded nodes to get the correct UTXO set is to 
upgrade.

It is important to keep in mind this was proposed as an alternative to a 
hardfork.  With a hardfork the UTXOs also diverge as upgraded and 
non-upgraded clients follow different chains.

--joe.


  reply	other threads:[~2015-12-31  4:39 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
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 [this message]
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=5a479e307f84c6e8547287489cd134d1@openmailbox.org \
    --to=joe2015@openmailbox$(echo .)org \
    --cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
    --cc=bob_bitcoin@mcelrath$(echo .)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