public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Venzen Khaosan <venzen@mail•bihthai.net>
To: Tom Harding <tomh@thinlink•com>,  bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] The need for larger blocks
Date: Fri, 26 Jun 2015 23:22:17 +0700	[thread overview]
Message-ID: <558D7C39.6010603@mail.bihthai.net> (raw)
In-Reply-To: <558D71EF.1060603@thinlink.com>

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

Apologies in advance for pulling you up on your statement, Tom, I've
noticed you're a regular and well respected poster in this list:

"free market" who?

Are you aware that the Bitcoin rally of 2013 was a result of
speculation by elements in Citi Bank, JPMorgan, and by many other Wall
Street trading desk managers who saw the opportunity of a
free-floating, unregulated commodity?

If the intention is to leave Bitcoin to the "free market" it already
is, and has been there for some time.

As for miners, those are finance capitalist interest too - if not
currently, in their majority, then eventually in China and the rest of
the world, so what does the term "free market" really mean? It must be
defined, because you are speaking to developers here, not visionary
economists or politicized brains, necessarily.

We cannot speak about "the market" without referencing concerns about
centralization, because any centralized business that plays the game
right seeks, by the rules, to corner the market. If they cannot do it
alone, they will seek allies.

"Free market" means as much under capitalism as "open democracy" under
Stalinism. Do you see my point? "Free Market" is a multivariate term
and Bitcoin does not (and should not have to) cater to all its
demands. That's like applying Microsoft standards to FOSS efforts -
becuase that's the "business use-case".

Bitcoin developers have to think about economy in an informed manner
and make provision with protection, else one can just make like Mike
Hearn and jump up and down shouting "faster-faster more-more".
Economics, markets and speculation is more complicated than that.

Venzen


On 06/26/2015 10:38 PM, Tom Harding wrote:
> On 6/26/2015 7:09 AM, Pieter Wuille wrote:
>> 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.
> 
> "Reasonably achievable" is a guideline that would keep bitcoin out
> of trouble caused by either too little, or too much, declared
> capacity. This matches Gavin's thinking, though you may differ on
> the numbers.
> 
> 
>> it seems silly to make a huge increase at once...
> 
> Unless it is reasonably achievable.  Leave the rest to the free
> market.
> 
> 
> 
> _______________________________________________ bitcoin-dev mailing
> list bitcoin-dev@lists•linuxfoundation.org 
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAEBAgAGBQJVjXw4AAoJEGwAhlQc8H1mX2kIAJCLodhsEhkzxkzZl1hUITkZ
fFZWuiKomsHTHU+6cCr0snt0VDI7+mP8SgyawWrwXNKdGKqpiUAX+B454I9POYBQ
pf/CUq/sWMFN/WRO1EYpVBz3zH/mDgMUZeLvnGYti05+3YzxJxBsy2cmkX5HCfUL
oUErqWEo+OjeQNT+ZgFSbYYLSBLO2fDJglPzXD4eTF6RrK3AsZpHgnVqQzlAC+4G
Q7zRQN/h3voXJ5ed684Hy8bb04KKsEo0EYx2Nz6Hd9mGkSnnqydIa8ieJO3ChYyi
IDyJVXpDOth0TshZARbTFuicYg0ULUmU/l5x38Z3HFp9J1G4GFhnoivBwRozlQ8=
=a+o4
-----END PGP SIGNATURE-----


  reply	other threads:[~2015-06-26 16:22 UTC|newest]

Thread overview: 61+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-26 14:09 Pieter Wuille
2015-06-26 14:38 ` Venzen Khaosan
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 [this message]
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=558D7C39.6010603@mail.bihthai.net \
    --to=venzen@mail$(echo .)bihthai.net \
    --cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
    --cc=tomh@thinlink$(echo .)com \
    /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