From: Peter Todd <pete@petertodd•org>
To: Venzen Khaosan <venzen@mail•bihthai.net>
Cc: bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] Block size increase oppositionists: please clearly define what you need done to increase block size to a static 8MB, and help do it
Date: Tue, 30 Jun 2015 12:25:26 -0400 [thread overview]
Message-ID: <20150630162526.GA8479@savin.petertodd.org> (raw)
In-Reply-To: <5592C0A3.8050008@mail.bihthai.net>
[-- Attachment #1: Type: text/plain, Size: 769 bytes --]
On Tue, Jun 30, 2015 at 11:15:31PM +0700, Venzen Khaosan wrote:
> > Do what's best for Bitcoin and define what needs to get done to
> > agree to a simple block size increase to a static 8MB.
>
> And this then leads back to the core issue: if an 8MB blocksize
> excludes many on this list from testnet, then the proposed 8MB blocks
> will exclude a lot of mainnet participants (miners) and degrade the
> quality of diversity and decentralization.
>
> How about testing at double the capacity: 2MB?
Which of course raises another issue: if that was the plan, then all you
can do is double capacity, with no clear way to scaling beyond that.
Why bother?
--
'peter'[:-1]@petertodd.org
00000000000000001599522de3e8ed28f0189ddccfa1d6db5eb380cacffc79d7
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 650 bytes --]
next prev parent reply other threads:[~2015-06-30 16:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-30 15:34 Michael Naber
2015-06-30 16:03 ` Richard Moore
2015-06-30 16:15 ` Venzen Khaosan
2015-06-30 16:25 ` Peter Todd [this message]
2015-06-30 16:35 ` Michael Naber
2015-06-30 19:59 ` Bryan Cheng
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=20150630162526.GA8479@savin.petertodd.org \
--to=pete@petertodd$(echo .)org \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=venzen@mail$(echo .)bihthai.net \
/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