From: Gregory Maxwell <gmaxwell@gmail.com>
To: grarpamp <grarpamp@gmail.com>
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Scalability issues
Date: Mon, 23 Jul 2012 03:35:08 -0400 [thread overview]
Message-ID: <CAAS2fgTHrWdXHbX8oiLgnrhdC+yxL4QyPd7S4iB8RMNip_sUGg@mail.gmail.com> (raw)
In-Reply-To: <CAD2Ti29dqCYoOMcX0zcOQnpLGCxnCjYHHqMzyyq+hvcVQ2c7nQ@mail.gmail.com>
On Sun, Jul 22, 2012 at 6:37 PM, grarpamp <grarpamp@gmail.com> wrote:
> It already takes a month to build a new blockchain, let alone keep up
> with new incoming blocks.
Please fix your software stack. Something is wrong with your system
and I doubt it has much to do with bitcoin. A full sync here takes
something like an hour.
There are certainly lots of scalability things going on, but there is
no cause for concern for regular hardware being unable to _keep up_
without a hardforking change to the protocol first.
next prev parent reply other threads:[~2012-07-23 7:35 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-22 22:37 [Bitcoin-development] Scalability issues grarpamp
2012-07-23 7:23 ` Raphael NICOLLE
2012-07-23 7:35 ` Gregory Maxwell [this message]
2012-07-23 9:00 ` Michael Grønager
2012-07-23 15:11 ` grarpamp
[not found] ` <CAAS2fgREzk_dU0ie+YvDdRwKcTk6tk_i=a2Bb74w9uF=EwYhGA@mail.gmail.com>
2012-07-23 22:33 ` grarpamp
2012-07-27 4:20 ` grarpamp
2012-07-27 4:59 ` Gregory Maxwell
2012-07-27 5:59 ` grarpamp
2012-07-27 6:03 ` Luke-Jr
2012-07-27 6:28 ` grarpamp
2012-07-27 6:56 ` Gregory Maxwell
2012-07-27 19:37 ` grarpamp
2012-07-27 8:53 ` Andreas Petersson
[not found] ` <CAPg+sBjpqqxL_GxYc+8Ry7DcXMkouO9bYi5VqOyEjj_5s0x06Q@mail.gmail.com>
2012-07-27 9:59 ` Pieter Wuille
2012-07-27 19:26 ` grarpamp
2012-07-23 15:54 ` steve
2012-07-24 8:25 ` Michael Grønager
2012-07-24 9:18 ` Mike Hearn
2012-07-24 19:56 ` steve
2012-07-25 9:45 ` Michael Grønager
2012-07-25 14:24 ` steve
2012-07-23 22:50 ` Aidan Thornton
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=CAAS2fgTHrWdXHbX8oiLgnrhdC+yxL4QyPd7S4iB8RMNip_sUGg@mail.gmail.com \
--to=gmaxwell@gmail.com \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=grarpamp@gmail.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