From: Allen Piscitello <allen.piscitello@gmail•com>
To: Jameson Lopp <jameson.lopp@gmail•com>
Cc: Bitcoin Development <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Monetary Authority for Bitcoin
Date: Mon, 9 Dec 2013 19:16:18 -0600 [thread overview]
Message-ID: <CAJfRnm5O7Y7cSi4B8kCxGvdG7mNChevfyO4bFLfPU6833BXS8w@mail.gmail.com> (raw)
In-Reply-To: <52A650E5.9070801@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1910 bytes --]
I've got a better idea. Ben Bernake needs a new job. Let's just let him
set the block reward.
On Mon, Dec 9, 2013 at 5:23 PM, Jameson Lopp <jameson.lopp@gmail•com> wrote:
> To piggyback on Jeff,
>
> Any proposal that is going to add reliance upon data from third parties
> outside of the Bitcoin network itself is likely going to be rejected
> outright. This opens far too many potential vulnerabilities.
>
> "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."
>
> Yeah... you can't just gloss over a little detail like that. There must
> be consensus between the miners, otherwise a solved block will be
> rejected by a miner's peers.
> --
> Jameson Lopp
> Software Engineer
> Bronto Software, Inc
>
> On 12/09/2013 06:10 PM, Jeff Garzik wrote:
> > On Mon, Dec 9, 2013 at 7:23 PM, Ryan Carboni <ryan.jc.pc@gmail•com>
> wrote:
> >> It is not a violation of the trust of those holding the currency. Many
> >> people bought Bitcoin in the hopes that it's value in the relation of
> other
> >> currencies will increase, not because there's a fixed money supply. The
> >> majority of people using Bitcoin as a currency in exchange for real
> goods
> >> are using the exchanges.
> >
> > Your proposal has been met with widespread laughter. Were I not ill
> > with the flu, mockery would ensue as well.
> >
>
>
> ------------------------------------------------------------------------------
> 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: 2825 bytes --]
next prev parent reply other threads:[~2013-12-10 1:16 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 [this message]
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=CAJfRnm5O7Y7cSi4B8kCxGvdG7mNChevfyO4bFLfPU6833BXS8w@mail.gmail.com \
--to=allen.piscitello@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=jameson.lopp@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