* [Bitcoin-development] Proposed BIP status changes
@ 2014-10-15 8:47 Wladimir
2014-10-16 4:29 ` Matt Corallo
2014-10-16 4:36 ` Luke Dashjr
0 siblings, 2 replies; 5+ messages in thread
From: Wladimir @ 2014-10-15 8:47 UTC (permalink / raw)
To: Bitcoin Dev
These BIPs should go to Final state - they are implemented all over
the place, and are thus entirely fixed in place now. Any changes would
require a new BIP as amandment:
- BIP 14 (BIP Protocol Version and User Agent)
- BIP 21 (URI Scheme)
- BIP 22 (getblocktemplate - Fundamentals)
- BIP 31 (Pong Message)
- BIP 34 (Block v2, Height in coinbase)
- BIP 35 (mempool message)
- BIP 37 (Bloom filtering)
Let me know if you (don't) agree.
Wladimir
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [Bitcoin-development] Proposed BIP status changes
2014-10-15 8:47 [Bitcoin-development] Proposed BIP status changes Wladimir
@ 2014-10-16 4:29 ` Matt Corallo
2014-10-16 4:36 ` Luke Dashjr
1 sibling, 0 replies; 5+ messages in thread
From: Matt Corallo @ 2014-10-16 4:29 UTC (permalink / raw)
To: bitcoin-development
On 10/15/14 08:47, Wladimir wrote:
> These BIPs should go to Final state - they are implemented all over
> the place, and are thus entirely fixed in place now. Any changes would
> require a new BIP as amandment:
>
> - BIP 14 (BIP Protocol Version and User Agent)
>
> - BIP 21 (URI Scheme)
ACK.
> - BIP 22 (getblocktemplate - Fundamentals)
>
> - BIP 31 (Pong Message)
>
> - BIP 34 (Block v2, Height in coinbase)
>
> - BIP 35 (mempool message)
>
> - BIP 37 (Bloom filtering)
>
> Let me know if you (don't) agree.
>
> Wladimir
>
> ------------------------------------------------------------------------------
> Comprehensive Server Monitoring with Site24x7.
> Monitor 10 servers for $9/Month.
> Get alerted through email, SMS, voice calls or mobile push notifications.
> Take corrective actions from your mobile device.
> http://p.sf.net/sfu/Zoho
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [Bitcoin-development] Proposed BIP status changes
2014-10-15 8:47 [Bitcoin-development] Proposed BIP status changes Wladimir
2014-10-16 4:29 ` Matt Corallo
@ 2014-10-16 4:36 ` Luke Dashjr
2014-10-16 6:22 ` Wladimir
1 sibling, 1 reply; 5+ messages in thread
From: Luke Dashjr @ 2014-10-16 4:36 UTC (permalink / raw)
To: Wladimir; +Cc: bitcoin-development
On Wednesday, October 15, 2014 8:47:18 AM Wladimir wrote:
> These BIPs should go to Final state - they are implemented all over
> the place, and are thus entirely fixed in place now. Any changes would
> require a new BIP as amandment:
>
> - BIP 14 (BIP Protocol Version and User Agent)
ACK
> - BIP 21 (URI Scheme)
ACK
> - BIP 22 (getblocktemplate - Fundamentals)
ACK
> - BIP 31 (Pong Message)
ACK
> - BIP 34 (Block v2, Height in coinbase)
ACK
> - BIP 35 (mempool message)
ACK
> - BIP 37 (Bloom filtering)
>
> Let me know if you (don't) agree.
Shouldn't we be doing this in a GitHub PR rather than spamming up the ML?
Luke
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [Bitcoin-development] Proposed BIP status changes
2014-10-16 4:36 ` Luke Dashjr
@ 2014-10-16 6:22 ` Wladimir
2014-10-16 6:46 ` Luke Dashjr
0 siblings, 1 reply; 5+ messages in thread
From: Wladimir @ 2014-10-16 6:22 UTC (permalink / raw)
To: Luke Dashjr; +Cc: Bitcoin Dev
>
> Shouldn't we be doing this in a GitHub PR rather than spamming up the ML?
Not really. BIP changes should be discussed on the mailing list,
that's the way to get community consensus (as specified in BIP1).
Wladimir
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [Bitcoin-development] Proposed BIP status changes
2014-10-16 6:22 ` Wladimir
@ 2014-10-16 6:46 ` Luke Dashjr
0 siblings, 0 replies; 5+ messages in thread
From: Luke Dashjr @ 2014-10-16 6:46 UTC (permalink / raw)
To: Wladimir; +Cc: Bitcoin Dev
On Thursday, October 16, 2014 6:22:04 AM Wladimir wrote:
> > Shouldn't we be doing this in a GitHub PR rather than spamming up the ML?
>
> Not really. BIP changes should be discussed on the mailing list,
> that's the way to get community consensus (as specified in BIP1).
>
> Wladimir
Discussion vs simple ACKing.
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2014-10-16 6:46 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-10-15 8:47 [Bitcoin-development] Proposed BIP status changes Wladimir
2014-10-16 4:29 ` Matt Corallo
2014-10-16 4:36 ` Luke Dashjr
2014-10-16 6:22 ` Wladimir
2014-10-16 6:46 ` Luke Dashjr
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox