From: Btc Drak <btcdrak@gmail•com>
To: Yifu Guo <yifu@coinapex•com>
Cc: Gregory Maxwell via bitcoin-dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Core Devs : can you share your thoughts about all BIPs on this website ?
Date: Fri, 21 Aug 2015 12:28:41 +0100 [thread overview]
Message-ID: <CADJgMzuBKauAX_tf4ZCxtErfz9Rq7ri3=8S9ZiKou6CPwP8cQw@mail.gmail.com> (raw)
In-Reply-To: <CAHcfU-XrSA6p_2AJJ1W6KmatkEZdvh1W4ruA-upq4wPWoaJTNQ@mail.gmail.com>
On Fri, Aug 21, 2015 at 11:55 AM, Yifu Guo via bitcoin-dev
<bitcoin-dev@lists•linuxfoundation.org> wrote:
> I like the intend of this attempt to bring more clarity to the blocksize
> debate, however it would be more help to make this a information site about
> the current outstanding BIPs and summarize their differences rather than
> voting mechanism.
> (ofcourse the author of the BIPs would "vote" for their own proposals.)
>
> It would be good to include supporting and counter statements regards to
> these BIPs on the site.
> in addition to highlight certain things like pools in china have voiced
> their opinion that increase should happen, and 8mb is something they are
> comfortable with, which is not directly related to a single BIP, but never
> the less relevant in this discussion.
I was rather surprised by the tweet from AntPool[1] today saying that
they support big blocks and would be prepared to upgrade to XT. Pools
have stated that they are willing to increase to a maximum of 8MB, but
upgrading to XT puts them on a schedule towards 8GB which is clearly
not what they have agreed to.
Do you have any insights into what's going on there?
Also do you have any insight into what Chinese pools would accept as a
compromise in terms of raising the blocksize limit?
Drak
[1] https://twitter.com/JihanWu/status/633288343338381314
next prev parent reply other threads:[~2015-08-21 11:29 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-19 4:57 Nicolas Dorier
2015-08-21 3:10 ` Btc Drak
2015-08-21 4:45 ` Gregory Maxwell
2015-08-21 5:10 ` Nicolas Dorier
2015-08-21 9:09 ` Btc Drak
2015-08-21 9:32 ` Peter Todd
2015-08-21 9:29 ` Peter Todd
2015-08-21 9:31 ` Btc Drak
2015-08-21 9:35 ` Peter Todd
2015-08-21 10:55 ` Yifu Guo
2015-08-21 11:28 ` Btc Drak [this message]
2015-08-21 12:28 ` Yifu Guo
2015-08-21 13:18 ` Oliver Egginger
2015-08-21 13:34 ` Will Madden
2015-08-21 17:31 ` Oliver Egginger
2015-08-21 18:07 ` Will Madden
2015-08-22 3:02 ` odinn
2015-08-21 16:58 ` Nicolas Dorier
2015-08-21 3:38 Nicolas Dorier
2015-08-21 3:45 ` Eric Lombrozo
2015-08-21 3:54 ` Nicolas Dorier
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='CADJgMzuBKauAX_tf4ZCxtErfz9Rq7ri3=8S9ZiKou6CPwP8cQw@mail.gmail.com' \
--to=btcdrak@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=yifu@coinapex$(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