1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <gmaxwell@gmail.com>) id 1WV41h-0003MC-GG
for bitcoin-development@lists.sourceforge.net;
Tue, 01 Apr 2014 19:07:13 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.215.44 as permitted sender)
client-ip=209.85.215.44; envelope-from=gmaxwell@gmail.com;
helo=mail-la0-f44.google.com;
Received: from mail-la0-f44.google.com ([209.85.215.44])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1WV41g-0006Jf-5q
for bitcoin-development@lists.sourceforge.net;
Tue, 01 Apr 2014 19:07:13 +0000
Received: by mail-la0-f44.google.com with SMTP id c6so1116496lan.17
for <bitcoin-development@lists.sourceforge.net>;
Tue, 01 Apr 2014 12:07:05 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.152.37.99 with SMTP id x3mr23528348laj.7.1396379225442; Tue,
01 Apr 2014 12:07:05 -0700 (PDT)
Received: by 10.112.89.68 with HTTP; Tue, 1 Apr 2014 12:07:05 -0700 (PDT)
In-Reply-To: <CAPg+sBh1_mYH4JNv1xTFnLsoC=qzmgi0QaLAyd7YeQ=wZQBDSQ@mail.gmail.com>
References: <CAPg+sBh1_mYH4JNv1xTFnLsoC=qzmgi0QaLAyd7YeQ=wZQBDSQ@mail.gmail.com>
Date: Tue, 1 Apr 2014 12:07:05 -0700
Message-ID: <CAAS2fgT_n-WAHLDRn8TqKB=gsj4bZeRgRAtZiUcKmPFew4MwBg@mail.gmail.com>
From: Gregory Maxwell <gmaxwell@gmail.com>
To: Pieter Wuille <pieter.wuille@gmail.com>
Content-Type: text/plain; charset=UTF-8
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
(gmaxwell[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: 1WV41g-0006Jf-5q
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Finite monetary supply for Bitcoin
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, 01 Apr 2014 19:07:13 -0000
On Tue, Apr 1, 2014 at 12:00 PM, Pieter Wuille <pieter.wuille@gmail.com> 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
A minor nitpick: It is well known that the Bitcoin core developers
are some of the most active TypeScript coders around,
E.g. http://osrc.dfm.io/sipa and http://osrc.dfm.io/gavinandresen
But I think this is an important step forward: Seminal alternative
crypto-currencies such as SolidCoin showed us that economic parameters
can be freely changed at any time, for any (or no) reason at all; and
so we should take this opportunity to demonstrate our commitment to
adopting innovative features like non-inflation regardless of their
origins in other crypto-currencies.
|
