From: Tomas <tomas@tomasvdw•nl>
To: Luke Dashjr <luke@dashjr•org>, bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] [BIP Draft] Decentralized Improvement Proposals
Date: Wed, 30 Dec 2015 19:22:59 +0100 [thread overview]
Message-ID: <1451499779.3919416.479357794.2C21BFA1@webmail.messagingengine.com> (raw)
In-Reply-To: <201512301710.27154.luke@dashjr.org>
> 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?
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.
Tomas
next prev parent reply other threads:[~2015-12-30 18:23 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 [this message]
2015-12-30 23:47 ` Luke Dashjr
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=1451499779.3919416.479357794.2C21BFA1@webmail.messagingengine.com \
--to=tomas@tomasvdw$(echo .)nl \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=luke@dashjr$(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