Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1R5hZa-0007fz-8z for bitcoin-development@lists.sourceforge.net; Mon, 19 Sep 2011 17:24:02 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.216.42 as permitted sender) client-ip=209.85.216.42; envelope-from=ampedal@gmail.com; helo=mail-qw0-f42.google.com; Received: from mail-qw0-f42.google.com ([209.85.216.42]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1R5hZZ-0004bb-FV for bitcoin-development@lists.sourceforge.net; Mon, 19 Sep 2011 17:24:02 +0000 Received: by qwi4 with SMTP id 4so17714500qwi.1 for ; Mon, 19 Sep 2011 10:23:56 -0700 (PDT) MIME-Version: 1.0 Received: by 10.229.81.197 with SMTP id y5mr2381269qck.266.1316453035855; Mon, 19 Sep 2011 10:23:55 -0700 (PDT) Received: by 10.229.227.137 with HTTP; Mon, 19 Sep 2011 10:23:55 -0700 (PDT) In-Reply-To: References: <201109182104.45994.luke@dashjr.org> <21269.192.251.226.206.1316448084.squirrel@lavabit.com> Date: Mon, 19 Sep 2011 13:23:55 -0400 Message-ID: From: Alex Waters To: Gavin Andresen Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Spam-Score: -1.3 (-) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (ampedal[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature 0.3 AWL AWL: From: address is in the auto white-list X-Headers-End: 1R5hZZ-0004bb-FV Cc: bitcoin-development@lists.sourceforge.net Subject: Re: [Bitcoin-development] Bitcoin Enhancement Proposals (BEPS) X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Sep 2011 17:24:02 -0000 I'm sorry that I misunderstood the protocol being separate from the client in regard to 'BEPS'. It definitely makes more sense that way. As far as naming; I vote BER pronounced Beer. On Mon, Sep 19, 2011 at 12:57 PM, Gavin Andresen wrote: > 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" =3D=3D Bitcoin Improvement Proposal > or "PEB" =3D=3D Proposal to Enhance Bitcoin > or "BER" =3D=3D Bitcoin Enhancement Request > > I think I like "BIP" =A0(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 > > -------------------------------------------------------------------------= ----- > BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA > Learn about the latest advances in developing for the > BlackBerry® mobile platform with sessions, labs & more. > See new tools and technologies. Register for BlackBerry® DevCon today= ! > http://p.sf.net/sfu/rim-devcon-copy1 > _______________________________________________ > Bitcoin-development mailing list > Bitcoin-development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bitcoin-development >