* [bitcoin-dev] Process for BIP number allocation
@ 2015-07-23 10:21 Kalle Rosenbaum
2015-07-23 19:29 ` Peter Todd
0 siblings, 1 reply; 4+ messages in thread
From: Kalle Rosenbaum @ 2015-07-23 10:21 UTC (permalink / raw)
To: bitcoin-dev
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
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [bitcoin-dev] Process for BIP number allocation
2015-07-23 10:21 [bitcoin-dev] Process for BIP number allocation Kalle Rosenbaum
@ 2015-07-23 19:29 ` Peter Todd
2015-07-23 21:36 ` Kalle Rosenbaum
0 siblings, 1 reply; 4+ messages in thread
From: Peter Todd @ 2015-07-23 19:29 UTC (permalink / raw)
To: Kalle Rosenbaum, Kalle Rosenbaum via bitcoin-dev, bitcoin-dev
-----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-----
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [bitcoin-dev] Process for BIP number allocation
2015-07-23 19:29 ` Peter Todd
@ 2015-07-23 21:36 ` Kalle Rosenbaum
2015-07-24 2:26 ` Peter Todd
0 siblings, 1 reply; 4+ messages in thread
From: Kalle Rosenbaum @ 2015-07-23 21:36 UTC (permalink / raw)
To: Peter Todd; +Cc: bitcoin-dev
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>:
> -----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-----
>
>
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2015-07-24 2:26 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-07-23 10:21 [bitcoin-dev] Process for BIP number allocation Kalle Rosenbaum
2015-07-23 19:29 ` Peter Todd
2015-07-23 21:36 ` Kalle Rosenbaum
2015-07-24 2:26 ` Peter Todd
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox