From: Andy Chase <theandychase@gmail•com>
To: Luke Dashjr <luke@dashjr•org>, bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] [BIP/Draft] BIP Acceptance Process
Date: Thu, 3 Sep 2015 17:52:06 -0700 [thread overview]
Message-ID: <CAAxp-m97sGnFkpVF-vHcg0AQpUsNMV0wESmafg40F6p23pKOwg@mail.gmail.com> (raw)
In-Reply-To: <201509040041.07948.luke@dashjr.org>
[-- Attachment #1: Type: text/plain, Size: 1144 bytes --]
> Any such a BIP like this needs to
> document the natural forces involved in real-world acceptance, not try to
lay
> down "rules" that people are expected to follow.
That's my goal: to take the hodgepodge of we already use for acceptance,
and apply rules that allow true acceptance to be identified in a clearer
way.
If people don't follow the "rules" then the system simply won't work, this
is mentioned in the last section.
On Thu, Sep 3, 2015 at 5:41 PM, Luke Dashjr <luke@dashjr•org> wrote:
> On Friday, September 04, 2015 12:30:50 AM Andy Chase via bitcoin-dev wrote:
> > Here's a BIP. I wrote the BIP mostly to stir the pot on ideas of
> > governance, but I’m moderately serious about it.
>
> Sigh. There is *no governance at all*. Any such a BIP like this needs to
> document the natural forces involved in real-world acceptance, not try to
> lay
> down "rules" that people are expected to follow.
>
> For hardforks, that means economic consensus. For softforks, miner
> majority.
> For basically anything else, real-world implementation and use (by any
> significant quantity of people).
>
> Luke
>
[-- Attachment #2: Type: text/html, Size: 1628 bytes --]
next prev parent reply other threads:[~2015-09-04 0:52 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-04 0:30 Andy Chase
2015-09-04 0:41 ` Luke Dashjr
2015-09-04 0:52 ` Andy Chase [this message]
2015-09-04 0:43 ` Bryan Bishop
2015-09-04 4:40 ` Andy Chase
2015-09-04 19:20 ` Btc Drak
2015-09-04 20:13 ` Andy Chase
2015-09-04 20:31 ` Peter Todd
2015-09-04 20:42 ` Martin Becze
2015-09-04 21:05 ` Milly Bitcoin
2015-09-04 21:01 ` Luke Dashjr
2015-09-04 21:36 ` Andy Chase
2015-09-04 21:45 ` Luke Dashjr
2015-09-05 21:19 ` Andy Chase
[not found] ` <CAHv+tb5ksyZKp5jLvmzFbD2vBOUrWn6ps80ODECVRqYj8m=PZA@mail.gmail.com>
2015-09-06 20:44 ` Andy Chase
2016-01-19 2:12 ` Luke Dashjr
2016-01-19 4:23 ` Andy Chase
2016-01-19 6:07 ` Dave Scotese
2015-09-07 19:37 ` Btc Drak
2015-09-10 1:21 ` Andy Chase
2015-09-12 23:50 ` Andy Chase
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=CAAxp-m97sGnFkpVF-vHcg0AQpUsNMV0wESmafg40F6p23pKOwg@mail.gmail.com \
--to=theandychase@gmail$(echo .)com \
--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