public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Venzen Khaosan <venzen@mail.bihthai.net>
To: Pieter Wuille <pieter.wuille@gmail.com>,
	 bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] The need for larger blocks
Date: Fri, 26 Jun 2015 21:38:58 +0700	[thread overview]
Message-ID: <558D6402.20300@mail.bihthai.net> (raw)
In-Reply-To: <CAPg+sBjOj9eXiDG0F6G54SVKkStF_1HRu2wzGqtFF5X_NAWy4w@mail.gmail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Pieter,

Sure. Your thinking is sound. I take things beyond where you have in
your post, so I neither imply that this is your position or that this
is the progression of your stated point.

In one sense, one has to ask the question: is there a reasonable case
for making Bitcoin super-capacitated so it can compete with Visa and
just be the fastest-ever payment network with everyone jizzing in
their pants over its speed and capacity and availability and dividends.

By virtue of the core requirement of decentralization, for Bitcoin to
remain meaningful, it will never compete with Visa or the Fed's new
blockchain-based payment system. So, why attempt the impossible and
expend energy on the futile?

Bitcoin's protocol and payment network has features and benefits that
Visa et all cannot have, so I refute the notion, sometimes expressed
here, that 7tps is a major cap on growth and adoption.

Such thinking takes as its axiom the idea that increased adoption
correlates to increased value. Not true. Look at the price chart for
proof: More businesses accept and more people are using and
transacting via Bitcoin now than ever before and yet the price chart
points *down*, not up.

Why should any explicitly centralized exchange and business venture
have their use of the protocol facilitated? Was the protocol designed
to conform to financial capital demands or was it designed to
fundamentally change the way ordinary users interact with markets?

If those present here, do not realize that the blockchain is a means
of escaping (and destroying through its use and promotion)
centralization, then they have shells over their eyes. Bitcoin is not
meant to fit into the system, it will evolve the system, by the system
coming to it.

Does that mean we shouldn't raise the blocksize? Maybe. But 8GB with
BIP100's protections seems a reasonable change given the sudden
increase in network usage that a global liquidity crisis will impose.

Many scenarios are possible, but there is no onus on developers or on
Bitcoin to "keep up". Like it or not, the global economy will
inevitably be forced to Slow Down as a result of the same thinking
that upholds constant growth without sympathetic contraction.

Venzen Khaosan


On 06/26/2015 09:09 PM, Pieter Wuille wrote:
> Hello all,
> 
> here I'm going to try to address a part of the block size debate
> which has been troubling me since the beginning: the reason why
> people seem to want it.
> 
> People say that larger blocks are necessary. In the long term, I
> agree - in the sense that systems that do not evolve tend to be
> replaced by other systems. This evolution can come in terms of
> layers on top of Bitcoin's blockchain, in terms of the technology
> underlying various aspects of the blockchain itself, and also in
> the scale that this technology supports.
> 
> I do, however, fundamentally disagree that a fear for a change in 
> economics should be considered to necessitate larger blocks. If it
> is, and there is consensus that we should adapt to it, then there
> is effectively no limit going forward. This is similar to how
> Congress voting to increase the copyright term retroactively from
> time to time is really no different from having an infinite
> copyright term in the first place. This scares me.
> 
> Here is how Gavin summarizes the future without increasing block
> sizes in PR 6341:
> 
>> 1. Transaction confirmation times for transactions with a given
>> fee
> will rise; very-low-fee transactions will fail to get confirmed at
> all.
>> 2. Average transaction fee paid will rise 3. People or
>> applications unwilling or unable to pay the rising fees
> will stop submitting transactions
>> 4. People and businesses will shelve plans to use Bitcoin,
>> stunting
> growth and adoption
> 
> Is it fair to summarize this as "Some use cases won't fit any
> more, people will decide to no longer use the blockchain for these
> purposes, and the fees will adapt."?
> 
> I think that is already happening, and will happen at any scale. I 
> believe demand for payments in general is nearly infinite, and only
> a small portion of it will eventually fit on a block chain
> (independent of whether its size is limited by consensus rules or
> economic or technological means). Furthermore, systems that compete
> with Bitcoin in this space already offer orders of magnitude more
> capacity than we can reasonably achieve with any blockchain
> technology at this point.
> 
> I don't know what subset of use cases Bitcoin will cater to in the
> long term. They have already changed - you see way less betting
> transactions these days than a few years ago for example - and they
> will keep changing, independent of what effective block sizes we
> end up with. I don't think we should be afraid of this change or
> try to stop it.
> 
> If you look at graphs of block sizes over time (for example, 
> http://rusty.ozlabs.org/?p=498), it seems to me that there is very 
> little "organic" growth, and a lot of sudden changes (which could 
> correspond to changing defaults in miner software, introduction of 
> popular sites/services, changes in the economy). I think these can
> be seen as the economy changing to full up the available space, and
> I believe these will keep happening at any size effectively
> available.
> 
> None of this is a reason why the size can't increase. However, in
> my opinion, we should do it because we believe it increases utility
> and understand the risks; not because we're afraid of what might
> happen if we don't hurry up. And from that point of view, it seems
> silly to make a huge increase at once...
> 
> -- Pieter
> 
> 
> 
> _______________________________________________ bitcoin-dev mailing
> list bitcoin-dev@lists.linuxfoundation.org 
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAEBAgAGBQJVjWQAAAoJEGwAhlQc8H1mIRMH/Rr8v+N3XdAL/EeEXuniT+Iu
/TrtieLJKrhmMPkyIX/jAWc4ggUirzWuTMIQZ7qPwOkVrbcWPcKKHOBKTmmUaCc5
GdnA8wiiC6D6ZMamO1NKtkU2QW7Kzuna/Y4EeqBZWsKWPrMvu1vkirDYH8XRvdiC
bMksVCzoRFm7QnTMYfimrSYNxNPdwQZxCfhtJDSBnJs2Mi0J68Xpw5riVbx6S0mD
TOcNlKWosQJEub11TWeh+wD3i901t5GfxFqBNU5XGN85JRn+vAIrrm2io0bbfbIZ
y58XdqcYcWrx8MQNUdHpQT1EK5+4DAkhxrouW60sjk8jfWHGIVIgfYweDQawbOg=
=f9Fg
-----END PGP SIGNATURE-----


  reply	other threads:[~2015-06-26 14:39 UTC|newest]

Thread overview: 61+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-26 14:09 [bitcoin-dev] The need for larger blocks Pieter Wuille
2015-06-26 14:38 ` Venzen Khaosan [this message]
2015-06-26 15:22 ` Milly Bitcoin
2015-06-26 15:24   ` Pieter Wuille
2015-06-26 18:05     ` Jeff Garzik
2015-06-26 18:32       ` Milly Bitcoin
2015-06-26 15:38 ` Tom Harding
2015-06-26 16:22   ` Venzen Khaosan
2015-06-26 17:04     ` Tom Harding
2015-06-26 17:55       ` Gavin Andresen
2015-06-26 17:57 ` Jeff Garzik
2015-06-26 18:12   ` Pieter Wuille
2015-06-26 18:23     ` Jeff Garzik
2015-06-26 18:31       ` Mark Friedenbach
2015-06-26 19:05         ` Aaron Voisine
2015-06-26 18:34       ` Pieter Wuille
2015-06-26 19:18         ` Ross Nicoll
2015-06-26 19:36           ` Peter Todd
2015-06-27  6:13             ` Filipe Farinha
2015-06-27  7:14               ` Aaron Voisine
2015-06-27 15:13                 ` Peter Todd
2015-06-27 19:40                   ` Aaron Voisine
2015-06-26 18:47       ` Patrick Strateman
2015-06-26 19:03         ` Tier Nolan
2015-06-26 19:12           ` Mark Friedenbach
2015-06-26 20:44       ` Owen Gunden
2015-06-27  2:18         ` Eric Lombrozo
2015-06-27  2:54           ` Eric Lombrozo
2015-06-27  8:16           ` Venzen Khaosan
2015-06-26 18:29     ` Alex Morcos
2015-06-27  7:43 ` Wladimir J. van der Laan
2015-06-27  9:55   ` NxtChg
2015-06-27 10:04     ` Wladimir J. van der Laan
2015-06-27 10:29       ` NxtChg
2015-06-27 11:04         ` Jorge Timón
2015-06-27 11:18           ` Eric Lombrozo
2015-06-27 11:43             ` Jorge Timón
2015-06-27 12:10           ` NxtChg
2015-06-28 12:13             ` Jorge Timón
2015-06-28 13:51               ` Ivan Brightly
2015-06-28 14:13                 ` Eric Lombrozo
2015-06-28 14:16                 ` Eric Lombrozo
2015-06-28 14:22                   ` Ivan Brightly
2015-06-28 15:05                 ` Jorge Timón
2015-06-28 16:01                   ` Ivan Brightly
2015-06-28 15:28               ` s7r
2015-06-28 15:45                 ` Jorge Timón
2015-06-27 10:19     ` Venzen Khaosan
2015-06-27 19:55       ` Aaron Voisine
2015-06-28 16:37         ` Venzen Khaosan
2015-06-28 20:56           ` Aaron Voisine
2015-06-27 10:13   ` Jorge Timón
2015-06-27 12:09     ` Wladimir J. van der Laan
2015-06-27 12:15       ` NxtChg
2015-06-27 12:17         ` Greg Sanders
2015-06-27 12:25           ` NxtChg
2015-06-27 12:35             ` Greg Sanders
2015-06-27 12:25         ` Wladimir J. van der Laan
2015-06-27 12:50           ` NxtChg
2015-06-27 13:01             ` Wladimir J. van der Laan
2015-06-28 12:03       ` 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=558D6402.20300@mail.bihthai.net \
    --to=venzen@mail.bihthai.net \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=pieter.wuille@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