From: "Luke-Jr" <luke@dashjr.org>
To: Benjamin Cordes <benjamin.l.cordes@gmail.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Finite monetary supply for Bitcoin
Date: Tue, 1 Apr 2014 19:19:01 +0000 [thread overview]
Message-ID: <201404011919.01918.luke@dashjr.org> (raw)
In-Reply-To: <CAOoPuRYem0HEAmz4spzUHzEBTQ3TV9KurLd_TeY2SfknePjLWw@mail.gmail.com>
Please, *music* is obsolete, but inline replies *are not*!
On Tuesday, April 01, 2014 7:16:42 PM Benjamin Cordes wrote:
> luke, you might enjoy the book Topos of Music. It's a complete
> mathematical music theory by a student of Grothendieck. He advanced
> Euler's theories of harmony based on advanced category theory. I'm
> sure there are many applications to Bitcoin.
>
> On Tue, Apr 1, 2014 at 9:12 PM, Luke-Jr <luke@dashjr.org> wrote:
> > On Tuesday, April 01, 2014 7:00:07 PM 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
> >>
> >> Please comment!
> >
> > I cleaned it up a bit. By 2214, we should be using tonal numbers after
> > all:
> >
> > https://gist.github.com/luke-jr/9920788
> >
> > -------------------------------------------------------------------------
> > ----- _______________________________________________
> > Bitcoin-development mailing list
> > Bitcoin-development@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/bitcoin-development
next prev parent reply other threads:[~2014-04-01 19:19 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-01 19:00 [Bitcoin-development] Finite monetary supply for Bitcoin 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 [this message]
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=201404011919.01918.luke@dashjr.org \
--to=luke@dashjr.org \
--cc=benjamin.l.cordes@gmail.com \
--cc=bitcoin-development@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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