From: Adam Back <adam@cypherspace•org>
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 09:46:51 +0200 [thread overview]
Message-ID: <CALqxMTF8wtXw7FEqLyrDYo1ntUtxF_nFYHJjOHLmUDcgLJYY8Q@mail.gmail.com> (raw)
In-Reply-To: <55BF153B.9030001@bitcartel.com>
On 3 August 2015 at 09:16, Simon Liu <simon@bitcartel•com> 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
There are two problems with this statement. Firstly we can not be doing
protocol design via political lobbying - this is not a scientific approach
and for sure leads to disaster; it is not the colour of the paint on the box,
it is the security of the system.
Secondly as I understand it the Chinese miners did this under duress
of threats of worse as a compromise beyond what they felt they could safely
cope with.
> With regards to China's international bandwidth, not only is intra-Asia
> capacity improving all the time, a major consortium cable FASTER is
> coming online Q2 2016.
That is good news.
Aadm
next prev parent reply other threads:[~2015-08-03 7:46 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-02 21:02 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
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 [this message]
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=CALqxMTF8wtXw7FEqLyrDYo1ntUtxF_nFYHJjOHLmUDcgLJYY8Q@mail.gmail.com \
--to=adam@cypherspace$(echo .)org \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=simon@bitcartel$(echo .)com \
/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