PM
Subject: Re: [Bitcoin-development] Bitcoin Enhancement Proposals (BEPS)
> 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
> 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.
this is an excellent "painting the bikeshed" question, so i cannot
resist p
t: Re: [Bitcoin-development] Bitcoin Enhancement Proposals (BEPS)
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 s
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 cand
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
> http://www.python.org/dev/peps/ is a good reference if you're
> interested in seeing how PEPs work in action. I would be more than
> willing to maintain a similar index if that's what people want.
Would the multi-signature proposal be a good test case for BEP-0002?
https://gist.github.com/dba89
http://www.python.org/dev/peps/ is a good reference if you're
interested in seeing how PEPs work in action. I would be more than
willing to maintain a similar index if that's what people want.
Something to note is that Python does not use Git or GitHub (AFAIK).
So we would need to update 001 to re
On Sunday, September 18, 2011 8:31:55 PM Amir Taaki wrote:
> Ideally these should go in a github.com/bitcoin/beps/ repo.
Please, somewhere people can freely commit to...
--
BlackBerry® DevCon Americas, Oct. 18-20, San Fra
I adapted the Python PEP 0001 to Bitcoin (its license is public domain):
https://en.bitcoin.it/wiki/Bitcoin_Enhancement_Proposals
https://en.bitcoin.it/wiki/BEP_0001
BEP 0001 is open to additional authors and revisions.
Ideally these should go in a github.com/bitcoin/beps/ repo.
Lets have a st
9 matches
Mail list logo
