From: "Jorge Timón" <jtimon@monetize•io>
To: Matt Corallo <bitcoin-list@bluematt•me>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Finite monetary supply for Bitcoin
Date: Tue, 1 Apr 2014 23:42:53 +0200 [thread overview]
Message-ID: <CAC1+kJPJMoM8jJZi4vmHw3x0-xEG59YGBQYpqOFmr8hOU835ng@mail.gmail.com> (raw)
In-Reply-To: <646363bb-9e42-4faf-a77f-3d57e7553376@email.android.com>
On 4/1/14, Matt Corallo <bitcoin-list@bluematt•me> wrote:
> Also, should we really do this with a soft fork when we can take this
> opportunity to redesign the whole system with a hard fork? This is out
> chance to switch to a whole new script engine!
+1
The hard fork also forces the whole community and not a few miners to decide.
Well, if it is possible for the community to reach an agreement with
such a short time frame...
> 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,
>>
>>--
>>Pieter
>>
>>------------------------------------------------------------------------------
>>_______________________________________________
>>Bitcoin-development mailing list
>>Bitcoin-development@lists•sourceforge.net
>>https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
--
Jorge Timón
http://freico.in/
next prev parent reply other threads:[~2014-04-01 21:43 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 [this message]
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
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=CAC1+kJPJMoM8jJZi4vmHw3x0-xEG59YGBQYpqOFmr8hOU835ng@mail.gmail.com \
--to=jtimon@monetize$(echo .)io \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=bitcoin-list@bluematt$(echo .)me \
/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