Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
	helo=mx.sourceforge.net)
	by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <jameson.lopp@gmail.com>) id 1VqQ9l-0004lN-QL
	for bitcoin-development@lists.sourceforge.net;
	Tue, 10 Dec 2013 16:27:33 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.213.52 as permitted sender)
	client-ip=209.85.213.52; envelope-from=jameson.lopp@gmail.com;
	helo=mail-yh0-f52.google.com; 
Received: from mail-yh0-f52.google.com ([209.85.213.52])
	by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1VqQ9l-0007fO-45
	for bitcoin-development@lists.sourceforge.net;
	Tue, 10 Dec 2013 16:27:33 +0000
Received: by mail-yh0-f52.google.com with SMTP id i72so3962374yha.11
	for <bitcoin-development@lists.sourceforge.net>;
	Tue, 10 Dec 2013 08:27:27 -0800 (PST)
X-Received: by 10.236.115.73 with SMTP id d49mr20425366yhh.12.1386692847542;
	Tue, 10 Dec 2013 08:27:27 -0800 (PST)
Received: from [192.168.119.206] (BRONTO-SOFT.car1.Raleigh1.Level3.net.
	[4.59.160.2])
	by mx.google.com with ESMTPSA id w45sm23201439yhk.4.2013.12.10.08.27.26
	for <bitcoin-development@lists.sourceforge.net>
	(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
	Tue, 10 Dec 2013 08:27:27 -0800 (PST)
Message-ID: <52A740EE.1020605@gmail.com>
Date: Tue, 10 Dec 2013 11:27:26 -0500
From: Jameson Lopp <jameson.lopp@gmail.com>
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: <CA+n47WKrAwbzb31YrHfytdNjKax9ixR2nT1Etw+UxsjLHqH08g@mail.gmail.com>
In-Reply-To: <CA+n47WKrAwbzb31YrHfytdNjKax9ixR2nT1Etw+UxsjLHqH08g@mail.gmail.com>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
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: 1VqQ9l-0007fO-45
Subject: Re: [Bitcoin-development] Popularity based mining (variable block
 reward)
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Tue, 10 Dec 2013 16:27:34 -0000


"no reliance on external data" ... "depending on various factors (coin
valuation/exchange rate"

ಠ_ಠ
--
Jameson Lopp
Software Engineer
Bronto Software

On 12/10/2013 11:23 AM, Jan Kučera wrote:
> Basically there would be no reliance on external data as the network itself
> would decide on reward height and everybody node would be free to do so.
> Each network node would determine the popularity on its own depending on
> various factors (coin valuation/exchange rate, number of transactions and
> many others) and basically come up with its own block reward value.