From: Gavin Andresen <gavinandresen@gmail•com>
To: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Bitcoin Enhancement Proposals (BEPS)
Date: Mon, 19 Sep 2011 12:57:58 -0400 [thread overview]
Message-ID: <CABsx9T0y601kjJ7ToczwhcQUoh3NZbuPa+iWwtm6-DZxZSRNPg@mail.gmail.com> (raw)
In-Reply-To: <21269.192.251.226.206.1316448084.squirrel@lavabit.com>
New 'standard' transaction forms would be perfect candidates for BEPS.
I think we aught to have a formal proposal to separate the protocol
version from the client version, too.
--
Does anybody besides me think maybe we should name them something
other than "BEP" ?
I'm worried we'll regret it in two years when a google for "BEP003"
takes you to the BitTorrent EPs instead of the BitCoin EPs.
Maybe "BIP" == Bitcoin Improvement Proposal
or "PEB" == Proposal to Enhance Bitcoin
or "BER" == Bitcoin Enhancement Request
I think I like "BIP" (PEB sounds like a diet soda, and I don't know
if BER should be pronounced "bear" or "beer").
I generally don't care about names, but it seems like a little
planning now might save some confusion later. And I don't want the
BitTorrent folks to get pissed off at us for 'stealing' their acronym,
either.
--
--
Gavin Andresen
next prev parent reply other threads:[~2011-09-19 16:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-19 1:04 Luke-Jr
2011-09-19 3:22 ` Alex Waters
2011-09-19 16:01 ` bgroff
2011-09-19 16:57 ` Gavin Andresen [this message]
2011-09-19 17:23 ` Alex Waters
2011-09-20 2:06 ` Amir Taaki
2011-09-23 19:45 ` Daniel F
2011-09-25 3:27 ` Amir Taaki
-- strict thread matches above, loose matches on Subject: below --
2011-09-19 0:31 Amir Taaki
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=CABsx9T0y601kjJ7ToczwhcQUoh3NZbuPa+iWwtm6-DZxZSRNPg@mail.gmail.com \
--to=gavinandresen@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/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