Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.161.47 as permitted sender)
	client-ip=209.85.161.47; envelope-from=gavinandresen@gmail.com;
	helo=mail-fx0-f47.google.com; 
MIME-Version: 1.0
In-Reply-To: <21269.192.251.226.206.1316448084.squirrel@lavabit.com>
References: <201109182104.45994.luke@dashjr.org>
	<CAL0fb61B6bqGMhWtCgvy0xwfHQ_nvmhbb9uLJQWx3biENhVJNw@mail.gmail.com>
	<21269.192.251.226.206.1316448084.squirrel@lavabit.com>
Date: Mon, 19 Sep 2011 12:57:58 -0400
Message-ID: <CABsx9T0y601kjJ7ToczwhcQUoh3NZbuPa+iWwtm6-DZxZSRNPg@mail.gmail.com>
From: Gavin Andresen <gavinandresen@gmail.com>
To: bitcoin-development@lists.sourceforge.net
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [Bitcoin-development] Bitcoin Enhancement Proposals (BEPS)
Precedence: list

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