LearnBitcoin

Bitcoin Dev Archive 2014

Proposed BIP status changes

5 messages, 15 to 16 Oct 2014. Started by Wladimir J. van der Laan.

Wladimir J. van der Laan (2), Luke Dashjr (2), Matt Corallo

Permalink Original thread on gnusha.org

Wladimir J. van der Laan permalink original

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

Matt Corallo in reply to Wladimir J. van der Laan permalink original

On 10/15/14 08:47, Wladimir wrote:

Quoted text (7 lines)
> 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.

Quoted text (25 lines)
> - 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
>
Luke Dashjr in reply to Wladimir J. van der Laan permalink original

On Wednesday, October 15, 2014 8:47:18 AM Wladimir wrote:

Quoted text (5 lines)
> 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

Quoted text (1 line)
> - BIP 21 (URI Scheme)

ACK

Quoted text (1 line)
> - BIP 22 (getblocktemplate - Fundamentals)

ACK

Quoted text (1 line)
> - BIP 31 (Pong Message)

ACK

Quoted text (1 line)
> - BIP 34 (Block v2, Height in coinbase)

ACK

Quoted text (1 line)
> - BIP 35 (mempool message)

ACK

Quoted text (3 lines)
> - 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

Wladimir J. van der Laan in reply to Luke Dashjr permalink original
Quoted text (2 lines)
>
> 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

Luke Dashjr in reply to Wladimir J. van der Laan permalink original

On Thursday, October 16, 2014 6:22:04 AM Wladimir wrote:

Quoted text (6 lines)
> > 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.