From: Jameson Lopp <jameson.lopp@gmail.com>
To: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Popularity based mining (variable block reward)
Date: Tue, 10 Dec 2013 11:27:26 -0500 [thread overview]
Message-ID: <52A740EE.1020605@gmail.com> (raw)
In-Reply-To: <CA+n47WKrAwbzb31YrHfytdNjKax9ixR2nT1Etw+UxsjLHqH08g@mail.gmail.com>
"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.
next prev parent reply other threads:[~2013-12-10 16:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-10 16:23 [Bitcoin-development] Popularity based mining (variable block reward) Jan Kučera
2013-12-10 16:27 ` Jameson Lopp [this message]
2013-12-10 17:18 ` Jorge Timón
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=52A740EE.1020605@gmail.com \
--to=jameson.lopp@gmail.com \
--cc=bitcoin-development@lists.sourceforge.net \
/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