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 not rising the block size
Date: Fri, 14 Aug 2015 15:48:51 +0200 [thread overview]
Message-ID: <1832593.Ok8MIJxeIG@coldstorage> (raw)
In-Reply-To: <55CD51D9.50103@mail.bihthai.net>
On Friday 14. August 2015 09.26.33 Venzen Khaosan via bitcoin-dev wrote:
> In the scenario below, you argue that the current 1MB limit would lead
> to "constantly full" blocks. If the limit is increased to say 1.6GB
> then a government or banking group may choose to utilize 1.5GB of the
> capacity of each block (and pay fees or not) for their settlement
> network. Then how did upping the blocksize remedy anything? Or is this
> use-case not plausible?
Your usecase only makes sense if we assume that blocks are community property.
This is provably not the case, it has been proven with the recent spam attack,
people could just continue sending their payments without issues by just
increasing the fee a bit.
As such, the bigger blocks don't immediately get filled, it makes more space
for everyone. People abusing it will also have to spend a lot more money (that
goes to benefit the network as a whole) to disrupt it.
--
Thomas Zander
next prev parent reply other threads:[~2015-08-14 14:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-12 9:59 Jorge Timón
2015-08-12 11:21 ` Venzen Khaosan
2015-08-14 22:35 ` Jorge Timón
2015-08-14 23:12 ` Jorge Timón
2015-08-14 23:57 ` Jorge Timón
2015-08-20 21:11 ` Elliot Olds
2015-08-20 21:29 ` Ahmed Zsales
2015-08-12 19:52 ` Elliot Olds
2015-08-14 22:55 ` Jorge Timón
2015-08-15 20:36 ` Elliot Olds
2015-08-13 9:52 ` Ashley Holman
2015-08-13 16:36 ` Jean-Paul Kogelman
2015-08-14 22:57 ` Jorge Timón
2015-08-13 22:01 ` Geir Harald Hansen
2015-08-14 2:26 ` Venzen Khaosan
2015-08-14 11:35 ` Marcel Jamin
2015-08-14 13:48 ` Thomas Zander [this message]
2015-08-14 22:59 ` 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=1832593.Ok8MIJxeIG@coldstorage \
--to=thomas@thomaszander$(echo .)se \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/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