Process for BIP number allocation
4 messages, 23 to 24 Jul 2015. Started by Kalle Rosenbaum.
Kalle Rosenbaum (2), Peter Todd (2)
Hi all
I suggest that we add to the "BIP Editor Responsibilities & Workflow" section of BIP0001 that if the BIP editor for some reason won't handle the BIP within a week, he/she should notify the author within that same week with an estimate on when it will be handled.
Maybe we could extend it to two weeks instead, the important thing is that the author knows what to expect.
I'm trying to get BIP numbers allocated for Proof of Payment. I have requested it from the BIP editor Gregory Maxwell with CC this list. I also emailed Gregory in private about it. So far I have not seen any reaction to my requests.
There are a number of BIP proposals floating arount right now, I don't know the exact status of them all, but this is roughly how it looks for some of them:
Date of request, bip#, Author, Title july 4, -, Gregory Maxwell, Invalid Block Fork Postmortem june 29, -, Peter Todd, Full Replace-by-Fee Deployment Schedule june 22, 101, Gavin Andresen, Increase Maximum Block Size june 17, 68, Mark Friedenbach, Consensus-enforced transaction replacement signalled via sequence numbers june 6, -,Kalle Rosenbaum, Proof of Payment june 6, -,Kalle Rosenbaum, Proof of Payment URI scheme june 6, 69?, Kristov Atlas, Lexicographical Indexing of Transaction Inputs and Outputs
I think that the de facto process for BIP allocation and inclusion in the bips repository is unclear. When a number is requested, the author should at least get a reply from the bip editor that the request is seen by him/her. Also, if the editor disapproves on the BIP for some reason, the author must be notified somehow within reasonable and predictable time.
Regards, Kalle
On 23 July 2015 06:21:55 GMT-04:00, Kalle Rosenbaum via bitcoin-dev <bitcoin-dev@lists•linuxfoundation•org> wrote:
Quoted text (14 lines)
>Hi all > >I suggest that we add to the "BIP Editor Responsibilities & Workflow" >section of BIP0001 that if the BIP editor for some reason won't handle >the BIP within a week, he/she should notify the author within that >same week with an estimate on when it will be handled. > >Maybe we could extend it to two weeks instead, the important thing is >that the author knows what to expect. > >I'm trying to get BIP numbers allocated for Proof of Payment. I have >requested it from the BIP editor Gregory Maxwell with CC this list. I >also emailed Gregory in private about it. So far I have not seen any >reaction to my requests.
To be clear, where is an implementation of your proposed BIP?
The philosophy of the process - particularly for non-consensus BIPs - is running code, preferably in production. An actual number for the standard that code implements isn't a barrier to that process.
Remember that it's convenient for all if the number of BIPs out there isn't significantly higher than the number of actual standards in place that are being used.
A PoP-enabled fork of Mycelium is available at https://github.com/kallerosenbaum/wallet and the server (validating code) is available at https://github.com/kallerosenbaum/poppoc/
There's also a demo site using the server code at http://www.rosenbaum.se:8080/ and a demo video at https://www.youtube.com/watch?v=euzZcoCilhc
Mycelium Binaries are also available on the demo site.
Regards, Kalle
2015-07-23 21:29 GMT+02:00, Peter Todd <pete@petertodd•org>:
Quoted text (46 lines)
> -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 > > > > On 23 July 2015 06:21:55 GMT-04:00, Kalle Rosenbaum via bitcoin-dev > <bitcoin-dev@lists•linuxfoundation•org> wrote: >>Hi all >> >>I suggest that we add to the "BIP Editor Responsibilities & Workflow" >>section of BIP0001 that if the BIP editor for some reason won't handle >>the BIP within a week, he/she should notify the author within that >>same week with an estimate on when it will be handled. >> >>Maybe we could extend it to two weeks instead, the important thing is >>that the author knows what to expect. >> >>I'm trying to get BIP numbers allocated for Proof of Payment. I have >>requested it from the BIP editor Gregory Maxwell with CC this list. I >>also emailed Gregory in private about it. So far I have not seen any >>reaction to my requests. > > To be clear, where is an implementation of your proposed BIP? > > The philosophy of the process - particularly for non-consensus BIPs - is > running code, preferably in production. An actual number for the standard > that code implements isn't a barrier to that process. > > Remember that it's convenient for all if the number of BIPs out there isn't > significantly higher than the number of actual standards in place that are > being used. > > > -----BEGIN PGP SIGNATURE----- > > iQE9BAEBCAAnIBxQZXRlciBUb2RkIDxwZXRlQHBldGVydG9kZC5vcmc+BQJVsUBy > AAoJEMCF8hzn9Lnc47AIAI11FdNBCFr9TybCvxKS32Idk4aZ4fveJ6ucHZx1PWPl > lzoz/CJBZGolWF9jWnpyiCnNxl64MjflNxi62ZD+VS4SEl0uHcYXdqXsNQzk9OoK > bZFXHJ57jZlHCwpwiLM72EWN6AZG/XZZFXisNRAvoYqryHdb5dDmVok0wPH87qOH > PBTlspyaKH4/OFDpslCdoDTLHcMxlasiyqNdC5NxC7eB1WpEtyGbOd1twvNeNH00 > 1opJNuajiUm1vJEhMS67a9DhfnYf9/3TDRtkc0lrYfF3r1n2aVtyzlPcJANX/cWa > 7L9HtC4WpVLqny0AiTs5dK6DxPIUy/u2Q9yFZ2oL6dM= > =RW4h > -----END PGP SIGNATURE----- > >
On Thu, Jul 23, 2015 at 11:36:45PM +0200, Kalle Rosenbaum wrote:
Quoted text (9 lines)
> A PoP-enabled fork of Mycelium is available at > https://github.com/kallerosenbaum/wallet and the server (validating > code) is available at https://github.com/kallerosenbaum/poppoc/ > > There's also a demo site using the server code at > http://www.rosenbaum.se:8080/ and a demo video at > https://www.youtube.com/watch?v=euzZcoCilhc > > Mycelium Binaries are also available on the demo site.
Good!
Now get people to actually use this and get back to us.
Remember that once there's actual adoption, BIP #'s will and have been assigned even for standards that are dangerous and badly designed; the barrier for non-consensus-stuff is the desire to avoid assigning a bunch of numbers for things that never get used.