public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Baz <bk@thinkloop•com>
To: "Jorge Timón" <jtimon@monetize•io>
Cc: 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 16:07:19 -0800	[thread overview]
Message-ID: <CAAsce+vzR_TGX5x9GaGGZLNh4ML4LO_mZPH0O1inhi0ag7sXVw@mail.gmail.com> (raw)
In-Reply-To: <CAC1+kJNbSn_3p9Pu_geyb0nYhE10mLkpJ1o-4BzR-w2p5e_5pQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2376 bytes --]

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
>

[-- Attachment #2: Type: text/html, Size: 3264 bytes --]

  reply	other threads:[~2013-12-11  0:37 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-09 22:01 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 [this message]
2013-12-11  1:01             ` Jeff Garzik
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=CAAsce+vzR_TGX5x9GaGGZLNh4ML4LO_mZPH0O1inhi0ag7sXVw@mail.gmail.com \
    --to=bk@thinkloop$(echo .)com \
    --cc=bitcoin-development@lists$(echo .)sourceforge.net \
    --cc=jtimon@monetize$(echo .)io \
    --cc=ryan.jc.pc@gmail$(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