public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@bitpay.com>
To: Baz <bk@thinkloop.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>,
	Ryan Carboni <ryan.jc.pc@gmail.com>
Subject: Re: [Bitcoin-development] Monetary Authority for Bitcoin
Date: Tue, 10 Dec 2013 20:01:52 -0500	[thread overview]
Message-ID: <CAJHLa0NTv15M691i3p4gOsWc+-zV_wo+_suh0y+JG8rKu4mEaA@mail.gmail.com> (raw)
In-Reply-To: <CAAsce+vzR_TGX5x9GaGGZLNh4ML4LO_mZPH0O1inhi0ag7sXVw@mail.gmail.com>

It is simpler than that; simple numbers.  Bitcoin is volatile right
now, not for fundamental architecture reasons, but for reasons why
many other small issues are volatile.  Low liquidity and a small issue
implies that a single big player can easily the move the market.
Further, it is volatile because common financial tools available
elsewhere -- shorting, futures/options, etc. -- are not widely and
easily available.

None of these factors are special or specific to bitcoin.  See
http://garzikrants.blogspot.com/2013/11/solution-to-bitcoin-volatility.html

However, this is getting WAY off-topic for a development mailing list.

Ryan successfully trolled the list.  Let's not further feed the trolls.


On Tue, Dec 10, 2013 at 7:07 PM, Baz <bk@thinkloop.com> wrote:
> Bitcoin's volatility is not a symptom of its architecture, but a reflection
> of the collective knowledge of its future acceptance. Currently that
> knowledge is based on very volatile sources: how some senator feels about it
> this morning, which direction departments in the Chinese government are
> leaning. The issue is that proof-of-work is missing from society's end. As
> time goes on, laws, regulations and policies will start to form, people will
> challenge them, they will be reviewed and updated, they will be challenged
> again on different grounds, re-reviewed, and so on. Each of those
> confirmations will make it that much harder to change earlier confirmations.
> It won't matter anymore what some senator thinks this morning because she
> will have months of hard-work ahead of her before she can affect any change.
> It also doesn't matter if the rulings are positive or negative, just having
> them will add stability to Bitcoin at some value between $0.0001 to $100,000
> per coin.
>
>
>
>
> On Tue, Dec 10, 2013 at 4:38 AM, Jorge Timón <jtimon@monetize.io> wrote:
>>
>> On 12/10/13, Ryan Carboni <ryan.jc.pc@gmail.com> wrote:
>> > You're just closed minded.
>>
>> No, at least to persons have explained you why your proposal is not
>> feasible.
>> If you wanted to learn, you would have made questions on why those
>> parts of your proposal are unfeasible.
>> There have been many proposals about "stablecoins" in bitcointalk and
>> other forums (for example, the "initial proposals" freicoin subforum).
>> I have participated in several of them trying to find a solution and
>> I'm now convinced that this is impossible to implement in a secure AND
>> P2P system.
>>
>> This is off-topic for this forum, specially if (as you've shown to us)
>> you are not interested in learning why this proposal is unfeasible.
>>
>> --
>> Jorge Timón
>>
>> http://freico.in/
>>
>>
>> ------------------------------------------------------------------------------
>> Sponsored by Intel(R) XDK
>> Develop, test and display web and hybrid apps with a single code base.
>> Download it for free now!
>>
>> http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk
>> _______________________________________________
>> Bitcoin-development mailing list
>> Bitcoin-development@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>



-- 
Jeff Garzik
Bitcoin core developer and open source evangelist
BitPay, Inc.      https://bitpay.com/



  reply	other threads:[~2013-12-11  1:02 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-09 22:01 [Bitcoin-development] Monetary Authority for Bitcoin Ryan Carboni
2013-12-09 22:06 ` Gavin Andresen
2013-12-10  1:19   ` Ryan Carboni
2013-12-10  4:05   ` Rick Wesson
     [not found] ` <20131209221130.GA22556@shavo.dd-wrt>
2013-12-09 22:23   ` Ryan Carboni
2013-12-09 22:57     ` Mike Caldwell
2013-12-10  8:19       ` Wladimir
2013-12-09 23:10     ` Jeff Garzik
2013-12-09 23:23       ` Jameson Lopp
2013-12-10  1:16         ` Allen Piscitello
2013-12-10  1:20       ` Ryan Carboni
2013-12-10 12:38         ` Jorge Timón
2013-12-11  0:07           ` Baz
2013-12-11  1:01             ` Jeff Garzik [this message]
2013-12-10  1:22 ` kjj

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=CAJHLa0NTv15M691i3p4gOsWc+-zV_wo+_suh0y+JG8rKu4mEaA@mail.gmail.com \
    --to=jgarzik@bitpay.com \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=bk@thinkloop.com \
    --cc=ryan.jc.pc@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