{"type":"rich","version":"1.0","author_name":"npub1ep4j5tjp6cd2774hrx96vh845dwqzhe3z7n3a2a9uxdm2dajqpgscm3rel","author_url":"https://nostr.ae/npub1ep4j5tjp6cd2774hrx96vh845dwqzhe3z7n3a2a9uxdm2dajqpgscm3rel","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2011-11-02\n🗒️ Summary of this message: Discussion on locking protocol version numbers and using sub_version_num as a client and version identifier in Bitcoin development. BIP proposal suggested.\n📝 Original message:Cool thread. I enjoyed reading that :) Thanks for sharing.\n\n\n________________________________\nFrom: Christian Decker \u003cdecker.christian at gmail.com\u003e\nTo: Amir Taaki \u003czgenjix at yahoo.com\u003e\nCc: \"bitcoin-development at lists.sourceforge.net\" \u003cbitcoin-development at lists.sourceforge.net\u003e\nSent: Wednesday, November 2, 2011 10:42 PM\nSubject: Re: [Bitcoin-development] Lock protocol version numbers\n\n\nJust for reference: https://github.com/bitcoin/bitcoin/pull/63\nThe issue resulted in my most useless pull request fixing two variables :-)\n\nI second the use of sub_version_num as a Client and Version identifier.\n\nRegards,\nChris\n\n\nOn Wed, Nov 2, 2011 at 11:33 PM, Amir Taaki \u003czgenjix at yahoo.com\u003e wrote:\n\nPoint taken.\n\u003e\n\u003e\n\u003eAbout the sub_version_num though. I prefer to let the field by defined clients however they wish, with just a guideline suggestion that IDENTIFIER VERSION is a format they should follow.\n\u003e\n\u003e\n\u003eThe idea being that different projects would have different release scheduling schemes and it'd be restrictive to lock people into the popular major.minor system.\n\u003e\n\u003e\n\u003eSo for the current bitcoin to find out the version number of other clients (if it was needed), it would have to parse the number from the string:\n\u003e\n\u003e\n\u003e\"Satoshi 0.5\"\n\u003e\n\u003e\n\u003eAlthough there would be little reason for this with a sane protocol versioning scheme.\n\u003e\n\u003e\n\u003eIf we're agreed then I'll start on that BIP.\n\u003e\n\u003e\n\u003e\n\u003e________________________________\n\u003eFrom: Gavin Andresen \u003cgavinandresen at gmail.com\u003e\n\u003eTo: Amir Taaki \u003czgenjix at yahoo.com\u003e\n\u003eSent: Wednesday, November 2, 2011 9:34 PM\n\u003eSubject: Re: [Bitcoin-development] Lock protocol version numbers\n\u003e\n\u003eGood idea.\n\u003e\n\u003eSounds perfect for a BIP....\n\u003e\n\u003e\n\u003eOn Wed, Nov 2, 2011 at 5:23 PM, Amir Taaki \u003czgenjix at yahoo.com\u003e wrote:\n\u003e\u003e Hey,\n\u003e\u003e Can we lock the version numbers to be the protocol version (which changes\n\u003e\u003e rarely) and instead use the sub_version_num field + revision number for\n\u003e\u003e individual builds?\n\u003e\n\u003e-- \n\u003e--\n\u003eGavin Andresen\n\u003e\n\u003e\n\u003e\n\u003e------------------------------------------------------------------------------\n\u003eRSA(R) Conference 2012\n\u003eSave $700 by Nov 18\n\u003eRegister now\n\u003ehttp://p.sf.net/sfu/rsa-sfdev2dev1\n\u003e_______________________________________________\n\u003eBitcoin-development mailing list\n\u003eBitcoin-development at lists.sourceforge.net\n\u003ehttps://lists.sourceforge.net/lists/listinfo/bitcoin-development\n\u003e\n\u003e\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20111102/12e3637a/attachment.html\u003e"}