From: Pieter Wuille <pieter.wuille@gmail•com>
To: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Finite monetary supply for Bitcoin
Date: Tue, 1 Apr 2014 22:53:37 +0200 [thread overview]
Message-ID: <CAPg+sBgiqT9MARkSdTVCe37Kpkyj3-Uwe66a5U+HGnOtU6Qc7A@mail.gmail.com> (raw)
In-Reply-To: <20140401200039.GA10403@tilt>
On Tue, Apr 1, 2014 at 10:00 PM, Peter Todd <pete@petertodd•org> wrote:
> On Tue, Apr 01, 2014 at 09:00:07PM +0200, Pieter Wuille wrote:
>> 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:
Interesting idea, but perhaps we can keep that change for a future
hard fork, as Matt suggested? That means it could be implemented much
more concisely too.
Mike, I'm sad to hear you feel that way. I'll move your name in the
document from ACKnowledgements to NAKnowledgements.
As this is a relatively urgent matter - we risk forks within 250 years
otherwise, I'd like to move this forward quickly.
In case there are no further objections (excluding from people who
disagree with me), I'd like to request a BIP number for this. Any
number is fine, I guess, as long as it's finite.
--
Pieter
next prev parent reply other threads:[~2014-04-01 20:53 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
2014-04-01 20:53 ` Pieter Wuille [this message]
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=CAPg+sBgiqT9MARkSdTVCe37Kpkyj3-Uwe66a5U+HGnOtU6Qc7A@mail.gmail.com \
--to=pieter.wuille@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/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