{"type":"rich","version":"1.0","author_name":"npub17ty4mumkv43w8wtt0xsz2jypck0gvw0j8xrcg6tpea25z2nh7meqf4qgyd","author_url":"https://nostr.ae/npub17ty4mumkv43w8wtt0xsz2jypck0gvw0j8xrcg6tpea25z2nh7meqf4qgyd","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2015-01-19\n📝 Original message:\u003e\n\u003e I'm a bit confused.  It's been a long time since I looked at protobuf (and\n\u003e will have to dig into it soon), but I seem to recall it doesn't have any of\n\u003e the determinism properties you guys just said.\n\u003e\n\nIt's not guaranteed no, which is why we store signed sub-messages as byte\narrays instead of typed submessages. In practice though, most\nimplementations do seem to serialise things the same way. I recall Python\nused to be an odd one out, unsure if it still is.\n\nOK, I guess we can boil this down more simply. BIP 70 uses protocol buffers\nbecause I designed it and implemented the original prototype (with lots of\ninput from Gavin and an earlier proposal by sipa). I used protocol buffers\nbecause, beyond all their nice properties, I used to work at Google and so\nwas very familiar with them.\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150119/bbd8b7d4/attachment.html\u003e"}