From: Hector Chu <hectorchu@gmail.com>
To: Simon Liu <simon@bitcartel.com>
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] A reason we can all agree on to increase block size
Date: Mon, 3 Aug 2015 08:34:00 +0100 [thread overview]
Message-ID: <CAAO2FKEBBS5wxefGCPcurcRGg76sORrBMHvd2SSNiW1q_zWBWQ@mail.gmail.com> (raw)
In-Reply-To: <55BF153B.9030001@bitcartel.com>
[-- Attachment #1: Type: text/plain, Size: 636 bytes --]
On 3 August 2015 at 08:16, Simon Liu via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:
> Increasing the block size shouldn't be a problem for Chinese miners.
> Five of the largest - F2Pool, Antpool, BW, BTCChina, Huobi - have
> already signed a draft agreement indicating they are fine with an
> increase to 8 MB: http://www.8btc.com/blocksize-increase-2
What's the current stance of the Chinese pools on Bitcoin XT, should
Bitcoin Core refuse to increase the block size to 8 MB in a timely fashion?
Would they run it if the economic majority (e.g. Coinbase, Bitpay, etc.)
publicly stated their support for big blocks?
[-- Attachment #2: Type: text/html, Size: 1066 bytes --]
next prev parent reply other threads:[~2015-08-03 7:34 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-02 21:02 [bitcoin-dev] A reason we can all agree on to increase block size Jim Phillips
2015-08-03 1:21 ` Pindar Wong
2015-08-03 4:33 ` Jim Phillips
2015-08-03 3:13 ` odinn
2015-08-03 6:34 ` Adam Back
2015-08-03 6:53 ` Jim Phillips
2015-08-04 10:53 ` Jorge Timón
2015-08-03 7:16 ` Simon Liu
2015-08-03 7:34 ` Hector Chu [this message]
2015-08-03 7:53 ` Adam Back
2015-08-03 8:06 ` Hector Chu
2015-08-03 8:20 ` Eric Lombrozo
2015-08-03 8:31 ` Hector Chu
2015-08-03 8:38 ` Eric Lombrozo
2015-08-03 8:52 ` Hector Chu
2015-08-03 9:01 ` Eric Lombrozo
2015-08-03 9:22 ` Hector Chu
2015-08-03 7:46 ` Adam Back
2015-08-03 13:57 ` Michael Ruddy
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=CAAO2FKEBBS5wxefGCPcurcRGg76sORrBMHvd2SSNiW1q_zWBWQ@mail.gmail.com \
--to=hectorchu@gmail.com \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=simon@bitcartel.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