public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@bitpay.com>
To: Chun Wang <1240902@gmail.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] User vote in blocksize through fees
Date: Sun, 14 Jun 2015 00:59:03 -0400	[thread overview]
Message-ID: <CAJHLa0Pvv-oyaZ03idm15WGAE-ra14oKdLkqv3w-bTdnS=wPog@mail.gmail.com> (raw)
In-Reply-To: <CAFzgq-y5xBSXexVi0mJw_w89R2_AHJCgmj=gLN4CK_-YaO4-eg@mail.gmail.com>

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

On Sun, Jun 14, 2015 at 12:55 AM, Chun Wang <1240902@gmail.com> wrote:

> To tell you the truth. It is only because most miners are not located
> in the West. If Slush, Eligius and BTC Guild still on top 3, the core
> developers, including brain-dead Mike Hearn, would be very happy to do
> BIP100 just like they did BIP34 and BIP66. Shame on you!
>

BIP 100 requires a hard fork to engage.  Users proactively opt-in.

-- 
Jeff Garzik
Bitcoin core developer and open source evangelist
BitPay, Inc.      https://bitpay.com/

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

  reply	other threads:[~2015-06-14  4:59 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-12 18:11 [Bitcoin-development] User vote in blocksize through fees Peter Todd
2015-06-12 18:20 ` Mark Friedenbach
2015-06-12 18:26   ` Matt Whitlock
2015-06-12 18:36     ` Peter Todd
2015-06-12 18:56     ` Jannes Faber
     [not found]       ` <CABr1YTfowMqgDZoWhDXiM0Bd3dwhVo6++FOvLntGc2HkApEbGw@mail.gmail.com>
2015-06-12 20:04         ` Eric Lombrozo
2015-06-12 23:01           ` Vincent Truong
2015-06-12 23:11             ` Luke Dashjr
2015-06-12 23:23           ` Aaron Gustafson
2015-06-12 18:22 ` Matt Whitlock
2015-06-12 18:34   ` Peter Todd
2015-06-12 18:36     ` Matt Whitlock
2015-06-12 18:39       ` Benjamin
2015-06-12 18:47         ` Peter Todd
2015-06-12 18:44       ` Peter Todd
2015-06-12 18:52         ` Matt Whitlock
2015-06-12 18:54         ` Matt Whitlock
2015-06-12 18:56           ` Aaron Gustafson
2015-06-13 22:20 ` Danny Thorpe
2015-06-13 22:24   ` Eric Lombrozo
2015-06-14  4:55   ` Chun Wang
2015-06-14  4:59     ` Jeff Garzik [this message]
2015-06-14  5:08     ` Eric Lombrozo
2015-06-14  5:13       ` Jeff Garzik
2015-06-14  5:20         ` Eric Lombrozo
2015-06-14  5:36           ` Jeff Garzik
2015-06-14 10:06             ` Mats Henricson
2015-06-14 10:34               ` Benjamin
2015-06-14 15:07                 ` Jeff Garzik
2015-06-14 21:59                   ` odinn
2015-06-14 20:10                 ` Eric Lombrozo
2015-06-14 14:42               ` Jeff Garzik
2015-06-14 22:26                 ` Mike Hearn
2015-06-15  3:59             ` Eric Lombrozo
2015-06-14  4:16 ` Stephen
2015-06-14  4:50   ` Eric Lombrozo
2015-06-14  4:56   ` Jeff Garzik
2015-06-14  7:19 ` Ashley Holman
2015-06-13 23:57 Raystonn
2015-06-14  4:28 ` odinn
2015-06-14  5:46   ` Aaron Voisine
2015-06-14 21:38     ` odinn

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='CAJHLa0Pvv-oyaZ03idm15WGAE-ra14oKdLkqv3w-bTdnS=wPog@mail.gmail.com' \
    --to=jgarzik@bitpay.com \
    --cc=1240902@gmail.com \
    --cc=bitcoin-development@lists.sourceforge.net \
    /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