Nice. I'll check with justmoon when I hopefully meet him at the conference. If 
all is OK, hopefully 0.6 will be the last protocol version bump for a while.



________________________________
From: Mike Hearn <[email protected]>
To: Amir Taaki <[email protected]>
Cc: "[email protected]" 
<[email protected]>
Sent: Saturday, November 12, 2011 7:31 PM
Subject: Re: [Bitcoin-development] [RFC] BIP 14 - Protocol Version and User 
Agent


Looks pretty reasonable to me. If Gavin changes the mainline client to use this 
format I'll change BitcoinJ as well. It'll need a bit of API work so clients 
are sure to set it up properly.


On Thu, Nov 10, 2011 at 10:16 PM, Amir Taaki <[email protected]> wrote:

Hi,
>
>
>https://en.bitcoin.it/wiki/BIP_0014
>
>
>Thanks to Gavin Andresen for proof reading and suggesting clarifications. 
>Thanks to Patrick Strateman for suggesting the hierarchical format and 
>pointing out some flaws of browser user-agents to me.
>
>
>The timeline is written in the past tense since BIPs are meant to be readable 
>in the future for explaining why we took certain decisions with bitcoin. A 
>nice cache for future historians when bitcoin is ubiquitous ;)
>
>
>
>The next version 0.6 should be the protocol version which becomes peeled off 
>from the current client. There are still some changes migrating into the 
>protocol that need to be finished.
>
>
>------------------------------------------------------------------------------
>RSA(R) Conference 2012
>Save $700 by Nov 18
>Register now
>http://p.sf.net/sfu/rsa-sfdev2dev1
>_______________________________________________
>Bitcoin-development mailing list
>[email protected]
>https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>
------------------------------------------------------------------------------
RSA(R) Conference 2012
Save $700 by Nov 18
Register now
http://p.sf.net/sfu/rsa-sfdev2dev1
_______________________________________________
Bitcoin-development mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bitcoin-development

Reply via email to