Re: [Bitcoin-development] Proposed BIP status changes

2014-10-16 Thread Wladimir

 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

--
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


Re: [Bitcoin-development] Proposed BIP status changes

2014-10-16 Thread Luke Dashjr
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.

--
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


[Bitcoin-development] Proposed BIP status changes

2014-10-15 Thread Wladimir
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

--
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


Re: [Bitcoin-development] Proposed BIP status changes

2014-10-15 Thread Matt Corallo


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
 

--
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


Re: [Bitcoin-development] Proposed BIP status changes

2014-10-15 Thread Luke Dashjr
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

--
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