From: Peter Todd <pete@petertodd•org>
To: Pieter Wuille <pieter.wuille@gmail•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Finite monetary supply for Bitcoin
Date: Tue, 1 Apr 2014 22:00:39 +0200 [thread overview]
Message-ID: <20140401200039.GA10403@tilt> (raw)
In-Reply-To: <CAPg+sBh1_mYH4JNv1xTFnLsoC=qzmgi0QaLAyd7YeQ=wZQBDSQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2058 bytes --]
On Tue, Apr 01, 2014 at 09:00:07PM +0200, Pieter Wuille wrote:
> Hi all,
>
> I understand this is a controversial proposal, but bear with me please.
>
> I believe we cannot accept the current subsidy schedule anymore, so I
> wrote a small draft BIP with a proposal to turn Bitcoin into a
> limited-supply currency. Dogecoin has already shown how easy such
> changes are, so I consider this a worthwhile idea to be explored.
>
> The text can be found here: https://gist.github.com/sipa/9920696
What's interesting about this bug is we could also fix the problem - the
economic shock - by first implementing the OP_CHECKLOCKTIMEVERIFY opcode
in a soft-fork, followed by a second soft-fork requiring miners to
"pay-forward" a percentage of their coinbase outputs to the future.
(remember that whomever mines a block controls what
recently-made-available anyone-can-spend txouts are included in their
block) We could then pick the distribution rate fairly arbitrarily; I
propose the following linear distribution:
Each gold mine produces 21,000,000 coins over 210,000*64 blocks, or
1.5625 BTC/block evenly distributed. Measured as an absolute against the
monetary the inflation rate will converge towards zero; measured against
the actual economic monetary supply the value will converge towards some
low value of inflation. In the short run we get an immediate reduction
in inflation, which can help our currently sluggish price. Either
outcome should be acceptable to any reasonable goldbug - fortunately our
community is almost entirely made up of such calm and reasonable people.
Meanwhile maintaining a miner reward has significant advantages in terms
of the long-term sustainability of the system - everyone needs PoW
security regardless of whether or not you do transactions, thus we
should all pay into it.
As for your example of Python, I'm sure they'll accept a pull-req
changing the behavior in the language.
--
'peter'[:-1]@petertodd.org
0000000000000000f4f5ba334791a4102917e4d3f22f6ad7f2c4f15d97307fe2
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 665 bytes --]
next prev parent reply other threads:[~2014-04-01 20:00 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-01 19:00 Pieter Wuille
2014-04-01 19:04 ` Matt Whitlock
2014-04-01 20:59 ` Pieter Wuille
2014-04-04 3:41 ` kjj
2014-04-04 7:01 ` Wladimir
2014-04-04 13:19 ` Jeff Garzik
2014-04-05 10:21 ` Jorge Timón
2014-04-05 10:40 ` Matt Whitlock
2014-04-05 11:28 ` Jorge Timón
2014-04-05 11:28 ` Wladimir
2014-04-05 15:54 ` Daryl Tucker
2014-04-05 17:29 ` Gregory Maxwell
2014-04-01 19:07 ` Gregory Maxwell
2014-04-01 19:09 ` Tamas Blummer
2014-04-01 19:09 ` Mike Hearn
2014-04-01 19:11 ` Matt Corallo
2014-04-01 21:42 ` Jorge Timón
2014-04-01 19:12 ` Luke-Jr
2014-04-01 19:16 ` Benjamin Cordes
2014-04-01 19:19 ` Luke-Jr
2014-04-01 20:00 ` Peter Todd [this message]
2014-04-01 20:53 ` Pieter Wuille
2014-04-01 21:47 ` Gregory Maxwell
2014-04-01 21:51 ` Daryl Banttari
2014-04-01 22:03 ` Jeff Garzik
2014-04-01 21:51 ` Matt Corallo
2014-04-01 22:37 ` Pieter Wuille
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=20140401200039.GA10403@tilt \
--to=pete@petertodd$(echo .)org \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=pieter.wuille@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