From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1VqAAe-0004ZJ-JN for bitcoin-development@lists.sourceforge.net; Mon, 09 Dec 2013 23:23:24 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.216.182 as permitted sender) client-ip=209.85.216.182; envelope-from=jameson.lopp@gmail.com; helo=mail-qc0-f182.google.com; Received: from mail-qc0-f182.google.com ([209.85.216.182]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1VqAAd-0001md-TQ for bitcoin-development@lists.sourceforge.net; Mon, 09 Dec 2013 23:23:24 +0000 Received: by mail-qc0-f182.google.com with SMTP id e16so3367404qcx.27 for ; Mon, 09 Dec 2013 15:23:18 -0800 (PST) X-Received: by 10.224.47.137 with SMTP id n9mr39525039qaf.47.1386631398433; Mon, 09 Dec 2013 15:23:18 -0800 (PST) Received: from [192.168.0.13] (cpe-076-182-064-253.nc.res.rr.com. [76.182.64.253]) by mx.google.com with ESMTPSA id z16sm23836611qab.3.2013.12.09.15.23.17 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 09 Dec 2013 15:23:17 -0800 (PST) Message-ID: <52A650E5.9070801@gmail.com> Date: Mon, 09 Dec 2013 18:23:17 -0500 From: Jameson Lopp User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.1.1 MIME-Version: 1.0 To: bitcoin-development@lists.sourceforge.net References: <20131209221130.GA22556@shavo.dd-wrt> In-Reply-To: X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Spam-Score: -1.6 (-) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (jameson.lopp[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature X-Headers-End: 1VqAAd-0001md-TQ Subject: Re: [Bitcoin-development] Monetary Authority for Bitcoin X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Dec 2013 23:23:24 -0000 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 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. >