From: Ryan Carboni <ryan.jc.pc@gmail.com>
To: Gavin Andresen <gavinandresen@gmail.com>,
bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Monetary Authority for Bitcoin
Date: Mon, 9 Dec 2013 17:19:18 -0800 [thread overview]
Message-ID: <CAO7N=i0hoDV9zviqOHTyfeXOEWmVAu65t9MGuNo8wynL-iC=pA@mail.gmail.com> (raw)
In-Reply-To: <CABsx9T3ikXBroxvJ6F6Y+1ZpevLhSJcHJd8v5uU6AR2THmtMZA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 788 bytes --]
Bitcoin is made of many parts, yes, but not all parts were developed
simultaneously.
On Mon, Dec 9, 2013 at 2:06 PM, Gavin Andresen <gavinandresen@gmail.com>wrote:
> On Tue, Dec 10, 2013 at 8:01 AM, Ryan Carboni <ryan.jc.pc@gmail.com>wrote:
>
>> The exchanges that are kept track of could be hard coded into Bitcoin or
>> the miner could choose, how this works is not something I'm personally
>> focused on.
>>
>>
> That is like saying "We need a way to travel around the world quickly.
> There will be an anti-gravity technology; how this works is not something
> I'm personally focused on."
>
> Or, in other words, you are ignoring exactly the sticky, difficult problem
> that would have to be solved for your proposal to have any chance of
> working.
>
> --
> --
> Gavin Andresen
>
[-- Attachment #2: Type: text/html, Size: 2193 bytes --]
next prev parent reply other threads:[~2013-12-10 1:19 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 [this message]
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
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='CAO7N=i0hoDV9zviqOHTyfeXOEWmVAu65t9MGuNo8wynL-iC=pA@mail.gmail.com' \
--to=ryan.jc.pc@gmail.com \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=gavinandresen@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