From: Luke Dashjr <luke@dashjr•org>
To: Tomas <tomas@tomasvdw•nl>
Cc: bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] [BIP Draft] Decentralized Improvement Proposals
Date: Wed, 30 Dec 2015 23:47:16 +0000 [thread overview]
Message-ID: <201512302347.17609.luke@dashjr.org> (raw)
In-Reply-To: <1451499779.3919416.479357794.2C21BFA1@webmail.messagingengine.com>
On Wednesday, December 30, 2015 6:22:59 PM Tomas wrote:
> > The specification itself looks like an inefficient and bloaty reinvention
> > of version bits.
>
> The actual assignment of version bits isn't clear from the
> specification. Are you saying that any implementation that wants to
> propose a change is encouraged to pick a free version bit and use it?
That should probably be clarified in the BIP, I agree. Perhaps it ought to be
assigned the same as BIP numbers themselves, by the BIP editor? (Although as a
limited resource, maybe that's not the best solution.)
> Furthermore, my proposal addresses the danger of forward-incompatible
> changes; a hard-fork can no longer occur as every implementation will
> agree on the active the set of rules even if it has not implemented
> them. This seems to be lacking in the version bits proposal.
I don't think that's possible. First of all, a hardfork can always occur,
since this is something done by the economy and not (even possibly opposed to)
miners. Furthermore, consider the change affecting how further rule changes
are made, such as a PoW algorithm change.
Luke
next prev parent reply other threads:[~2015-12-30 23:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-30 16:35 Tomas
2015-12-30 17:10 ` Luke Dashjr
2015-12-30 18:22 ` Tomas
2015-12-30 23:47 ` Luke Dashjr [this message]
2016-01-03 23:31 ` Rusty Russell
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=201512302347.17609.luke@dashjr.org \
--to=luke@dashjr$(echo .)org \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=tomas@tomasvdw$(echo .)nl \
/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