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
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <bitcoin-list@bluematt.me>) id 1WV4Th-0006JW-K3
for bitcoin-development@lists.sourceforge.net;
Tue, 01 Apr 2014 19:36:09 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of bluematt.me
designates 192.241.179.72 as permitted sender)
client-ip=192.241.179.72; envelope-from=bitcoin-list@bluematt.me;
helo=mail.bluematt.me;
Received: from mail.bluematt.me ([192.241.179.72])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256)
(Exim 4.76) id 1WV4Tg-0007tP-BW
for bitcoin-development@lists.sourceforge.net;
Tue, 01 Apr 2014 19:36:09 +0000
Received: from [22.195.238.60] (unknown [172.56.4.231])
by mail.bluematt.me (Postfix) with ESMTPSA id 748324B7C3;
Tue, 1 Apr 2014 19:11:03 +0000 (UTC)
User-Agent: K-9 Mail for Android
In-Reply-To: <CAPg+sBh1_mYH4JNv1xTFnLsoC=qzmgi0QaLAyd7YeQ=wZQBDSQ@mail.gmail.com>
References: <CAPg+sBh1_mYH4JNv1xTFnLsoC=qzmgi0QaLAyd7YeQ=wZQBDSQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="----XBT0TX858IS21RMJQD6MQZDWXSZXZI"
From: Matt Corallo <bitcoin-list@bluematt.me>
Date: Tue, 01 Apr 2014 15:11:01 -0400
To: Pieter Wuille <pieter.wuille@gmail.com>,
Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Message-ID: <646363bb-9e42-4faf-a77f-3d57e7553376@email.android.com>
Content-Transfer-Encoding: 7bit
X-Spam-Score: -1.1 (-)
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 SPF_PASS SPF: sender matches SPF record
-0.6 RP_MATCHES_RCVD Envelope sender domain matches handover relay
domain 1.0 HTML_MESSAGE BODY: HTML included in message
X-Headers-End: 1WV4Tg-0007tP-BW
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:36:09 -0000
------XBT0TX858IS21RMJQD6MQZDWXSZXZI
Content-Type: text/plain;
charset=UTF-8
Content-Transfer-Encoding: quoted-printable
I disagree with this proposal both in spirit and in practice.
We all know satoshi was the best programmer like no one ever was. Clearly=
he intended this monetary supply from the beginning, who are we but mere=
mortals to go against satoshi's will?
Also, should we really do this with a soft fork when we can take this opp=
ortunity to redesign the whole system with a hard fork? This is out chanc=
e to switch to a whole new script engine!
Matt
On April 1, 2014 3:00:07 PM EDT, 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
>
>Please comment!
>
>Thanks,
>
>--=20
>Pieter
>
>------------------------------------------------------------------------=
------
>_______________________________________________
>Bitcoin-development mailing list
>Bitcoin-development@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/bitcoin-development
------XBT0TX858IS21RMJQD6MQZDWXSZXZI
Content-Type: text/html;
charset=utf-8
Content-Transfer-Encoding: quoted-printable
<html><head></head><body>I disagree with this proposal both in spirit and=
in practice.<br>
<br>
We all know satoshi was the best programmer like no one ever was. Clearly=
he intended this monetary supply from the beginning, who are we but mere=
mortals to go against satoshi's will?<br>
<br>
Also, should we really do this with a soft fork when we can take this opp=
ortunity to redesign the whole system with a hard fork? This is out chanc=
e to switch to a whole new script engine!<br>
<br>
Matt<br><br><div class=3D"gmail_quote">On April 1, 2014 3:00:07 PM EDT, P=
ieter Wuille <pieter.wuille@gmail.com> wrote:<blockquote class=3D"g=
mail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rg=
b(204, 204, 204); padding-left: 1ex;">
<pre class=3D"k9mail">Hi all,<br /><br />I understand this is a controver=
sial proposal, but bear with me please.<br /><br />I believe we cannot ac=
cept the current subsidy schedule anymore, so I<br />wrote a small draft =
BIP with a proposal to turn Bitcoin into a<br />limited-supply currency. =
Dogecoin has already shown how easy such<br />changes are, so I consider =
this a worthwhile idea to be explored.<br /><br />The text can be found h=
ere: <a href=3D"https://gist.github.com/sipa/9920696">https://gist.github=
.com/sipa/9920696</a><br /><br />Please comment!<br /><br />Thanks,<br />=
</pre></blockquote></div></body></html>
------XBT0TX858IS21RMJQD6MQZDWXSZXZI--
|
