From: joe2015@openmailbox•org
To: Marco Falke <falke.marco@gmail•com>
Cc: bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] An implementation of BIP102 as a softfork.
Date: Thu, 31 Dec 2015 00:27:50 +0800 [thread overview]
Message-ID: <814e1ba765445a4c3b7364c471299393@openmailbox.org> (raw)
In-Reply-To: <CAKJqnrGUKeUb7g4SrjnWNAcPZOuLDKB-kjP2+Jy8Rdk_MfWLyQ@mail.gmail.com>
On 2015-12-30 18:33, Marco Falke wrote:
> This is an interesting approach but I don't see how this is a soft
> fork. (Just because something is not a hard fork, doesn't make it a
> soft fork by definition)
> Softforks don't require any nodes to upgrade. [1]
> Nonetheless, as I understand your approach, it requires nodes to
> upgrade. Otherwise they are missing all transactions but the coinbase
> transactions. Thus, they cannot update their utxoset and are easily
> susceptible to double spends...
>
> Am I missing something obvious?
>
> -- Marco
>
>
> [1] https://en.bitcoin.it/wiki/Softfork#Implications
It just depends how you define "softfork". In my original write-up I
called it a "generalized" softfork, Peter suggested a "firm" fork, and
there are some suggestions for other names. Ultimately what you call it
is not very important.
--joe.
next prev parent reply other threads:[~2015-12-30 16:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-30 5:46 joe2015
2015-12-30 10:33 ` Marco Falke
2015-12-30 16:27 ` joe2015 [this message]
[not found] ` <CAKJqnrE7W8aRgracL1cy_hBLWpVsTAQL4qg4ViSP9aCHvM1yvA@mail.gmail.com>
2016-01-03 3:51 ` joe2015
2016-01-04 18:04 ` Nick ODell
2016-01-05 1:26 ` joe2015
2016-01-12 3:58 ` joe2015
2015-12-30 13:29 ` Jonathan Toomim
2015-12-30 13:57 ` Marcel Jamin
2015-12-30 14:19 ` Peter Todd
2015-12-30 14:31 ` Peter Todd
2015-12-30 15:00 ` Jonathan Toomim
2015-12-30 11:16 Martijn Meijering
2015-12-30 14:28 ` Peter Todd
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=814e1ba765445a4c3b7364c471299393@openmailbox.org \
--to=joe2015@openmailbox$(echo .)org \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=falke.marco@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