From: Matt Corallo <bitcoin-list@bluematt.me>
To: Gregory Maxwell <gmaxwell@gmail.com>,
Pieter Wuille <pieter.wuille@gmail.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Finite monetary supply for Bitcoin
Date: Tue, 01 Apr 2014 17:51:16 -0400 [thread overview]
Message-ID: <0fe42ca1-2688-4d4c-9ba5-e9e3d97f9f8c@email.android.com> (raw)
In-Reply-To: <CAAS2fgTQbeeDwheRQPw=osOZ8LLQFsiteRQPdavE6iNnuGLtAA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1152 bytes --]
I move to reclaim bip 42 as reserved for a bip containing either a reference to musical dolphins or towels in the name.
Matt
On April 1, 2014 5:47:34 PM EDT, Gregory Maxwell <gmaxwell@gmail.com> wrote:
>On Tue, Apr 1, 2014 at 1:53 PM, Pieter Wuille <pieter.wuille@gmail.com>
>wrote:
>> 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.
>
>With ten people commenting on this proposal there are quite a few ways
>in which you could partition their views. Only one possible integer
>partitioning has everyone in the same partition, so consensus seems
>unlikely.
>
>But owing to a rather large bribe (or at least not less large than any
>other offered by competing parties) I hereby assign BIP 42 for this
>proposal.
>
>------------------------------------------------------------------------------
>_______________________________________________
>Bitcoin-development mailing list
>Bitcoin-development@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/bitcoin-development
[-- Attachment #2: Type: text/html, Size: 1564 bytes --]
next prev parent reply other threads:[~2014-04-01 21:51 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
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 [this message]
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=0fe42ca1-2688-4d4c-9ba5-e9e3d97f9f8c@email.android.com \
--to=bitcoin-list@bluematt.me \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=gmaxwell@gmail.com \
--cc=pieter.wuille@gmail.com \
/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