Re: [Bitcoin-development] Revisiting the BIPS process, a proposal

2013-11-19 Thread Gregory Maxwell
On Tue, Nov 19, 2013 at 9:45 AM, Wladimir wrote: > Talking about complete, BIP 40 and 41 don't even have an associated > document: > https://github.com/bitcoin/bips > I agree that was over-eager number assigning. Maybe! The subject matter its assigned for is already _widely_ deployed, for better

Re: [Bitcoin-development] Revisiting the BIPS process, a proposal

2013-11-19 Thread Wladimir
On Tue, Nov 19, 2013 at 6:01 PM, Gregory Maxwell wrote: > On Tue, Nov 19, 2013 at 8:53 AM, Drak wrote: > > It's quite normal for standards bodies to allocate numbers when in draft > > status. If they don't pass, they don't pass - they are clearly labelled > > DRAFTs. > > > > +1 on having things

[Bitcoin-development] Fwd: Revisiting the BIPS process, a proposal

2013-11-19 Thread Wladimir
On Tue, Nov 19, 2013 at 6:06 PM, Peter Todd wrote: > On Tue, Nov 19, 2013 at 05:32:55PM +0100, Wladimir wrote: > > On Mon, Oct 21, 2013 at 4:30 PM, Jeff Garzik wrote: > > > > > BIP drafts are stored in git://github.com/bitcoin/bips.git/drafts/ and > > > are not automatically assigned a BIPS numb

Re: [Bitcoin-development] Revisiting the BIPS process, a proposal

2013-11-19 Thread Drak
On 19 November 2013 17:01, Gregory Maxwell wrote: > On Tue, Nov 19, 2013 at 8:53 AM, Drak wrote: > > It's quite normal for standards bodies to allocate numbers when in draft > > status. If they don't pass, they don't pass - they are clearly labelled > > DRAFTs. > > > > +1 on having things in a g

Re: [Bitcoin-development] Revisiting the BIPS process, a proposal

2013-11-19 Thread Peter Todd
On Tue, Nov 19, 2013 at 05:32:55PM +0100, Wladimir wrote: > On Mon, Oct 21, 2013 at 4:30 PM, Jeff Garzik wrote: > > > BIP drafts are stored in git://github.com/bitcoin/bips.git/drafts/ and > > are not automatically assigned a BIPS number. > > > > Are we going to move ahead with this? > > If so,

Re: [Bitcoin-development] Revisiting the BIPS process, a proposal

2013-11-19 Thread Gregory Maxwell
On Tue, Nov 19, 2013 at 8:53 AM, Drak wrote: > It's quite normal for standards bodies to allocate numbers when in draft > status. If they don't pass, they don't pass - they are clearly labelled > DRAFTs. > > +1 on having things in a github repository. Much better for collaboration, The IETF makes

Re: [Bitcoin-development] Revisiting the BIPS process, a proposal

2013-11-19 Thread Drak
On 19 November 2013 16:32, Wladimir wrote: > > On Mon, Oct 21, 2013 at 4:30 PM, Jeff Garzik wrote: > >> BIP drafts are stored in git://github.com/bitcoin/bips.git/drafts/ and >> are not automatically assigned a BIPS number. >> > > Are we going to move ahead with this? > > If so, I'm volunteering

Re: [Bitcoin-development] Revisiting the BIPS process, a proposal

2013-11-19 Thread Wladimir
On Mon, Oct 21, 2013 at 4:30 PM, Jeff Garzik wrote: > BIP drafts are stored in git://github.com/bitcoin/bips.git/drafts/ and > are not automatically assigned a BIPS number. > Are we going to move ahead with this? If so, I'm volunteering to create the repository and import the current BIPs from

[Bitcoin-development] Disentangling Crypto-Coin Mining: Timestamping, Proof-of-Publication, and Validation

2013-11-19 Thread Peter Todd
In the design of Bitcoin mining serves two fundemental purposes: proof-of-publication and order consensus. Bitcoin's design entangles these fundemental purposes with other goals, such as validation and initial coin distribution. This leads to a design that is fundementally unscalable, albeit effec