From: Aaron Voisine <voisine@gmail•com>
To: venzen@mail•bihthai.net
Subject: Re: [bitcoin-dev] The need for larger blocks
Date: Sun, 28 Jun 2015 13:56:20 -0700 [thread overview]
Message-ID: <CACq0ZD5+4f19MCoiDxu8R7oHVki8VnA_f0TdUNGgnyk5PoJ+Mw@mail.gmail.com> (raw)
In-Reply-To: <559022BE.2060503@mail.bihthai.net>
[-- Attachment #1: Type: text/plain, Size: 2736 bytes --]
Moving the list to BCC, since this isn't really a technical discussion.
On Sun, Jun 28, 2015 at 9:37 AM, Venzen Khaosan <venzen@mail•bihthai.net>
wrote:
>
> Bitcoin's exchange rate, as a commodity money floating freely in the
> market, will go up and down according to speculative cycles and we
> should conceptually separate its valuation in fiat terms, from its
> fundamental value which is: mathematical consensus, cryptographic
> transaction security and censorship resistance, etc.
I get the feeling we might be reasoning from different underlying
assumptions, but I don't think you can separate value that way. Those
fundamental properties were chosen to serve the goal of creating a digital
commodity money. They are useful only in as much as they serve ends that
people value. Consensus, security, censorship resistance are valuable
because they are desirable properties for money to have.
If you want to argue that the properties of bitcoin are valuable for other
things besides money, that's fine, but those other uses presumably can be
accomplished with tiny amounts of bitcoin, so don't appreciably increase
demand.
> These values are
> critically reliant on Bitcoin's *degree of decentralization* for them
> to remain true and for Bitcoin to retain its meaning, and, therefore,
> its value. That is what I point out when I say "greater adoption has
> not reflected in the price chart". And that may remain the case for
> evermore because the value is in the protocol, the blockchain and its
> utility and degree of decentralization, not in the chart or the size
> of the user base
>
I think it depends on what you mean by "adoption". Adoption as a
store-of-value must necessarily increase the market price given the
restricted and eventually fixed supply. If we're talking about merchant
adoption as a payment system, or increased transaction volume, the yes,
these things have no direct impact on the price. They only impact the price
indirectly in as much as they encourage further adoption as a
store-of-value.
> I argue that we already know what the value of Bitcoin is. In its
> current form Bitcoin most likely fulfills 80% or 90% of its eventual
> fully evolved value. Increased adoption will not strengthen the
> fundamentals, so let's proceed with scaling that will safeguard
> Bitcoin's fundamental value and implement protections that ensure
> quality of decentralization.
>
Increased adoption does strengthen the fundamentals. The most important
fundamental for money is how many other people standardize on the same
money, and want to hold it. This drives it's price in terms of other
commodities. You want to hold what everyone else wants to hold.
Aaron Voisine
co-founder and CEO
breadwallet.com
[-- Attachment #2: Type: text/html, Size: 3790 bytes --]
next prev parent reply other threads:[~2015-06-28 20:56 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
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 [this message]
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=CACq0ZD5+4f19MCoiDxu8R7oHVki8VnA_f0TdUNGgnyk5PoJ+Mw@mail.gmail.com \
--to=voisine@gmail$(echo .)com \
--cc=venzen@mail$(echo .)bihthai.net \
/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