From: Pindar Wong <pindar.wong@gmail•com>
To: Gregory Maxwell <gmaxwell@gmail•com>
Cc: Bitcoin Development <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] BIP for standard multi-signature P2SH addresses
Date: Thu, 12 Mar 2015 07:24:59 +0800 [thread overview]
Message-ID: <CAM7BtUqE4cq3EMHitL-ms3YaDE79=RF09f1eiLc023t8u=GySA@mail.gmail.com> (raw)
In-Reply-To: <CAAS2fgR_nA5p+6+wgJGLddxjswxdqqzOsPg5=s0GNEiEAYFxnQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2233 bytes --]
Hi,
Perhaps at some point consider introducing something akin to a
'Bitcoin-Draft' (BD) status with some autoexpiry period?
I understand that the Internet Engineering Task Force (IETF)
<http://www.ietf.org> has the concept of 'Internet Drafts" (ID)
<http://www.ietf.org/ietf-ftp/1id-guidelines.txt> and this looks like it
has worked for them so far.
m2c.
p.
On Thu, Mar 12, 2015 at 4:16 AM, Gregory Maxwell <gmaxwell@gmail•com> wrote:
> 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.
>
>
> ------------------------------------------------------------------------------
> Dive into the World of Parallel Programming The Go Parallel Website,
> sponsored
> by Intel and developed in partnership with Slashdot Media, is your hub for
> all
> things parallel software development, from weekly thought leadership blogs
> to
> news, videos, case studies, tutorials and more. Take a look and join the
> conversation now. http://goparallel.sourceforge.net/
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists•sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
[-- Attachment #2: Type: text/html, Size: 3051 bytes --]
next prev parent reply other threads:[~2015-03-11 23:25 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
2015-03-11 23:24 ` Pindar Wong [this message]
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='CAM7BtUqE4cq3EMHitL-ms3YaDE79=RF09f1eiLc023t8u=GySA@mail.gmail.com' \
--to=pindar.wong@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=gmaxwell@gmail$(echo .)com \
/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