From: Gregory Maxwell <gmaxwell@gmail•com>
To: Thomas Kerin <me@thomaskerin•io>
Cc: Bitcoin Development <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] BIP for standard multi-signature P2SH addresses
Date: Wed, 11 Mar 2015 20:16:13 +0000 [thread overview]
Message-ID: <CAAS2fgR_nA5p+6+wgJGLddxjswxdqqzOsPg5=s0GNEiEAYFxnQ@mail.gmail.com> (raw)
In-Reply-To: <55002AD9.2060006@thomaskerin.io>
On Wed, Mar 11, 2015 at 11:45 AM, Thomas Kerin <me@thomaskerin•io> wrote:
> I used BIP0090 as a place-holder, but I would like to request a BIP number
> for this now.
We have had repeated problems in the past with people working on and
circulating prior draft proposals squatting on each others numbers,
and each demanding access to the same numbers. As a matter of
procedure I will not assign squatted numbers, but also discussion
should come in advance of number assignment; general subject here
seems reasonable but many proposals are withdrawn by the party
tendering them after further discussion shows the effort to be without
public interest or actually subsumed by other functionality. :)
Proposals should not be called "BIP[nn]" until they're actually a BIP.
Feel free to call it bip-kerin-multisignature or any other
placeholder name that won't be confused with a finished BIP for
drafting.
If there is any public documentation on the process which caused you
specific confusion, please feel free to point me at it and I'll be
sure to fix it! Sorry for any confusion there.
next prev parent reply other threads:[~2015-03-11 20:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-11 11:45 Thomas Kerin
2015-03-11 17:16 ` Mike Hearn
2015-03-11 20:16 ` Gregory Maxwell [this message]
2015-03-11 23:24 ` Pindar Wong
2015-03-11 23:34 ` Gregory Maxwell
2015-03-11 23:50 ` Pindar Wong
2015-03-11 23:11 ` devrandom
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='CAAS2fgR_nA5p+6+wgJGLddxjswxdqqzOsPg5=s0GNEiEAYFxnQ@mail.gmail.com' \
--to=gmaxwell@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=me@thomaskerin$(echo .)io \
/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