From: Thomas Zander <thomas@thomaszander.se>
To: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] A summary list of all concerns related to rising the block size
Date: Wed, 12 Aug 2015 18:41:36 +0200 [thread overview]
Message-ID: <2133828.JttggH90JM@pluto> (raw)
In-Reply-To: <CABm2gDqn4bDTqmp=9h_qBjgjV0=LhY97bTHdRevAREYVyR07EQ@mail.gmail.com>
On Wednesday 12. August 2015 12.28.39 Jorge Timón wrote:
> But let's just list the concerns first.
Concerns?
I have never heard of "develop-by-concerns"? Is that similar to
fire fighting management?
To that I have this reply;
http://www.aleanjourney.com/2009/07/stop-fighting-fires.html
Your question makes sure that the proper answers don't fit.
And that may be why you are getting frustrated because I've given a lot of
reasons why a blocksize increase is needed soon, and none of them show up
in your list...
http://lists.linuxfoundation.org/pipermail/bitcoin-dev/2015-August/010120.html
http://lists.linuxfoundation.org/pipermail/bitcoin-dev/2015-August/010129.html
And various others; I'm not going to bother pasting URLs, you probably have
them already.
Point is, Bitcoin is a growing network, with a growing amount of transactions
and we KNOW we will get into problems when the block consistently get full.
How do we know? Because of the old guys in this list having the experience
that this always happens, because anyone in the IT business can tell you the
same.
We have started LN to cope with this growth, but this won't be enough since it
just won't handle all usecases and thus the on-chain growth will continue. For
instance remittances and cross-border purchases.
We need both LN as well as bigger blocks.
--
Thomas Zander
next prev parent reply other threads:[~2015-08-12 16:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-12 10:28 [bitcoin-dev] A summary list of all concerns related to rising the block size Jorge Timón
2015-08-12 16:41 ` Thomas Zander [this message]
2015-08-12 17:08 ` Milly Bitcoin
2015-08-14 22:01 ` Jorge Timón
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=2133828.JttggH90JM@pluto \
--to=thomas@thomaszander.se \
--cc=bitcoin-dev@lists.linuxfoundation.org \
/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