public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Tom Harding <tomh@thinlink.com>
To: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] soft-fork block size increase(extensionblocks)
Date: Wed, 17 Jun 2015 17:04:38 -0700	[thread overview]
Message-ID: <55820B16.5060806@thinlink.com> (raw)
In-Reply-To: <COL131-DS14939FCAB6DB494743B545CDA60@phx.gbl>


"Increase DEFAULT_BLOCK_MAX_SIZE to 1MB"
https://github.com/bitcoin/bitcoin/pull/6231

On 6/17/2015 8:28 AM, Raystonn . wrote:
> Wow.  That email was delayed by the list for quite some time.  It was 
> sent on 6/1.
>
>> I also need to argue for increasing the default block limit to the 
>> full 1MB in the next release. We’re already hitting that limit in 
>> bursts of transactions, which puts pressure on the average displayed 
>> in the below graphs.
>
>




  reply	other threads:[~2015-06-18  0:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-01 19:02 [Bitcoin-development] soft-fork block size increase (extensionblocks) Raystonn .
2015-06-17 15:28 ` [Bitcoin-development] soft-fork block size increase(extensionblocks) Raystonn .
2015-06-18  0:04   ` Tom Harding [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-06-01 15:40 [Bitcoin-development] soft-fork block size increase (extension blocks) Adam Back
2015-06-01 16:12 ` Mike Hearn
2015-06-01 17:21   ` Adam Back
2015-06-01 18:01     ` Mike Hearn
2015-06-01 18:39       ` [Bitcoin-development] soft-fork block size increase (extensionblocks) Raystonn .

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=55820B16.5060806@thinlink.com \
    --to=tomh@thinlink.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