public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Andy Chase <theandychase@gmail.com>
To: Thomas Kerin <thomas.kerin@gmail.com>,
	bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] [BIP/Draft] BIP Acceptance Process
Date: Sun, 6 Sep 2015 13:44:56 -0700	[thread overview]
Message-ID: <CAAxp-m-TYga4RuhZ+Nv2rgrBAcpYPntSXtrwj95Q=p+uF=324w@mail.gmail.com> (raw)
In-Reply-To: <CAHv+tb5ksyZKp5jLvmzFbD2vBOUrWn6ps80ODECVRqYj8m=PZA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 3195 bytes --]

Dang you are right Thomas! I'm just pretty excited about this proposal and
sparking a discussion on this issue.

Here's some updates and thoughts:

   - Luke said: "BIPs wouldn't be recognised as such because nobody cares
   to meet the higher requirements"
      - Possibly true, but maybe not! I think people like having a say
      especially people with a lot of money on the line or those who are really
      passionate about Bitcoin
      - One counter example, I emailed all the sponsors of the workshop
      conference about their stance in regards to scalability going into the
      workshop and I got a 47% response rate (with 21% responding with
a concrete
      answer). See here:
      https://www.reddit.com/r/bitcoinxt/comments/3isqmf/which_of_the_scaling_bitcoin_conference_sponsors/cujg3vc
      - One example that agrees with you, I talked to the #bitcoin-assets
      community and they seemed very against participating in future
BIPs or even
      allowing discussion with people outside their community:
      http://pastebin.com/H5WeNwu3
   - I'm seeking a historian or political science expert to assist me in
   this area. If you guys know any I'd be glad to talk to them about working
   with them.
   - Many people are complaining about the stake part, and are worried
   about the ambiguity. I firmly believe that proof of stake is a poor voting
   mechanism because it gives the most power to those that have a lot of
   money.
      - I think proof of stake might work for merchants to prove they have
      a decent economic stake if they sign with a well-known cold
wallet address,
      but I agree with someone that said merchants may be hesitant about doing
      that.


On Sun, Sep 6, 2015 at 6:36 AM, Thomas Kerin <thomas.kerin@gmail.com> wrote:

> Normally allocation comes after about 2 weeks or so, not 2 days!
> On 5 Sep 2015 10:20 pm, "Andy Chase via bitcoin-dev" <
> bitcoin-dev@lists.linuxfoundation.org> wrote:
>
>> Okay for sure yeah writing another proposal that reflects the current
>> state of affairs as people see it might provide some interesting
>> perspective on this proposal. I would welcome that.
>>
>> Greg: With no other direct comments appearing to be inbound I'd like to
>> move forward with this one and get a number assigned to it. Thanks!
>>
>> Thanks to all for the discussion!
>>
>> On Fri, Sep 4, 2015 at 2:45 PM, Luke Dashjr <luke@dashjr.org> wrote:
>>
>>> On Friday, September 04, 2015 9:36:42 PM Andy Chase wrote:
>>> > I understand your concerns. What kinds of changes do you think should
>>> go
>>> > through a process like this? Just hard forks?
>>>
>>> The process loses meaning if it doesn't reflect reality. So only
>>> hardforks
>>> should go through the hardfork process; only softforks through the
>>> softfork
>>> process; etc. Trying to make one-size-fits-all just means de facto
>>> accepted
>>> BIPs wouldn't be recognised as such because nobody cares to meet the
>>> higher
>>> requirements.
>>>
>>> Luke
>>>
>>
>>
>> _______________________________________________
>> bitcoin-dev mailing list
>> bitcoin-dev@lists.linuxfoundation.org
>> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>>
>>

[-- Attachment #2: Type: text/html, Size: 4784 bytes --]

  parent reply	other threads:[~2015-09-06 20:45 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-04  0:30 [bitcoin-dev] [BIP/Draft] BIP Acceptance Process Andy Chase
2015-09-04  0:41 ` Luke Dashjr
2015-09-04  0:52   ` Andy Chase
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 [this message]
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-m-TYga4RuhZ+Nv2rgrBAcpYPntSXtrwj95Q=p+uF=324w@mail.gmail.com' \
    --to=theandychase@gmail.com \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=thomas.kerin@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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