{"type":"rich","version":"1.0","author_name":"npub10plv6jx6pktpp5ezldnus6kj8ffg045g2kdjl78w23njrlveqy5s3pfaef","author_url":"https://nostr.ae/npub10plv6jx6pktpp5ezldnus6kj8ffg045g2kdjl78w23njrlveqy5s3pfaef","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2015-01-19\n📝 Original message:For what it's worth, there was consideration of replacing protocol\nbuffers when modifying BIP70 to function with the altcoin I work on\n(changes were required anyway in eliminate any risk that payment\nrequests could not be accidentally applied to the wrong blockchain). The\neventual conclusion was that while we might have used JSON or XML if we\nwere starting from scratch, there's no choice that's clearly better.\nWhile deployed infrastructure for payment protocol is still quite\nlimited, it seems that the cost to replace at this point is higher than not.\n\nIf there's ever a major reworking of the standard, for example to handle\nrecurring payments, it's probably worth thinking about then, but\nprotocol buffers result in a compact data format which is supported by\nmost major languages (and size is a concern if dealing with Bluetooth or\nNFC), and has no major drawbacks I am aware of.\n\nRoss\n\nOn 19/01/2015 20:40, Mike Hearn wrote:\n\u003e\u003e I'm a bit confused.  It's been a long time since I looked at protobuf (and\n\u003e\u003e will have to dig into it soon), but I seem to recall it doesn't have any of\n\u003e\u003e the determinism properties you guys just said.\n\u003e\u003e\n\u003e It's not guaranteed no, which is why we store signed sub-messages as byte\n\u003e arrays instead of typed submessages. In practice though, most\n\u003e implementations do seem to serialise things the same way. I recall Python\n\u003e used to be an odd one out, unsure if it still is.\n\u003e\n\u003e OK, I guess we can boil this down more simply. BIP 70 uses protocol buffers\n\u003e because I designed it and implemented the original prototype (with lots of\n\u003e input from Gavin and an earlier proposal by sipa). I used protocol buffers\n\u003e because, beyond all their nice properties, I used to work at Google and so\n\u003e was very familiar with them.\n\u003e\n\u003e\n\u003e\n\u003e ------------------------------------------------------------------------------\n\u003e New Year. New Location. New Benefits. New Data Center in Ashburn, VA.\n\u003e GigeNET is offering a free month of service with a new server in Ashburn.\n\u003e Choose from 2 high performing configs, both with 100TB of bandwidth.\n\u003e Higher redundancy.Lower latency.Increased capacity.Completely compliant.\n\u003e http://p.sf.net/sfu/gigenet\n\u003e\n\u003e\n\u003e _______________________________________________\n\u003e Bitcoin-development mailing list\n\u003e Bitcoin-development at lists.sourceforge.net\n\u003e https://lists.sourceforge.net/lists/listinfo/bitcoin-development\n\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150119/c508d0e9/attachment.html\u003e"}